Forum Discussion
Luigi_Iotti
Mar 13, 2020Copper Contributor
Windows Server 2019 warns No Internet Access after AD, DNS and DHCP setup
Hi all. I have a Windows Server 2019 VM (HyperV) where I setup my first DC. I also setup DNS and DHCP on the server. After deploying these, the yellow warning icon appeared on the network icon in...
Jason_Pitts
Apr 13, 2021Copper Contributor
Luigi_Iottitry restarting the Network Location Awareness service and allow it to restart the Network List service automatically. If it solves the warning then it's because the Network Location Awareness service is starting before DNS. You can fix this by creating a dependency using the following command from an elevated command prompt:
sc config nlasvc depend=DNS
nealcoff
Oct 04, 2021Copper Contributor
1. Press Windows + R keys.
2. Type regedit, click OK.
3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet.
4. Make sure following values exist in right pane of Internet:
"ActiveDnsProbeContent"="8.8.4.4"
"ActiveDnsProbeContentV6"="2001:4860:4860::8844"
"ActiveDnsProbeHost"="dns.google"
"ActiveDnsProbeHostV6"="dns.google"
"ActiveWebProbeHostV6"="www.msftconnecttest.com"
"EnableActiveProbing"="1"
5. Restart Network Location Awareness service
Referenced from: Arash.Dargahi
On domain controllers using 127.0.0.1 as their primary DNS, run the following:
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\Windows\NetworkConnectivityStatusIndicator" /v UseGlobalDNS /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\Windows\NetworkConnectivityStatusIndicator" /v NoActiveProbe /t REG_DWORD /d 0 /f