Ask a new question

Dreaded "Unidentified Network" after BSOD; No fix seems to work

Hey Guys.

Sorry to just come in here and post a new thread about what I'm sure is a common problem, but I've searched the internet to no avail and am at my wit's end.

Quick info: Windows 7, 64-bit.  I forget if I have Pro or Home Premium.  I have an Asus Striker Extreme (not Striker Extreme 2.  This is an older rig) which has 2 onboard LAN ports (nVidia networking).

I had gotten 2 BSODs recently.  I searched what was going on and it looked like it was due to a memory leak in the neworking stack.  Unfortunately, before I could do anything about it, I got a third BSOD, and this time when I rebooted I got the dreaded "Unidentified Network".  I couldn't get any communication to my router.

I tried everything I could find - route delete 0.0.0.0; netsh int ip reset; netsh wins reset; etc etc.  Downloaded updated drivers, nothing.  I connected my wife's Macbook to the ethernet cable, and instant connection  ... Eventually I just bought a new NIC - a TP-Link TG-3468 PCIE Gigabit Ethernet controller.  I plugged that in, installed the drivers ... still no connection.  

I tried booting into Ubuntu using a CD, and it didn't have drivers for the new NIC, and I still didn't have connection with the onboard lan.  Then I remembered that when I installed Win7 from XP that I had installed to a new HD, so I booted to XP (Win XP 64 Pro) on my secondary drive.  I installed the drivers for the new NIC, and BOOM - internet.  The onboard LAN ports were still dead.  At least I knew the NIC worked.

I disabled the onboard LAN in the BIOS just in case it caused a problem and booted back to Win7.  Still no connection to the router.  I know the hardware is good - I get internet everytime I boot into WinXP.  No internet ever booting into Win7.

My network setup:

Comcast -> Belkin router -> TP-Link TLSG1016D 16port switch -> PC's NIC 
All cabling is Cat5e (Full copper, no CCA).  

(All other devices on the network work fine, and this machine works fine in XP on this NIC.)

This computer usually gets a static IP of 192.168.2.50.  (My DHCP range for this network is 192.168.2.100 - 192.168.2.254.)

If I set the IP address to DHCP, I get the 169.x.x.x "GFY" address.  If I set the address to a static address (.2.50, gateway .2.1), I get "communication" in that I see incoming packets, but not many of them and they come in slowly.  "ping 192.168.2.1" sometimes reports "no response" and sometimes reports "no route to host found".

Firewall is disabled.  Antivirus is AVG; all internet/network "protection" is disabled.  I have no Bonjour anywhere on my machine that I can see (checked services, etc).

Things I've tried (multiple times and in combinations):

  • "Diagnose problems with this connection" (LOL)
  • Buy a new NIC (see above)
  • Router reboot (Multiple times)
  • Different ports on the switch.
  • Direct connection to the router.
  • Direct connection to the cable modem.
  • netsh int ip reset
  • netsh wins ip reset
  • ipconfig /flushdns
  • disabling IPv6
  • disabling "network sharing discovery"
  • all permissions on public networks
  • set this network to my "home network"
  • force set Speed/Duplex (tried 10/full, 100/full, 100/half, and 1Gb/full)
  • tried multiple static IPs (.2.53, .2.80)
  • deleted all networks from registry
  • add reg key *NVis... something - kept it from showing in Network Center, but didn't help
  • clean boot (msconfig - disable all non-MS services)

The last two items on my list:

1. Uninstall AVG (required for my work ... if this works I'll need to deep dive it :()

2. Clean Windows install (/sadpanda)


Before I do that, I was wondering if anyone else had any suggestions.  It really looks to me like my onboard LAN died so hard it took Windows networking with it ... 

Thanks in advance.

ipconfig /all:

Windows IP Configuration

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

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Gigabit PCI Express Network Adapter
   Physical Address. . . . . . . . . : 64-66-B3-03-65-C3
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.2.50(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{683AB3EE-541E-4935-B962-9E121B2B2B68}:

   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 . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

route print:

===========================================================================
Interface List
 15...64 66 b3 03 65 c3 ......Gigabit PCI Express Network Adapter
  1...........................Software Loopback Interface 1
 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

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
      192.168.2.0    255.255.255.0         On-link      192.168.2.50    266
     192.168.2.50  255.255.255.255         On-link      192.168.2.50    266
    192.168.2.255  255.255.255.255         On-link      192.168.2.50    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      192.168.2.50    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      192.168.2.50    266
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  1    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None


tl;dr:
Used to have network; now I don't. Network works fine in XP.  No fix seems to work.  WHAT DO?

note: I'm at work now, but will update this once I get home with more information.

Also, I don't know what the forum's policy on images is, but I uploaded a picture to imagur at bzneLdw, which shows the status with a static IP and no communication, despite packets going out and coming in.

Thanks!

Hello IRosmarin,

Thank you for posting your query in Microsoft Community Forum.

Do you get any error message? If yes, what is the complete and exact error message?

As your system is not on automatic DNS, your DNS addresses are manually set. Please refer to the following link to change the DNS settings to automatically assign DNS addresses and check the issue.

http://windows.microsoft.com/en-au/windows/change-tcp-ip-settings#1TC=windows-7

Please post back your results for further assistance, we'll be glad to assist you.

Regards,

Harkanwar

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Harkanwar.

Thank you for your reply.

I have not received any error except "destination host unreachable" when I ping my router.  And no connection to the internet, obviously.

As you can see above, my DNS servers have been manually set to Google's public DNS servers.  I don't think this is part of the issue, however, since DNS is issued to resolve names (like "www.google.com") to IP addresses (like 142.2.2.7), and I am unable to ping on my local network.

Thanks for the suggestion, though.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank you for the update!

I apologize for my late response.

Basically, when pinging a host on your own subnet the sender will first send an ARP (Address Resolution Protocol) request for the MAC address of the associated IP address. Since the host does not exist or is not identified, the sending station is reporting to you that the destination host is unreachable because the ARP request was not completed.

So, I would suggest you to try the following steps to diagnose the issue and check if you persists in the following methods:

Method 1:

As a test, boot into safe mode with networking and check if the issue is reproduced.

Start your computer in safe mode http://windows.microsoft.com/en-in/windows/start-computer-safe-mode#start-computer-safe-mode=windows-7

Select Safe mode with Networking in the Advanced startup options.

Check if you are able to connect to the router.

Method 2:

1. Open Device Manager by clicking the Start button, clicking Control Panel, clicking System and Security, and then, under System, clicking Device Manager. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

2. In the list of hardware categories, find and expand the Network Adapters and right click on the network device driver that you want to update, and then click Uninstall.

3. Install the latest drivers from the manufacturer's website.

For further information, visit the below mentioned link:
http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly

Method 3:

You may also refer to the suggestions by Shekhar S in the following thread.

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/lan-unidentified-network-no-network-access-on/120ce27b-561e-4629-86d2-d4d56580396c

Hope this information is helpful. For any further assistance, please post back with your results.

Thank you.

Regards,

Harkanwar

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Harkanwar.

I had tried all those things and nothing worked.

So I bought a new motherboard.  Everything worked great.  I think I had a hardware-level issue on my PCI southbridge controller.

Oh well.


Thanks for the help!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi IRosmarin,

Thank you for updating us with the status of the issue.

It's really unfortunate to know that the problem turned out to be a hardware-level issue. But I am happy to note that you finally figured out the root cause and were able to fix the problem.

I hope you do not find any more issues with your computer. However, if ever you get any issue regarding Windows, please feel free to reply. We'll be glad to assist you.

Regards,

Harkanwar

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated February 5, 2020 Views 1,346 Applies to: