No IP following PC freeze-up

Intel / Core 2 duo 6550
January 30, 2009 at 14:14:31
Specs: Windows XP Pro, Intel Duo 4 gig RAM
My computer running XP Pro froze up earlier today. It has been doing this for the past week or so, about once a day, but a hard reset always seemed to restart the computer as normal. However, upon resetting the computer today, I was suddenly unable to connect to the internet. The network connection says that "limited or no connectivity." I'm able to post this through my girlfriend's wireless connection to the same router (I've tested a hard connection too -- works fine), so I know it can't be an issue with the router or my ISP. Some things I have tried include:

* Having the router's DHCP auto-assign me an IP, does not work.
* Setting a static IP, including gateway and DNS, for my computer. Does not work.
* Connecting the computer directly to the modem and obtaining an IP from my ISP. No dice.
* Checking WINSOCK to see if anything is wrong with my DHCP for the heck of it, no problem there.
* Uninstalling and re-installing my NIC drivers -- did nothing.

When I set my computer to a static IP, I'm still unable to ping the router, even with DHCP disabled on the router. All of this work is leading me to believe that the built-in NIC on my motherboard got fried when the computer froze this morning, but I am still able to ping 127.0.0.1 with no problem. I just figured I'd post on here to see if any of you had any more ideas to try before I ran out to buy a new NIC.


See More: No IP following PC freeze-up

Report •


#1
January 30, 2009 at 14:59:03
127.0.0.1 is your local host internal IP not the IP of your router. You can ping that IP even if you have no external connection. EG. my router ( a DLINK) uses 192.168.0.1 as it's default IP. What is the IP you enter to get into your router's admin interface? Can you ping that from the problem machine?

What does device manager tell you about your NIC? Have you tried a different LAN cable and a different router port?

Goin' Fishin' (Some day)


Report •

#2
January 30, 2009 at 16:54:17
I'm aware that 127.0.0.1 is the localhost IP. I was pinging to see if my computer could even "talk" with the NIC. I cannot ping my router at 192.268.1.1 with the problem machine whether I set the IP manually or let it try to connect to the router's DHCP.

Again, I can't obtain an IP straight from the ISP when I plug the problem computer directly into the cable modem. This leads me to believe that the problem lies somewhere within the drivers or Windows.


Report •

#3
January 30, 2009 at 17:27:47
What does ipconfig show? Powering off the computer when Windows is running is a bad idea. You need to determine what is causing the freeze-up as well.

"So won’t you give this man his wings
What a shame
To have to beg you to see
We’re not all the same
What a shame" - Shinedown


Report •

Related Solutions

#4
January 30, 2009 at 17:39:29
Have you tried a different ethernet cable?
What does devicemanager say about the NIC?

Is it reported a functioning? Since you say you have uninstalled/reinstalled drivers I suspect a hardware rather than software failure.

Goin' Fishin' (Some day)


Report •


Ask Question