Here's the situation: This morning, everything was working FINE. I had some friends over and put too many computers in one room, tripping the circuit breaker. I reset the circuit breaker, and rebooted the two comps I own. Now one has internet, the other doesn't. The bum comp says it is connected to an "unidentified network" and spends a lot of time "Identifying..." I have explored many threads with regard to this issue with no avail. Ended up completely reinstalling Windows 7, yet the problem persists. I have also tried connecting the computer directly to my laptop (which has worked in the past, giving me internet on both via "shared internet connection") and the same message appears. Bonjour is not causing this issue. This exact same comp on the same network configured the same way worked earlier this morning. Any ideas?

Not enough information to debug your problem. But, it sounds like your computer is trying to connect to a network (possibly a wireless network outside your location?) and it is failing to connect. Press the Windows Key and R key at the same time. This will launch the Run dialog box Type cmd and press return. This will launch the command interpreter console window. type ipconfig /all and press return to get a listing of the network configuration. Post the info here. The same info should appear on both computers - except the IP addresses will be different. They should have the same Gateway, DNS Servers, DHCP, DNS Suffix, etc. configurations on the two computers. Try to Ping Google.com and see what results you get. If you get successful results (no packet loss). Then your network is working fine. Otherwise, the error message will be a good indicator of what to start looking for in order to solve the problem. Note - If there are multiple wireless networks, make sure your computer is trying to connect to yours. Problems can occur when you have connected to multiple wireless networks in the past. The computer will generally try to connect to the first available network in the cached list based on the order defined in the list. This has the effect of surprising you because it connects (or trys to connect) to a network you were not intending it to connect to."It's a tough life... but someone has to enjoy it!"

Both computers are hard wired. One has full connectivity and I have posted the ipconfig/all results below. They are connected to the same router. Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. Windows IP Configuration Host Name . . . . . . . . . . . . : ****** Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8168D/8111D Family PCI-E Gigab it Ethernet NIC (NDIS 6.20) Physical Address. . . . . . . . . : 00-24-1D-11-B7-A6 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ac4c:1ff:4d0e:a6ac%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.10.101(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Sunday, December 26, 2010 8:37:15 PM Lease Expires . . . . . . . . . . : Monday, December 27, 2010 8:37:14 PM Default Gateway . . . . . . . . . : 192.168.10.1 DHCP Server . . . . . . . . . . . : 192.168.10.1 DHCPv6 IAID . . . . . . . . . . . : 251667485 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-A0-8D-2C-00-24-1D-11-B7-A6 DNS Servers . . . . . . . . . . . : 192.168.10.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{37B2965D-35EF-4FCA-9ECB-5EA66B829679}: 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 Local Area Connection* 11: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2ccf:953:b8a3:991e(Prefe rred) Link-local IPv6 Address . . . . . : fe80::2ccf:953:b8a3:991e%11(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Also, pinging google gave 0% packet loss

The results you posted indicate that this computer is configured correctly and that the Ping results can resolve the host name Google.com and can furthermore successfully send/receive ICMP packets to this host. Therefore, you should be able to access the Internet via any installed and properly configured Browser. If you still cannot access the Internet, what error message are you getting? "It's a tough life... but someone has to enjoy it!"

This above info was posted from the computer that can connect. The other connects to an unidentified network with no internet access. Running repair wizard says that "'Local area connection' doesnt have a valid ip configuration." Again, this computer was fully functional this morning. I have since completely reloaded windows 7 and have installed the latest ethernet drivers (nforce 570 sli for win7 x64, which is the correct driver) Here's the IPCONFIG/ALL for the broken comp: Windows IP Configuration Host Name . . . . . . . . . . . . : Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet Physical Address. . . . . . . . . : 00-1D-7D-A1-00-45 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::8973:77a1:7224:21a5%16(Preferred) Autoconfiguration IPv4 Address. . : 169.254.33.165(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 268443005 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-A9-B6-52-00-1D-7D-A1-00-45 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{DE64974A-4313-44E1-BEA1-1BFF239DCD42}: 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 Local Area Connection* 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes

This above info was posted from the computer that can connect. The other connects to an unidentified network with no internet access. Running repair wizard says that "'Local area connection' doesnt have a valid ip configuration." Again, this computer was fully functional this morning. I have since completely reloaded windows 7 and have installed the latest ethernet drivers (nforce 570 sli for win7 x64, which is the correct driver)

Yep. That PC is not getting any attention from your DHCP server. The IP was assigned by APIPA (169.254.33.165 and subnet mask 255.255.0.0 are a dead giveaway for that). This means the PC self assigned its own IP configuration because it was not able to get it from the network. Can you Ping the IP address of your Router (your Gateway at 192.168.10.1)? If so, you have a connection to your Router. If not, is the Router configured as your DHCP Server? Or are you using another PC/Server for DHCP services? It's possible that your DHCP server is out of assignable IP addresses within its scope range. You have to check the DHCP server properties to check this. Are you sure that the network configuration for the Ethernet Local Area Network Adapter is configured to use DHCP. Seems so based on the log info you included. But, you can always verify. Are you sure that the physical connection is working? Bad or disconnected Ethernet cable? Are you sure that the Router port is functioning (try a different physical port to connect the cable to)? Network card is configured properly (check Device Manager to ensure hardware is working and Driver is installed properly? Bottom line is that you need to ensure that your physical connections are solid, the hardware is working properly (you did mention that the whole problem started with a blown breaker and a power surge could have torched your network card), and that your DHCP and network configuration parameters are correct. Signing off for tonight. "It's a tough life... but someone has to enjoy it!"

This issue occurs if you have an incorrect default route setting. This route can be added by some third party programs. Please reinstall the audio adapter driver. If the issue persists, please run the following command in command prompt with administrative privilege. route delete –p 0.0.0.0 ON-LINK If the issue still occurs, please run route print > %userprofile%\Desktop\routeprint.txt Then open the file routeprint.txt on Desktop, paste the contents into your post.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

This issue occurs if you have an incorrect default route setting. This route can be added by some third party programs. Please reinstall the network adapter driver. If the issue persists, please run the following command in command prompt with administrative privilege. route delete –p 0.0.0.0 ON-LINK If the issue still occurs, please run route print > %userprofile%\Desktop\routeprint.txt Then open the file routeprint.txt on Desktop, paste the contents into your post. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Jagade: I have switched out the ethernet cable (switched the cables between the working comp and non-working comp--the working one still worked and the non-working was still broken). Pinging the router's ip address loses all packets. The router is the DHCP server (DHCP is enabled and IP addresses range from 192.168.10.100 to 192.168.10.200--seems like enough open addresses). Different router port made no change. Device manager shows that the device is functioning properly and the drivers are up to date. How likely is a blown card? It seems strange that windows 7 recognizes my network adapter and says that it is functioning properly if it indeed is blown... Arthur Xie: The "route delete" command didn't work (see below). C:\Windows\system32>route delete -p 0.0.0.0 on-link The route deletion failed: The parameter is incorrect. C:\Windows\system32>route delete -p 0.0.0.0 The route deletion failed: Element not found. So here is the "route print" information: C:\Windows\system32>route print =========================================================================== Interface List 13...00 1d 7d a1 00 45 ......NVIDIA nForce 10/100 Mbps Ethernet 1...........................Software Loopback Interface 1 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 11...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 169.254.0.0 255.255.0.0 On-link 169.254.201.196 266 169.254.201.196 255.255.255.255 On-link 169.254.201.196 266 169.254.255.255 255.255.255.255 On-link 169.254.201.196 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 169.254.201.196 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 169.254.201.196 266 =========================================================================== Persistent Routes: None IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 13 266 fe80::/64 On-link 13 266 fe80::b91b:cf05:f1ac:c9c4/128 On-link 1 306 ff00::/8 On-link 13 266 ff00::/8 On-link =========================================================================== Persistent Routes: None

OK. The reason I suspected hardware problems was because you said (a) you had a power outage that precipitated this problem and (b) that you re-installed Windows 7 in an effort to fix it... which pretty much rules out software as the underlying cause of your problem. To truly rule out a failed network card, you really should trying using a replacement or add a second card if you can get access to another LAN card. I'd try installing it and connecting your network cable to it. You could also beg, buy, steal, or borrow a USB wired or wireless network adapter and try that. Then you'll know for sure that it isn't hardware related. Moving on... The steps that Arthur had you do failed because, for one thing, you don't use the -p switch with any Route command other than ADD. And you don't need to specify a Gateway (On-link) when running the Route DELETE command. In the second case, where you tried running Route Delete -p 0.0.0.0 it failed because no Route exists for the destination network 0.0.0.0 (equal to the entire Internet IP domain). That Route does not exist because you never got assigned a valid routable IP address by the DHCP server and there is also no Gateway assigned from which to get the Route assignment in the first place, etc. etc. But, I digress... If you want to see what your Route table should really look like, do a Route Print on your "functioning" computer that is connected to the network/Internet. You will see that the very first entry in the table looks something like: 0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.100 20 (bold means these values vary - because your network card is your interface and the IP address assigned to it is via DHCP, the value 20 is the metric assigned to the Route - FYI, a lower metric number means that that Destination Route will be tried first when routing IP packets). At this point - assuming that your hardware really is working - then we have to also assume that your network stack is simply are not picking up configuration information from the DHCP server (your Router). You might try checking to make sure that the following Services are running (they must say STARTED in the STATUS column and AUTOMATIC in the STARTUP TYPE column). Go to Start, Control Panel, Administrative Tools, Services. Check DHCP CLIENT first. Then check NETWORK STORE INTERFACE service to make sure both are running. Also check REMOTE PROCEDURE CALL as well. Jagade "It's a tough life... but someone has to enjoy it!"

It's a long shot but try this: Power down the PC and disconnect the power from the wall outlet. If it's a laptop, remove the battery as well. Press the PC's power button; the fans may spin for a moment even though there's no power from the mains - this is because there may still be some power stored in the capacitors and we need to drain them. Reset your router - unplug the power, wait a few seconds (about 10 should do, 30 would be better). Plug it back in and wait for it to reconnect to your ISP. Plug the computer back into the wall outlet and turn it on. See if the problem's resolved.

If you have a hub, IP telephone or any other type of device between your computer and the router, I would try removing it/rebooting it. I just spent 5 hours troubleshooting a similar problem and it ended up being the IP telephone that acts as a hub for the PC's RJ45 connection that was causing the problem. ACK! I had unplugged and plugged the connection into the workstation 1/2 dozen times, but the phone is so innocuous, that I let it slip from my troubleshooting scope. BTW, the phone incoming and outgoing was working fine, but just unplugging and plugging the phone back in seems to have fixed the problem. Other than that, I was sometimes getting connection, and sometimes not. At first, it seemed that disabling Symantec Endpoint Protection fixed the problem, but after several tests, it proved to be less predictable than that. Every step led me to believe it was something else. Hours spent chasing down different blind alley's just to find it was basically a wirng problem. Good Luck, J