Key things. The IPv4 Address is bogus and Default Gateway is **Blank**
I have literally tried EVERY windows 7 unidentified network fix I can google.
- Ipconfig /release then /renew : This fails with the error "An Error occurred while releasing interface Loopback Pseudo-Interface 1: The system cannot find the file specified. The /renew never get passed the configuration stage and gives the same error along with connection to DHCP server has timed out. << Duh it's trying to access bogus IP paths.
-The Bonjour fix is irrelevant as this is a fresh install and is not installed
-The DHCP Broadcast flag Broadcast does NOT affect anything whether it is enabled or disabled.
-TCP/IP reset does nothing
-The Default Gateway of 0.0.0.0 Default is not the culprit.
I have uninstalled the Network Drivers. Restarted. Installed new ones.
I have completely reinstalled Windows 7 with a reformat the hdd.
I have completely powered off, disconnected/drained power, and reset the mobo via CMOS reset.
I have reset the router, a DLink DIR-615, to orginal settings.
I have disabled IPv6, but it makes no difference.
I have reserved an IP in the router manually, and told the network adapter the settings, still it cannot connect to the router.
I have removed the router and connected directly to the modem. Windows 7 still can not automatically or manual receive proper IP and DNS settings.
I've pretty much checked and rechecked and reinstalled every possible solution.
The adapter is recognized as a properly working device in the hardware. The yellow led pulses with according that its trying to communicate with something, the green light for proper connection never appears.
Doesn't appear to be hardware problem. Oh, yes and the cable and router both work fine between a PS3, Laptop with Xp, another Wired Desktop with Windows 7, and even wifi phones have no problem connecting.
I've also tried old realtek drivers, new realtek drivers and the included CD drivers.
I'm mentally exhausted. The only option I haven't tried is to use an external wireless network card (well and a wire bridge with my laptop but i don't feel like configuring that). But I shouldn't have to buy a wifi card just to connect to the internet. Ethernet ports are supposed to plug n play. Ha yeeaaaaa rigghttttttt.
Sooo. I don't know how but out of sheer desperation I moved the computer and switched from a 15ft to a 3ft cable. Magically works now...Yet I just plugged in both my roommate and my laptop (turned off the wireless cards) and the cable works for both laptops.
And wowwwwwww just dawned on me, baked out of my mind to check the cable.
Turns out it was a cat5 cable and not a cat5e cable, which couldnt communicate with the Fast Ethernet port in the Mobo.
By far the most retarded - uh wut? - moment I've encountered.
My problem started after loading the drivers that came with my motherboard, the Nvidia drivers from BioStar started the problem, before that the built in driver in Win 7 Ultimate worked just fine, I uninstalled just the Nvidia driver for my network adapter and left all the other drivers in place and now I boot up and have the one proper network listed and am conneted to the Internet, before my solution was to disable then reenable the network adapter each reboot, then it would auto detect and just give me the one network, but after rebooting I would have to do it again.. Now it works perfectly after leaving the default Ethernet driver that came with Win 7 Ultimate
I know this thread is old, but I have been chasing my tail for a couple of days trying to get rid of the "unidentified network" issue. I tried everything...reset TCPIP, reset Winsock, removed the 0.0.0.0 default route, removed the nic to get Win 7 to reinstall it on boot, disabled bonjour, set a static IP/gateway, edited the registry to set a DHCP flag....basically everything I could find out there...nothing worked. As I was pulling some more hair out, I had a thought back to my old hardware days....check the Speed & Duplex of the NIC! Once I followed the steps below, and rebooted...up came my network...and no more "unidentified network"!! :-)
There are several ways to do this, but here is the one used...Open Network and Sharing Center, Click on "Change adapter settings", right-click on the NIC and select "Properties", then click the "Configure" button. Select the "Advanced" tab (I think pretty much any NIC should have this), scroll down until you find "Speed & Duplex". The default value for this setting is "Auto Negotiation"...change it to a fixed value (I used 100 Mbps Full Duplex). You may have to try a couple of the settings (there is no fear of causing any issues by changing this setting) in order to find what works best for your NIC...and the switch/hub/router that you are connected to.
Bottom line, my issue (and maybe yours, and maybe not) was caused by the NIC having trouble negotiating the connection speed to the network...since it couldn't get a solid connection, but knew there was a network there, Win7 classifies it as an "unidentified network". Once you set a fixed speed & duplex, the NIC immediately connects at the selected speed. This of course assumes you have set a speed & duplex that all components on your network is capable of running at (if you only have a 100Mbps port on your router, don't set the NIC to 1Gbps).
I have a very similar problem. My network shows as an unidentified network (with no internet access). When checking the router status I noticed that the computer I'm having problems with is not even in the DHCP clients table. All the other devices connected to the router work perfectly fine (wired and wireless). I have tried all of the other fixes mentioned so far in this topic (no success).
The origin of this problem is from dual booting windows 8 release candidate with windows 7. The network and internet worked just fine in windows 8, but when I returned to Windows 7 I found this problem. Even after reformatting (windows 7 only) the problem persisted.
When a server or workstation reboots, it has to re-establish its connection to any connected switches. Many switches have spanning tree protocol enabled by default on all ports. When the switch powers up, or when a device is connected to a port, the port normally enters the spanning tree listening state. When the Forward Delay timer expires, the port enters the learning state. When the Forward Delay timer expires a second time, the port is transitioned to the forwarding or blocking state.
Unfortunately, the Network Location Awareness service runs its tests to determine network info before the connected port is fully up so the discovery fails.
The solution for Cisco devices is to enable spanning tree portfast on the connected switches. PortFast causes a switch or trunk port to enter the spanning tree forwarding state immediately, bypassing the listening and learning states. You can use PortFast on switch or trunk ports connected to a single workstation, switch, or server to allow those devices to connect to the network immediately, instead of waiting for the port to transition from the listening and learning states to the forwarding state.
When you enable PortFast on a switch or trunk port, the port is immediately transitioned to the spanning tree forwarding state.
By immediately forwarding traffic, the NLA discovery tests complete and gather the proper network information.
If you are connected to a home router or other device, you will not have the option to configure PortFast. In that case, you can disable STP (Spanning Tree Protocol) as you do not need it unless you have multiple paths to other connected switches.