Odd IP Issue

rctneil · 8 Sep 2009 at 18:57

Hello,
I have a client who's laptop connects to their wireless network fine and can use the net fine for about 5 mins (bit slow though) and all of a sudden, pretty instantly, the connection gets the "Limited or no connectivity" message. I did cmd > ipconfig /all and it says that the current ip when the net dies is 169.254.something.something

After about 8 minutes, all is whell and I get the 192.168.2.4 normal dhcp address it should have.

If i release the ip and try to renew it during the problem, it never manages to renew it.

Any ideas guys?

Thanks

Regards,
Neil

esK` · 8 Sep 2009 at 19:25

WinsockXP fix. Try that.

rctneil · 8 Sep 2009 at 19:31

Will that stop it suddenly changing to the odd 169.254 address?

esK` · 8 Sep 2009 at 19:39

Yeah it flushes out the winsock / netbios, I have it on my memory stick for work.

rctneil · 9 Sep 2009 at 12:02

Still no luck with solving this. I tried a micrsoft fix it thing too which also failed.

I ahve some print screens of the system in question whcih I will post below:

I the first pic, the top half of the cmd windows shows the settings when the net is working but a few seconds later it all suddenly changed to the settings in the lower portion of that same cmd window

And this is the odd ip it keeps changing too:

169.254.204.128

Biffa · 9 Sep 2009 at 12:28

Thats the IP address the TCP/IP stack will set itself to when it can't get an IP address from DHCP. Its a non routeable IP.

Its probably an incompatability between the wireless card in the computer and the wireless access point.

rctneil · 9 Sep 2009 at 12:29

Issue Solved.

I read about AutoConfiguring IP's on a Micrsoft Support Site so followed these instructions and it seems fine now. The client will let me know if it fails again:

These are the steps:

For Windows 2000, Windows XP, and Windows Server 2003, APIPA can be disabled by adding the "IPAutoconfigurationEnabled" DWORD registry entry with a value of 0x0 to the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Adapter GUID>
Note The Adapter GUID subkey is a globally unique identifier (GUID) for the computer's LAN adapter.

Specifying a value of 1 for IPAutoconfigurationEnabled DWORD entry will enable APIPA, which is the default state when this value is omitted from the registry.

Biffa · 9 Sep 2009 at 12:44

Yeah that will stop it assigning itself that address if it can't get an IP from the dhcp server, but it wont solve the problem of why its not able to get an IP address.

rctneil · 9 Sep 2009 at 12:49

The funny is, is that it IS getting an IP address from the router. It IS doing. It gets a correct 192.168.2.4 address whcih works fine and then the autoconfig ip suddenly bursts things and makes it fail. Disabling the autoconfig lets it keep it's assigned DHCP address

PistolPete · 9 Sep 2009 at 12:57

Looks like there is an issue with the DHCP server in the router.

The APIPA should only appear if the DHCP lease is un-renewable within the lease time or there is no DHCP available.

I'm guessing the DHCP server is issuing DHCPNAKs when it shouldn't

rctneil · 9 Sep 2009 at 12:58

How would this be solved then?

PistolPete · 9 Sep 2009 at 13:20

I'm assuming you get your DHCP from the router.
If so, I'd try a complete factory reset and reconfigure the router again and see how it goes.

J.B · 9 Sep 2009 at 13:23

Im going to blame it on the Belkin router!

You could try latest drivers for the wireless adaptor and latest firmware for the router.