We just installed WinXP + SP1 and latest Microsoft critical updates. It worked fine for one day, and accessing the internet via our Linksys DSL 4-port home router via DHCP.
After a break for dinner, the internet connection died for this computer. However, two other PC's connected to the router were still OK. We also tried bypassing the Linksys LAN card, by using a Linksys USB LAN connection, to same effect.
I cannot even ping the router at 192.168.1.1, and a netview replies with only the computer's hostname, e.g. \\MYPCNAME. If I ping MYPCNAME, it responds with 169.254.6.138 in a few msec's.
When working normally, ping MYPCNAME responds with 192.168.1.2 (or *.3 or *.4). Why does PCNAME thinks its loopback address is 169.254.6.138? If a good PC is disconnected from the router, it responds with the normal loopback address of 127.0.0.1.
We also tried setting the IP address to 192.168.1.4, subnet mask 255.255.255.0, and gateway 192.168.1.1, and set SBC PacBell's DNS servers per the Linksys router status. Then, I can ping the router, PacBell DNS addresses, and even the IP address for ad.doubleclick.net! It also pings other PC's on the home network by hostname. But http does not work for browsing the internet. All the network, DNS, and DHCP services are started, and have been restarted. So ping can access an IP address on the internet, but IE or Mozilla browsing does not work.
Can someone provide a clue how to repair, short of re-installing WinXP.
I should add that we had seen the IDENTICAL error condition when running on Win2000 -- after 3 years of running OK. We tried the same diagnostics as for WinXP, even with that odd 169.254.6.138 loopback address. So we decided to reformat and install WinXP from scratch. Time to upgrade anyway. My perception is that DHCP is not working correctly, and failing to assign loopback address to 127.0.0.1 when not connected, and to one of the router's addresses when connected. And DNS does not seem to work either, when I set the TCPIP properties to fixed addresses. It seems like there is something blocking internet accress, yet we don't have any ZoneLab software firewalls that might have gotten mistakenly set.
Darryl
