Today I decided to dig into this further to see if I could come up with a better solution. Using a script allows doing this even when connected remotely, but it’s awkward and you have to customize the interface name for each PC. Netsh interface set interface 'Ethernet' enabled Netsh interface set interface 'Ethernet' disabled In fact I have script a RestartNetworkAdapter.cmd on many computers to do just that:
The only sure way that I have found to force the NLA service to re-detect the domain is to stop and restart the network adapter. That doesn’t work because the Network List Service depends on the NLA service, and the Network List Service, for some reason, can’t be stopped. That’s has not been enough in this environment.Īt least one article suggests restarting the NLA service. Several articles suggest changing the NLA service to “Automatic (Delayed Start)”. The problem, of course, is that the Network Location Awareness (NLA) service can’t determine that the machine is on a domain, so it falls back to Public: Some desktops, especially those that have are behind a couple switches, often have problems confirming that they are on the domain, so they come up on the Public network, which messes up RDP connections. One small client has a Server 2012 R2 Essentials domain controller and a few Windows 7 desktops.