Unidentified Network, Wired(Ethernet adapter) Windows 7

razorback71854 · May 14, 2015

I recently upgraded my network router, and so far, all of my devices are able to connect to the internet fine (wifi and wired) with the exception of this one PC. I am able to connect with a wifi adapter, but the connection is weak and unsuitable for video streaming/gaming.

I am running Windows 7 Home Premium, My ethernet adapter says "Unidentified Network" (Set as public). No network access.

I have googled this issue and tried every solution possible with no luck. The router I recently installed is a Linksys AC1900. I'm almost at the point that I'm willing to call the linksys help desk and suffer through their script.

Here are the results of my ipconfig /all: (The bold part is the adapter that is giving me problems)
Windows IP Configuration

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

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-49-B8-C2-FA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Adapter
Physical Address. . . . . . . . . : 00-40-05-08-16-B5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3489:19ce:2093:f5bb%27(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.245.187(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 570441733
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-65-F8-48-BC-AE-C5-B3-1F-9D

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 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 6A-FD-B9-5F-5E-42
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 2.4GHz Wireless Lite-N PCI-E Adapter
Physical Address. . . . . . . . . : 6C-FD-B9-5F-5E-42
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::481e:1c42:7b37:db8b%21(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.107(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, May 14, 2015 7:39:32 AM
Lease Expires . . . . . . . . . . : Friday, May 15, 2015 7:39:33 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 594345401
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-65-F8-48-BC-AE-C5-B3-1F-9D

DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{726C5DA0-A02F-4894-B425-2FA8C7AD4D25}:

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 isatap.{49B8C2FA-72D2-4AA9-A1C7-1785F17E4AF9}:

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

Tunnel adapter Reusable ISATAP Interface {CA72A7F5-9B6E-46DB-8FD5-92A275E586E2}:

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

Tunnel adapter Local Area Connection* 22:

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
IPv6 Address. . . . . . . . . . . : 2001:0:5cf2:8c44:1cad:180f:3f57:fe94(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::1cad:180f:3f57:fe94%23(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{08D774C9-CC24-4E36-B098-111C2F35A6B8}:

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

Tunnel adapter isatap.{34170C6E-1E7C-45B6-B812-EEF5D7368CA4}:

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

Ralston18 · May 14, 2015

Razor,

You need to reconfigure Ethernet Adapter Local Area Connection #2.

Go to Control Panel, Network & Internet, Network Connections.

Right click that adapter and go into properties.

Look at the IPv4 and IPv6 properties. Make sure they are set to automatically obtain a DHCP IP and DNS server automatically.

It appears that the adapter is still looking for the original router or modem/router based on the configuration information in the "bold" area of your ipconfig.

The ipconfig information should be much the same as ipconfig shows for one of your other wired devices.

razorback71854 · May 14, 2015

Ralston18 :

I verified that both connections are setup to automatically obtain a DHCP IP and DNS server. Disabled both and re-enabled the 3 connection first. I'm still getting an unidentified network.

Ralston18 · May 14, 2015

Razor,

Thanks.

Just re-read and realized I mistyped the adapter reference. I meant #3 (DLink PCI adapter) not #2. My error and my apologies...

Anyway you apparently caught my error and actually verified #3.

Also, with respect to Ethernet Connection #2 (two) that seems to be for a VPN (Open VPN). Unless you are really using VPN I think that #2 can be disabled or uninstalled. References: Google ---> TAP-Win32 Adapter V9.

Going back to Ethernet Adapter #3. Can you ping 169.254.245.187? Can you ping 192.168.1.1? What does tracert show for each ip?
I also googled 169.254.245.187 - assigned to BOGONS which, I read, are addresses associated with VPNs and a source of DDOS attacks.

It still appears to me that Ethernet Adapter Local Area Connection #3 is misconfigured. Either your changes are not being saved or they are being saved and then getting changed back to the ipconfig by some other means - possibly malware or a virus maybe...

Ethernet Adapter #3 should be going to your router (192.168.1.1) as a physical wired connection etc.. The ipconfig /all should show that once the adapter settings are corrected and permanently configured. If the adapter settings do not remain as expected then that issue can be addressed.

Please let me know. Thanks.

razorback71854 · May 14, 2015

Ralston18 :

Ethernet Connection #2 is used by a VPN, however I have disabled it for the time being while I'm seeking a solution to this issue.

I am not picking up any viruses with MSE. I haven't ran a spyware scan recently, so I will do that.

I specified the following changes in my adapters settings for IPv4, So it is saving what I put in manually.
Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Adapter
Physical Address. . . . . . . . . : 00-40-05-08-16-B5
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3489:19ce:2093:f5bb%27(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.110(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 570441733
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-65-F8-48-BC-AE-C5-B3-1F-9D

DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
(Still getting Unidentified Network)

Here are the results of ping and tracert to 169.254.245.187 and 192.168.1.1 (Before I manually entered the IPv4 settings)
Tracing route to USER-PC [169.254.245.187]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms USER-PC [169.254.245.187]

Trace complete.

C:\Users\USER>ping 169.254.245.187

Pinging 169.254.245.187 with 32 bytes of data:
Reply from 169.254.245.187: bytes=32 time<1ms TTL=128
Reply from 169.254.245.187: bytes=32 time<1ms TTL=128
Reply from 169.254.245.187: bytes=32 time<1ms TTL=128
Reply from 169.254.245.187: bytes=32 time<1ms TTL=128

Ping statistics for 169.254.245.187:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Tracing route to 192.168.1.1 over a maximum of 30 hops

1 192.168.1.107 reports: Destination host unreachable.

Trace complete.

C:\Users\USER>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.107: Destination host unreachable.
Reply from 192.168.1.107: Destination host unreachable.
Reply from 192.168.1.107: Destination host unreachable.
Reply from 192.168.1.107: Destination host unreachable.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

AND AFTER
Ping to 192.168.1.1 and 192.168.1.110
C:\Users\USER>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.110: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.110: Destination host unreachable.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

C:\Users\USER>ping 192.168.1.110

Pinging 192.168.1.110 with 32 bytes of data:
Reply from 192.168.1.110: bytes=32 time<1ms TTL=128
Reply from 192.168.1.110: bytes=32 time<1ms TTL=128
Reply from 192.168.1.110: bytes=32 time<1ms TTL=128
Reply from 192.168.1.110: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Tracert to 192.168.1.1 and 192.168.1.110
Tracing route to 192.168.1.1 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * USER-PC [192.168.1.110] reports: Destination host unre
achable.

Trace complete.

Tracing route to USER-PC [192.168.1.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms USER-PC [192.168.1.110]

Trace complete.

Ralston18 · May 14, 2015

Before:

You could ping 169.254.245.187 (USER) and get a reply.
You could ping 192.168.1.1 (normally the 1900AC router) and get "Destination host unreachable" per the reply from 192.168.1.107

Then you configured adapter #3 to no DHCP and set a static IP of 192.168.1.110. Was that your intent? (Per your manual changes.)

Pinging and tracert to 169.254.245.187 are now moot. That ip is no longer applicable with respect to adapter #3's configuration.

After:

You then pinged 192.168.1.1 and the router is unreachable and 2 out of 4 packets are lost.
tracert to 192.168.1.1 timed out as "Destination host unreachable"

Flush the dns cache (ipconfig /flushdns etc.) and then try the pings and tracert again. Thanks.

razorback71854 · May 14, 2015

Ralston18 :

Flushed DNS..

Ping to default gateway: 3 packets timed out, one reply from 192.168.1.110 (Destination Host unreachable)
Ping to 192.168.1.110: Successful No packets lost.
Tracert to default gateway: First 3 hops all packets timed out. Fourth hop, reply from 192.168.1.110 (Destination Host unreachable).

Ralston18 · May 14, 2015

Razor,

Thanks. I appreciate your patience...

Anyway this "Unidentified Network - Unable to Connect" problem is not at all uncommon. Seems that there are various solutions but finding the one that works for a specific situation can take some effort.

I have been googling etc. (as I know that you have been doing) for possible causes and solutions. The information you have provided has been helpful but no "smoking gun" as they say. Or, if so, I am sure missing it in this case.

In your situation I think that the previous VPN configuration is a contributor even though you have disabled it. But I am questioning my original logic there.

ROUTE DELETE 0.0.0.0 worked for some people - you may want to try that if you have not already done so.

I also saw a solution that involved bridging between two selected network connections (one wired and one wireless) - smoothed things out for that person.

Someone else just simply spoofed the NIC MAC address. There was another solution that, as I understood it, disabled the IPv6 protocols.

Just not comfortable suggesting possible solutions without a specific indication that any given solution is relevant or applicable.

However, I still have one immediate thought: Can you disable and physically remove the D-Link PCI adapter and, instead, enable and try using the motherboard's built in NIC? You might have to go into BIOS to enable the built in NIC.... And/or just try another PCI adapter? Seems that the current DLink adapter (#3) is sort of at the center of things and . Pull the adapter out and see if some form of properly working wired connectivity can be established.

Sort of a fresh start to see if removing the current adapter will either solve the problem or identify the culprit.

razorback71854 · May 15, 2015

Ralston18 :

I haven't tried route delete, so I will try that. I can also completely remove the VPN installation and reinstall it later to rule that out.

I have tried bridging the connections, doing so only made things worse.
I'm not sure what you mean about spoofing the MAC address, I will try to look into that.
I am not able to try another NIC at this time, the original hardware on the Mobo failed so this is why I'm using the DLINK card (or was using it). I am not opposed to buying a new card, but I would like for that to be a last resort without further indication that it is the problem.

Update:

While attempting to spoof the MAC address I received the following error..
C:\Windows\system32>ipconfig /renew

Windows IP Configuration

An error occurred while renewing interface Local Area Connection 3 : unable to contact your DHCP server. Request has timed out.
An error occurred while releasing interface Loopback Pseudo-Interface 1 : The system cannot find the file specified.

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5b:2ec6:5fe3:bcfd%27
Autoconfiguration IPv4 Address. . : 169.254.188.253
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::481e:1c42:7b37:db8b%21
IPv4 Address. . . . . . . . . . . : 192.168.1.107
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
The error with the DCHP server explains why I'm getting an APIPA address when I try to let it acquire an IP automatically.
It would appear to me that there is some issue with the card finding the default gateway, but I don't claim to know much about networking.

Ralston18 · May 15, 2015

You are doing very well from my viewpoint. Tough problem...

Please take a look at this link:

http://superuser.com/questions/324551/stubborn-apipa-issue-possible-ipv4-problem-ipv6-okay

Seems to be a closer match to your situation than some of the other possible fixes I have found..... (Saw one fix that seemed to work if IPv6 protocol was unchecked for use. Did not seem specific enough with respect to the problem at hand.)

Do not really prefer providing just links but not going to "reinvent the wheel" either. Still felt it best to let you take a look at the link. It could help you narrow down the issue some more.

Probably need to decide at what point you will try another NIC. Since the orginal onboard hardware failed and the DLink is suspect (can you try it in another system?) then I would now work towards eliminating or identifying a hardware problem. Starting to think even more that configuration is not the problem as I originally believed. You have tried many of the configuration fixes.

Will stay open minded in any case.

And you (actually both of us) will probably end up knowing more about networking one way or the other.

Take care.

razorback71854 · May 16, 2015

Ralston18 :

Sorry for the delay, I just saw this message. I'm starting to think the NIC may be the problem as well, though I haven't tried the link you suggested yet. I will do that and post back my results, I do have another PC that I could test the Dlink NIC in, so I will go ahead and do that as well. It will probably take a day or so for me to get around to taking the card out and putting it in the other PC.

razorback71854 · May 18, 2015

The solution you linked did not fix the problem. I had planned to swap out the NIC yesterday, but work got in the way unfortunately.

I will be busy with work for the next 2-3 days as well, so It will probably be thursday before I can get around to doing that.

razorback71854 · May 21, 2015

After a bit of trial and error, I believe I've found the problem to be the network cable.

I connected my PC with the short cable that was included with the new router and it established a connection very quickly with no issues. Thanks for your help Ralston.

Search

Unidentified Network, Wired(Ethernet adapter) Windows 7

razorback71854

Reputable

Ralston18

Titan

razorback71854

Reputable

Ralston18

Titan

razorback71854

Reputable

Ralston18

Titan

razorback71854

Reputable

Ralston18

Titan

razorback71854

Reputable

Ralston18

Titan

razorback71854

Reputable

razorback71854

Reputable

razorback71854

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page