So now I am happy I have solved the issue and I hope anyone else who is having such issue will find this useful.Once connected you need to configure the two Ethernet adapters to be able to communicate. Today I upgraded two systems and having removed my local DNS server from the adapter configuration – no 127.0.0.1 or ::1 for the DNS server entries (those were overriding the DHCP defined entries from the router) I also commented out the references to 127.0.0.0/8 and ::1 : x.x.x.x(Preferred)įor the DNS server entries then the networking worked correctly if I also set the “interface:” and “access_control” definitions in the unbound configuration file to the same addresses That said, if I changed the Adapter configuration so that it pointed to the IPV4 and IPV6 address the IPCONFIG /ALL I don’t know if this is intentional on MS’s behalf or a bug – time will perhaps tell. I did this and then played with the Unbound configuration.Īny reference to 127.0.0.x or ::1 for DNS entries in the Adapter configuration causes the networking to fail to detect internet access is available. I use Macrium Reflect as backup software and that allows me to take a backup and then convert that into a VM.
This got me thinking and I have now upgraded my desktop to V2004 again and low and behold – networking issues. This apparently has been the case sine the end of July. Where blocking MS telemetry IP addresses (DNS Names) via the hosts file would cause Windows Defender to complain that the hosts file had been “infected” and would return it to defaults depending on how you answered Defenders prompt. I could never get it to show the little TV screen icon to say networking was up and running and the internet was fully accessible. The little system tray icon always showed the little world icon (as I call it) to say no internet access. Windows thought that it was not connected to the internet. Since the Windows 10 V2004 update has been out and about, every time I have upgraded a system I have had issues with the networking. This reply was modified 1 year, 5 months ago by RayG. Looks like it will be a while before it gets fixed – not sure how long it will work for time will tell. It seems it is a Microsoft Driver Issue See this link: Windows then decided it wanted to update the WiFi Adapter Driver – and then it looks like the install fails (each time) and when that happens things go wrong. I then uninstalled and removed the drivers when prompted all the items in device manager under the network branch and rebooted. I then uninstalled the Sandbox rebooted and that made no difference either. However changing them made no difference.
What I did find however was the when the Windows Sandbox is installed it runs a Hyper-V virtual adapter which does have those options.
Tried your suggestions but the WiFi adapter does not have those options.
0 kommentar(er)
