Windows 7 Unidentified Network using ethernet

[Jaypowder]

Help! My ethernet cable was working fine until now. This is what I get:

This is in the properties dialog:

Can anyone help me? I think I have tried just about everything.
This is ipconfig:

Windows IP Configuration
Host Name . . . . . . . . . . . . : Jordan-HP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Belkin
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : 04-7D-7B-8B-83-CF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1c33:2bcf:b2e9:38bd%17(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.56.189(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 285506939
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B4-B0-D7-04-7D-7B-8B-83-CF
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : 802.11n Wireless LAN Card
Physical Address. . . . . . . . . : 9C-B7-0D-E5-DA-16
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1101:94d5:7cfc:a112%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, September 01, 2013 3:40:11 AM
Lease Expires . . . . . . . . . . : Wednesday, October 08, 2149 12:57:05 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 253759610
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B4-B0-D7-04-7D-7B-8B-83-CF
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.Belkin:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : Belkin
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 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
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:9d38:6abd:200d:b8f:3f57:fdfa(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::200d:b8f:3f57:fdfa%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{05E638E5-DE32-46B0-8075-2527544CA36C}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Reusable ISATAP Interface {BBE99161-C837-4CA0-B1F0-8E60FFAF8B54}:
 
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Thanks!

 

[TanyaC]

Hi, Welcome to Seven Forums.

This address...
Autoconfiguration IPv4 Address. . : 169.254.56.189(Preferred)

Means you are not getting an address from your router.

As a starting place, check your DHCP range in your router, and that hou have no MAC filters defined to only allow specific MAC addresses. Or specific MAC addresses blocked (such as the wired physical address/MAC address).

Often routers use a default range of 192.168.2.1 to 192.168.2.100 for the DHCP range.

Your wireless picked up 5, so do you have other PCs/Devices using the other addresses?

You could also try a static address just to test.

IP Address: 192.168.2.6
Subnet: 255.255.255.0
Gateway: 192.168.2.1
DNS: 192.168.2.1

and see if that works.

Please let us know how that goes..

Tanya

 

[PeaB4YouGo]

Hi Jay

Welcome to the forums.

Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : 802.11n Wireless LAN Card
Physical Address. . . . . . . . . : 9C-B7-0D-E5-DA-16
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1101:94d5:7cfc:a112%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, September 01, 2013 3:40:11 AM
Lease Expires . . . . . . . . . . : Wednesday, October 08, 2149 12:57:05 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 253759610
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B4-B0-D7-04-7D-7B-8B-83-CF
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled

That section of the post tells me that you're connected via wireless. According to the pic you posted, there don't seem to be any problems with the unidentified network, because you're not connected to it. However, I'd like to see the top portion of the first picture you posted. I don't believe your system is connected via ethernet, at all. In fact, the second picture tends to confirm that.

Having said that, check the connection at both ends to confirm that something hasn't become unplugged. Be sure that all of the pins at the connectors are not bent or damaged. Change the port that the ethernet is plugged to, at the router... Things like that.

 

[chev65]

From what I see the router requires a reset. Should be a reset button on the router for this or just unplugging the router for a few minutes can work.

It's fairly typical for either the wireless or the Ethernet to go out separately on a router.

 

[Shadowjk]

Some great help already here Just thought to add that the DHCP lease for your wireless connection is unbelievably high! Over time it is possible for you to have exhausted all possible leases because of that, so that may be an issue.

Lease Obtained. . . . . . . . . . : Sunday, September 01, 2013 3:40:11 AM
Lease Expires . . . . . . . . . . : Wednesday, October 08, 2149 12:57:05 PM

   Note

Restarting the router/modem as previously stated should remove any DHCP leases active and solve the issue temporarily.

Last thing I just wanted to add is to try and temporarily disable your firewall since it possible for it to block DHCP offers.

Josh

 

[chev65]

Some great help already here Just thought to add that the DHCP lease for your wireless connection is unbelievably high! Over time it is possible for you to have exhausted all possible leases because of that, so that may be an issue.

Lease Obtained. . . . . . . . . . : Sunday, September 01, 2013 3:40:11 AM
Lease Expires . . . . . . . . . . : Wednesday, October 08, 2149 12:57:05 PM

   Note

Restarting the router/modem as previously stated should remove any DHCP leases active and solve the issue temporarily.

Last thing I just wanted to add is to try and temporarily disable your firewall since it possible for it to block DHCP offers.

Josh

Mine says the same thing Josh, I believe it has to do with the machine being on the DHCP reservation list with makes it so that the IP has a lease that never expires.

Of course resetting the router will change that unless a router configuration file is first created.

 

[Shadowjk]

Ahh, forgot about reservation lists... Typically I don't use them and assign statics outside the range. All I can think of with this is either a firewall issue (Unlikely since one was obtained already) or DNS getting in the way and preventing another DHCP lease for the ethernet interface because a reserved one used for that machine (defined by hostname) is already in use on the Wireless card.

Just my thought,
Josh

 

[chev65]

Ahh, forgot about reservation lists... Typically I don't use them and assign statics outside the range. All I can think of with this is either a firewall issue (Unlikely since one was obtained already) or DNS getting in the way and preventing another DHCP lease for the ethernet interface because a reserved one used for that machine (defined by hostname) is already in use on the Wireless card.

Just my thought,
Josh

I'm just one of those let the router do everything guys.

I also set up my DNS on the router, it's just much easier this way, no messing with the IPv4 properties on every single machine.

If the router crashes or requires a reset I use the .gws D-Link configuration file to restore the routers settings.

Although in this case I'm convinced that the router is the source of the problem.

It that doesn't work I have my handy IPResetALL.exe file to flush the DNS, reset TCP-ip winsock etc. The way I named this file makes it easy to see when other people use it to fix problems on other forums.

 

[Jaypowder]

Thanks for all the help, I will try some of these and tell you how it goes!

 

[Jaypowder]

Ok so I have reset my router and the problem still persists. I also have tried other ports on the router. Could it be with the computer? Here are some pictures that may provide information

Also could this problem be from the port on the computer? I have had this issue before and to fix it I just installed protocol and it fixed it. But it has happened again and even if I reinstall protocol it still persists. I really need help!
Thanks!

 

[Shadowjk]

Do you have any DHCP reservations on your router for your machine? If so, please remove them as these could cause issues.

You said you installed a protocol? What was it? Messing with TCP/IP can cause issues and you may need to re-install your network driver in order for it to be restored.

Josh

 

[Jaypowder]

The protocol was Reliable Multicast Protocol. And I don't have any DHCP reservations. Not that I know of atleast.

 

[Shadowjk]

Hmmm... Just a test to see if any third party applications are messing things up. Can you temporarily disable your firewall and A/V application and then boot your machine into Safe Mode with Networking. After that test connectivity.

http://www.sevenforums.com/tutorials/69585-safe-mode.html

   Note

Please replace all references of Safe Mode with Safe Mode with Networking

Do any other machines experience issues similar to this? If so are they wired or wireless?

Also, have you reset your router back to factory default settings at all? As previously stated it may be an issue on your routers side

Josh

 

[Jaypowder]

I do not think it is a issue with the router because the ethernet cable works fine on other computers. And I will try disabling firewall and AV
​

 

[Shadowjk]

The cable works fine because your machine is detecting it Your router may not be sending a valid IP configuration, that is why it is a suspect.

Josh

 

[chev65]

I do not think it is a issue with the router because the ethernet cable works fine on other computers. And I will try disabling firewall and AV
​

Did you ever run the IPReset file that I posted earlier, that can sometimes fix this problem although there are other possible causes, many of which are posted in the comments section in the following link.

You might also try typing in the default gateway manually into the IPv4 properties per the instructions in the link. Very common problem but with many possible solutions.

Windows 7 Unidentified Network, Limited Access, No Internet Connection Problem Resolved