Forum Discussion
Windows Server 2019 warns No Internet Access after AD, DNS and DHCP setup
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
Jason_Pitts Yes, that command solved my problems, but AFAIK there is a problem using it like that:
sc config nlasvc depend= DNS
It overwrites all dependencies the service currently has. So if you want to add and not overwrite the service's dependencies list, a solution would be first to get the dependencies list, runnig this command:
sc qc nlasvc
That outputs this:
SERVICE_NAME: nlasvc
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:\Windows\System32\svchost.exe -k NetworkService -p
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : Network Location Awareness
DEPENDENCIES : NSI
: RpcSs
: TcpIp
: Dhcp
: Eventlog
SERVICE_START_NAME : NT AUTHORITY\NetworkService
Secondly run this command to add DNS:
sc config nlasvc depend= NSI/RpcSs/TcpIp/Dhcp/Eventlog/DNS
Please, let me know if I am wrong.
- johntheproJun 01, 2023Copper Contributor
m32po you are correct, that would be the right way to ensure that nothing was removed inadvertently.
In the case of the NLA service, it has no dependencies by default, so nothing to worry about here.
- AnonymousJul 23, 2023What about "Network List Service" as a dependency?