Unsolved

This post is more than 5 years old

6 Posts

14783

July 14th, 2004 18:00

Computer not accepting IP address assigned by router

I have a 4 port linksys router (wired) and four computers connected to it.  Two of the computers are Windows XP, one is Windows 98SE, and the fourth is Windows ME.  The router is connected to a linksys cable modem.  All has been fine up until Monday.  On Monday, my daughter could not access the internet on her Dell 8100 machine (w/Windows XP).  All other computers access the internet fine.  I did alot of things I read on here to troubleshoot.  I connected my work laptop to the same ethernet wire and was able to access the internet so the problem has to be in her computer.   I discovered that her computer did not receive an IP address from the router.  However, when I logged on to the router via another computer, I could see that the router had assigned an IP address to her computer.  I could not ping the router or any other computer from her computer.  I fixed the problem by changing her configuration from being assigned an IP address by the router to a fixed IP address.  I simply used the one the router had assigned.   What could be the problem?  What is causing her computer to not be able to read or accept the assigned IP address from the router?  No changes had been made to her operating system prior to the problem (e.g., no windows updates had been installed recently).

2 Intern

 • 

12K Posts

July 14th, 2004 20:00

It sounds like the TCP/IP stack has become corrupt and the easiest way to fix it would be to uninstall the netwrok thru the device manager and reboot allowing Windows to re-install the adpater automatically.

6 Posts

July 14th, 2004 21:00

The first thing I did was uninstall the network card driver and reboot so that the driver was re-installed.   It did not help. 

1 Message

July 19th, 2004 20:00

Problems connecting to the Internet.

1. Cannot connect to the Internet Get "Page not found" message from IE.

2. From a DOS prompt - run ipconfig/all and you see that you have a valid IP address and subnet mask and default gateway addresses. If you get a 169.254.x.x IP address, which indicates that it can’t communicate with the DHCP server, the WinSock Stack may be corrupted.

3. There is a problem with Microsoft's critical update hotfix Q815485 causes some wireless drivers to fail. Remove Hotfix SP2 Q815485

4. There is a problem with Adware and Registry Fixers removing components that corrupt the Windows WinSock stack resulting in loss of Internet connection.

I cannot tell you how often this little utility has proved a lifesaver:

WinsockXPFix Direct download:

http://www.iup.edu/house/resnet/winfix.shtm

Bob...

2 Intern

 • 

12K Posts

July 19th, 2004 23:00

I think it is probably the update that is contained within 815485 that point to KB Article 826942 whihc is the real culprit for some wireless devices, Netgear in particular.  I have run in circles for about 4 days chasing this one becasue it did not affect my Linksys clients but played pure havoc with the one Netgear client I have.  Removed the hotfix for 826942 and all is well.

6 Posts

July 20th, 2004 13:00

2.  I got all 0's for the IP address

3.  My LAN is not wireless.

4. I tried the WinsockXPfix utility and it did not help.

Once I input a fixed IP address, the computer communicates normally with the router.  My problem is the computer no longer accepts a DHCP assigned address from the router.  On the router status page, I can see that it recognizes the computer and has assigned an IP address to it.  However, when I get on said computer, it cannot ping the router and it says it can't get an IP address.  I have not tried reconfiguring it back to DHCP yet.  I still have it on a fixed IP address.

2 Intern

 • 

12K Posts

July 30th, 2004 22:00

Sometime just uninstalling the NIC from the device manager and rebooting can make all the difference in the world.  Just make sure you have the correct driver before doing this so you can get back online.

2 Posts

July 30th, 2004 22:00

the utility recommended above ("WinsockXPFix") solved the problem.  before running, i installed ALL 3rd party software (i.e. any software not from MSFT or Dell). 

 

-dqc

2 Posts

July 30th, 2004 22:00

i have this same problem with an Inspiron 1100.  thus far  i have uninstalled EVERY piece of 3rd party software on the machine.

next i am going to run the utility ... if that doesnt work, then i will delete the network interface thru the device manager.

any other suggestion?  (this is what i get for letting my girlfriend use my computer)!

-dqc

No Events found!

Top