


Don't ask me why the desktop didn't have any problems. That was it! The laptop could connect to the DHCP server again. So I removed the power from it, reconnected it -and- BINGO!

Request has timed out.Īfter double checking to see if all my cables were still connected correctly, I decided there's only one thing left to do: reset the router. Then I decided to see if I would get any error messages if I "renewed" the IP address of my network adapter by running the command ipconfig /renew from a command window, and sure enough, I got an error: An error occurred when renewing interface Local Area Connection: Unable to contact your DHCP server. Weird thing was that at the same time my desktop computer was running too, and its network connection status showed that it had been assigned an IP address by the DHCP server. After checking the connection details, I noticed that the connection had somehow been assigned a .x address, instead of a 192.168.1.x address that should have been "handed" out by the DHCP server. Windows XP wouldn't connect to the Internet anymore. The Linksys router has its DHCP server enabled.Īfter installing SP2 on my laptop I ran into problems. Computers are set to obtain IP addresses & DNS server addresses automatically. Never had any connectivity problems before. I use a Linksys broadband router to connect several PC's to my ADSL connection. It happened to me too, and I took some time to figure out what was wrong. The Local Area Connection Status will show a warning that it has "Limited or no connectivity". I have heard several people complain about this problem: After upgrading to Windows XP Service Pack 2, they lose their network connection. "Limited or no connectivity" Network Error in Service Pack 2 By: Arie Slob
