Forum Discussion
Windows Server 2022 Unable to restart 'Network Location Awareness' Service
bradcope Same issue here, and NLS is messing with NIC firewall profile as well: some of my NICs are switched from domain profile to public profile...
@bradcope , Same for me too. On my server 2022 DC, the "nlasvc" service doesn't even have Active Directory Domain Services as a dependency. And my NIC profile is set to Private. I did try and run "sc config NlaSvc depend=NSI/RpcSs/TcpIP/Dhcp/Eventlog/Netlogon/DNS/NTDS" from an elevated CMD prompt, which succeeded, but I am unable to restart the NLASVC due to an "Error 1601: The service cannot accept control messages at this time."
- Any luck figuring this out? I run into the issue w/ restarting NLA often and have no issues doing so in any version of server prior to 2022. I have a clean install ADDC that does this. I have found that disabling IPv6 has been the only solution for me. That or I kill the service PID. I don't want to have to do this every time I reboot this server. I'm using Switch Embedded Teaming
A little trick I'm using right now is just to enable or disable IPv6 and then reverse. I don't use IPv6 so i will check the box to enable and then disable. I am now appearing on the appropriate network.
Thanks
DaveTT_Vert Hi Dave, I managed to fix mine by adding the DNS suffix on my IPV4 adapter. Now my DC boots to Domain Network on every reboot.
IPV4 Properties > General > Advanced > DNS > Register Suffix for this connection (add your domain name e.g. "domain.local").
I also set the Network Location Awareness service to "Delayed Start"
Hope the above helps.
Thank you for that. I did add that to my biggest problem child 2022 server and it seems to have worked. Going to try that on a few more servers and see if it resolves it. I appreciate you taking the time to mention this. Shocking MS doesn't have any official solution to this like you do.
Dave
