Windows XP SP 3 Wireless Issues (winsock corruption)
Posted on 2010-08-23
We have several Laptops that are frequently (many times a day) docked then undocked. We find that at some point the IP of the Lan Card is not released when undocked and if you reboot the computer without a LAN connection the card gets a 169.254.x.x address. Normal a working Laptop once it is undocked the Lan IP on an ipconfig returns to 0.0.0.0 (network cable is unplugged notice) and the Wireless Card with a valid IP. If I do a route print while unplugged from the Lan then the LAN card interface doesn’t display, only the Wireless IP Interface and the Loopback IP.
All computers are Windows XP SP3 with all security and critical Windows updates up to date.
At some point something gets corrupted where when I removed the computer form the dock and do an ipconfig then the Lan IP still shows an IP address (should show 0.0.0.0). And if I do a route print the Lan IP address shows as an active interface and is the active Default Gateway.
Currently we reset the Winsock by running Netsh commands:
Netsh int ip reset reset.log
Netsh winsock reset category
After running these commands and rebooting the computer everything works properly again for a while but something triggers this to corrupt again. It seems that the media sensing fails to recognize that the network cable has been removed. If the Lan IP is not released and the routing table doesn’t update to route through the wireless card then the computer cannot see the network.
Is there any permanent fix for this so when the network cable is released the IP is released and the route table updates?