"Unidentified Network" with No Connectivity to Router or Internet

[oneofthem]

"Unidentified Network" with No Connectivity to Router or Internet

Two day ago I was streaming video to JTV when suddenly my computer froze. I immediately knew it was strange because the computer did not respond to mouse movement or ctrl+alt+del, which has never happened before in the 4 years of owning this rig.
I proceeded to reboot the computer and found that I was not connected to the internet. I turned off the Router and Modem for 30 seconds and plugged it back in which did not resolve the issue. I then decided that the video I was uploading may have overloaded the router (Linksys WRT54G v6) so I performed a Hard Reset of the router which did not resolve the issue. It instead caused another issue which I corrected by changing the TCP/ip4 settings to DHCP because it was before set on a static IP. When changing the settings however I noticed that upon clicking "Okay" from the properties menu the window would become unresponsive and not close unless I rebooted. I booted up in Safe Mode with Networking to succesfully change the settings but even in Safe Mode my connection to the internet does not work.
What makes this case particularly odd to me is the fact that I can NOT open my router's web page. I will put 192.168.1.1 (my router's IP) into the Browser but it loads forever and does not connect. Usually if my internet connection is the problem I can still get to my Router.
Unfortunately I can not get any information off of the effected computer because I lack any flash drives to do so with, so I can not post an ipconfig /all for you. I can confirm that there is nothing wrong with my network tcp/ip settings.

So my problem in a nutshell is:
After my computer froze I suddenly can not connect to my router or the internet, while every other device in the house can. I have tried bypassing the router and hooking directly into the modem as well. The network shows up as "Unidentified Public Network" with no connectvity. I have also disabled and re-enabled the nForce Networking Controller driver and even uninstalled and reinstalled it.

 

[chev65]

Following some of the steps in this tutorial might help
http://www.sevenforums.com/tutorials/71408-unidentified-networks-set-private-public.html?filter

There is a chance that your default gateway was changed in which case the link below might help.
Windows 7 Unidentified Network, Limited Access, No Internet Connection Problem Resolved

You should also try another reset of your router with DHCP enabled on the Win 7 machine.

 

[oneofthem]

Well I tried both of those already previously, and both of their problems are very different from my own anyway. They had 2 networks, a regular network and a unidentified one. My problem is my regular network is showing up as "Unidentified" when everything else can connect to it no problem. Network Troubleshooter says it could not identify the problem.

 

[chev65]

If you can't do an ipconfig or open your routers web page then it could be hardware failure of some type. Have you using system restore on the machine? Maybe clearing the cmos would help because it sounds like your board is messed up.

 

[oneofthem]

I have tried System Restore to a couple different dates and it did not help. What do you mean by clearing up the cmos? Could I get instructions on how to do that

Oh btw I found a Flash Drive and AM able to do an ipconfig. Here it is:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Spartan
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media unoperational
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 02-EF-22-FD-23-10
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b1f5:aef:d4da:af18%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.254(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.100
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{83531D2C-45FA-466B-892F-8FE7BF842854}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

 

[chev65]

On your motherboard somewhere there is a small blue jumper which probably says cmos in very small letters. You just need to power down the machine, unplug the power and drain the power by pushing the start button. With the side case off you can access the cmos clear jumper, you just need to move the jumper from one side to the other. It may say CLRTC , you can look this info up as it's different for most boards.

It's a good idea to copy your bios settings before hand so you can return those settings to normal values. Sometimes you only need to enable the SATA drives. You can also do this by removing the mobo battery but you need to reset the bios time/date settings if you do that. I found this manual for your board but you need Adobe acrobat to see it. If you scroll down to page 26 it tells you about the jumpers and what they do.
http://static.compusa.com/pdf/Asus_P5N-E_SLI_Manual.pdf

You can see the blue jumpers lower left in this picture of your board. One of them is the clear cmos button, should say which one in small letters.
http://www.cdrinfo.com/Sections/Reviews/Specific.aspx?ArticleId=20960

 

[oneofthem]

Well I unplugged it and drained the power, then opened it up and looked but wasn't sure if I was looking at the right thing. So I didn't touch anything and plugged it back in. I started it up and it was magically fixed!
I guess it just needed an extreme reboot or something! Either way, problem solved! Thanks for your help.

 

[chev65]

Sometimes just draining the power will fix these types of problems. Kinda figured it was a board problem of some sort with the freeze up and all. Looks like it worked in this case. Nice work on that one oneofthem. Glad we figured this out.

 

[Faladu]

I'm sorry, you unplugged the power to your PC, and then plugged it back in, and that fixed a network problem?
I don't buy that at all... jiggled a loose network cable and/or card back into place looking at it, that I can believe!
--
Network cards or on-board go bad, I always have a spare handy.

 

[chev65]

I'm sorry, you unplugged the power to your PC, and then plugged it back in, and that fixed a network problem?
I don't buy that at all... jiggled a loose network cable and/or card back into place looking at it, that I can believe!
--
Network cards or on-board go bad, I always have a spare handy.

Well I unplugged it and drained the power, then opened it up and looked but wasn't sure if I was looking at the right thing. So I didn't touch anything and plugged it back in. I started it up and it was magically fixed!
I guess it just needed an extreme reboot or something! Either way, problem solved! Thanks for your help.

He didn't just unplug it he also drained the power by unplugging the power supply and pressing the start button. Bleeding off power or clearing the cmos fixes board problems like this all the time. I've seen bleeding off power fix board problems like this on many occasion, chipsets are a little strange that way. Although it certainly wasn't magic, just another board problem, these things happen all the time.

 

[Faladu]

That's the thing I didn't catch, thanks for the follow up.