I've run into a problem that a fair few people seem to encounter on Windows: "Unidentified Network, no connection"
Let's put the situation into context:
I've built a nice shiny new AM4 desktop. When I boot into Linux from a USB stick, my connection is lovely and fine. However, when I boot from my freshly installed copy of Windows 10 (Education, 1607, and normal, 1703), I get the error. The machine goes via Homeplugs, but also has the same issue when I connect directly to the router by ethernet (BT Smart hub). I've been reading about this for some time, and so far I have tried:
- Reinstalling Windows
- Installing the latest network driver from the motherboard manufacturer, from Realtek, and uninstalling the driver and letting Windows work
- Factory reset of router
- Disabling IPv6
- Setting a static IP
ipconfig /release
throws an error: an address has not yet been associated with the network endpointnetsh int ip reset resetlog.txt
did not help- network discovery set to on
- I turned off fast startup, didn't help
- Using secpol.msc, I forced networks to be set to private
- I stopped the DHCP service, and rebooted
Now, given that these didn't work, I did a bit of snooping around the network as well:
- When plugged in, the ethernet cable power light is on, and when it is plugged in for the first time, the activity light blinks for a few seconds
- I cannot ping the router, but:
- The router does have events registered when I connect:
18:52:57, 10 Jul.
BR_LAN:LAN Neighbor Discovery : Host fe80::71f4:88fe:ad1a:4dbc is set active
18:53:59, 10 Jul.
BR_LAN:DHCPv6 message : Advertise , LAN DHCPv6 Client: fe80::71f4:88fe:ad1a:4dbc
18:53:59, 10 Jul.
BR_LAN:DHCPv6 message : Solicit , LAN DHCPv6 Client: fe80::71f4:88fe:ad1a:4dbc
- and packets are sent and received according to Windows (though, very few indeed)
My ipconfig \all is pasted below:
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-II0VBEU
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 70-85-C2-3D-32-84
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.77.188(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{3F7D1273-E153-462E-9400-6282528ADCA6}:
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
I do not believe this to be driven by any bugs on 1607 because of the repeated failure in 1703.
Do you know of any further solutions?
Many thanks for the help!
169.254.x.x
, so it's definitely having some sort of issue communicating with DHCP. I would double check your adapter settings to make sure it's set to assign and IP address automatically? I guess you could also try to reinstall your network drivers on Windows. I'll try to think of a few other things to try out