New
#1
Ethernet connection: 'unidentified network'
Hi all,
I'm yet another victim of the unidentified network Windows bug. I've had my Surface Pro 4 for two weeks now and ethernet has never worked through my docking station. Originally I thought it was a surface thing, but apparently all Windows users are confronted by it at some stage.
These are my results for ipconfig/all
C:\WINDOWS\system32>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-I7I3ODSPrimary Dns Suffix . . . . . . . :Node Type . . . . . . . . . . . . : HybridIP Routing Enabled. . . . . . . . : NoWINS Proxy Enabled. . . . . . . . : NoDNS Suffix Search List. . . . . . : telenet.be
Wireless LAN adapter LAN-verbinding* 3:
Media State . . . . . . . . . . . : Media disconnectedConnection-specific DNS Suffix . :Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual AdapterPhysical Address. . . . . . . . . : B6-AE-2B-D0-25-9BDHCP Enabled. . . . . . . . . . . : YesAutoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :Description . . . . . . . . . . . : Surface Ethernet AdapterPhysical Address. . . . . . . . . : 58-82-A8-91-1E-42DHCP Enabled. . . . . . . . . . . : YesAutoconfiguration Enabled . . . . : YesLink-local IPv6 Address . . . . . : fe80::7583:a4f1:1f9b:78d1%19(Preferred)Autoconfiguration IPv4 Address. . : 169.254.120.209(Preferred)Subnet Mask . . . . . . . . . . . : 255.255.0.0Default Gateway . . . . . . . . . :DHCPv6 IAID . . . . . . . . . . . : 425231016DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-4A-BE-3D-58-82-A8-91-1E-42DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1fec0:0:0:ffff::2%1fec0:0:0:ffff::3%1NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : telenet.beDescription . . . . . . . . . . . : Marvell AVASTAR Wireless-AC Network ControllerPhysical Address. . . . . . . . . : B4-AE-2B-D0-24-9ADHCP Enabled. . . . . . . . . . . : YesAutoconfiguration Enabled . . . . : YesLink-local IPv6 Address . . . . . : fe80::a47c:6ab5:bb9:6c7e%12(Preferred)IPv4 Address. . . . . . . . . . . : 10.114.12.181(Preferred)Subnet Mask . . . . . . . . . . . : 255.255.252.0Lease Obtained. . . . . . . . . . : 18 February 2016 23:00:37Lease Expires . . . . . . . . . . : 18 February 2016 23:25:29Default Gateway . . . . . . . . . : 10.114.12.1DHCP Server . . . . . . . . . . . : 195.130.137.17DHCPv6 IAID . . . . . . . . . . . : 62172715DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-4A-BE-3D-58-82-A8-91-1E-42DNS Servers . . . . . . . . . . . : 195.130.131.134195.130.130.134NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.telenet.be:
Media State . . . . . . . . . . . : Media disconnectedConnection-specific DNS Suffix . : telenet.beDescription . . . . . . . . . . . : Microsoft ISATAP Adapter #8Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP Enabled. . . . . . . . . . . : NoAutoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{FCBE9E9E-8488-4FAD-BAD9-0579C1A548AD}:
Media State . . . . . . . . . . . : Media disconnectedConnection-specific DNS Suffix . :Description . . . . . . . . . . . : Microsoft ISATAP Adapter #9Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0DHCP Enabled. . . . . . . . . . . : NoAutoconfiguration Enabled . . . . : Yes
The media disconnected message has no particular meaning, as my network adapter detects an ethernet plug. It simply cannot be identified. Troubleshooting gives me the following message: "ethernet" does not have a valid IP configuration.
I checked multiple times and the IP and DNS addresses are set to automatic.
Things that didn't help
- ipconfig/release and ipconfig/renew
- disabling and reenabling the ethernet adapter
- resetting winsock
- resetting ipv4 and ipv6
- reinstalling the ethernet adapter
Incredibly frustrating stuff. Thanks in advance!
Simon