Peter's Blog

Redefining the Impossible

Windows Wifi not connecting


Had a manager with a shiny new Dell Inspiron 220 laptop which was working ok but suddenly the Wifi stopped connecting. It reported a weak signal (1Mbps) when trying to connect to either of the company wireless access points.

On a hunch (I cannot recall my reasoning but I'm not sure it was desperation) I tried giving it a static IP address rather than using automatic settings (i.e. DHCP). Sure enough, this cured the problem, connected fine. I looked in the dhcp server logs and while it was not complaining that the IP address pool was all used, it did seem that all the IP addresses available were being used. I increased the number of IP addresses available to be allocated by the dhcp server and problem solved.

The big mystery to me is why Windows XP would report this as a problem with a weak signal? Isn't the access to the dhcp server and the allocation of the IP address at a layer above the wireless connection? Anyway, it's useful to be warned that the wireless diagnostics are misleading.


Filed under: dhcp wifi windows

Anonymous Says:

over 3 years ago

Perhaps the wifi driver was trying to connect to *another* wireless access point - further away, probably not one of your own, since it could not get a lease from the near-by access point, and that's where the 'weak signal' bit comes from...

Peter Says:

over 3 years ago

Well it listed the local access points and it said it was trying to connect to them. I've never seen any other networks listed in the 'View Available Wireless Networks' thing but I know it is possible to hide from that.

Peter

Have Your Say

I welcome constructive comments or questions but I reserve the right to delete any comments that displease me.

Who are you?

(Optional) If you enter an email address here I might email you back. Your email address will not be sold to spammers or shown anywhere

What do you have to say?