Ralink Wireless Adapter

Rozzy85 · 13 Nov 2011 at 16:57

I'm trying to fix a laptop using this adapter. It's got the problem where it can't get an IP from the DHCP and defaults to 169.xxx.xxx.xxx. I've had this problem before with routers before but this appears to be the NIC as I've tried it with two routers, both of which work fine.

I've unistalled then reinstalled the drivers (most recent) and the problem persists. Has anyone used a Ralink adapter before? They appear to make cheap, low end OEM stuff things which probably explains it. I was thinking to just get a better quality adapter instead. The hardware layer appears to be fine as the Link-Layers protocols work so it appears to be a TCP protocol issue.

Skidilliplop · 13 Nov 2011 at 17:04

The majority of layer3 functions occur within the OS not the adapter hardware or drivers. So it could well be windows.

If you set up another host on a link local address as well can they talk? are you able to boot from a linux liveCD and then ping stuff?

It could be the DHCP client service on the laptop isn't started /working hence it won't send DHCP discovers. It could also be the whole TCP/IP stack is rogered and needs re-installing.

Perhaps install wireshark on it to take a look at what's being sent and recieved on the WLAN interface.

Rozzy85 · 13 Nov 2011 at 17:31

Yeah, it appears you right. I just tried connecting with wired LAN and the same thing happens so it's not the adapter after all. How do I go about repairing the DHCP client service other than just doing a format/restore?

Skidilliplop · 14 Nov 2011 at 17:08

Well firstly check it is actually the DHCP client service by manually setting an IP and testing it. It could be the TCP/IP stack.

If it is the DHCP client service you can uninstall and re-install it using add/remote windows components.

But it's rarely a bad idea when something has gone this wrong to backup and format. It depends what's on there.

Rozzy85 · 14 Nov 2011 at 18:01

In the end I just did a restore (just a few files to backup) as I was just wasting my time trying different fixes. Tried manual IP and reseting the TCP/IP but to no avail. It did start getting an IP from the DHCP and could ping clients on the LAN but could not connect to the gateway.