Forum Discussion
ViolentCrow
Oct 08, 2023Copper Contributor
Domain Controller showing network connection as Public
Notice for quite awhile now with the vnext server builds that when you promote it to domain controller it shows the network connections as public or private instead of DomainAuthenticated. Is the...
rpaz61
Jul 09, 2024Copper Contributor
This happened to a client that has two DCs. I found a solution that dates back to Nov 2014:
1. Set the Network Location Awareness service to 'Automatic (delayed start)'.
2. Double-check Network Location Awareness service existing dependencies by running: "sc qc nlasvc" from an elevated command prompt.
3. Add the following dependencies to the Network Location Awareness service: DNS and NTDS. To do so from elevated command prompt:
sc config nlasvc depend=NSI/RpcSs/TcpIp/Dhcp/Eventlog/DNS/NTDS
4. Reboot the domain controller. Once the domain controller is up and running, verify that the Windows Firewall is connected to "Domain networks".
1. Set the Network Location Awareness service to 'Automatic (delayed start)'.
2. Double-check Network Location Awareness service existing dependencies by running: "sc qc nlasvc" from an elevated command prompt.
3. Add the following dependencies to the Network Location Awareness service: DNS and NTDS. To do so from elevated command prompt:
sc config nlasvc depend=NSI/RpcSs/TcpIp/Dhcp/Eventlog/DNS/NTDS
4. Reboot the domain controller. Once the domain controller is up and running, verify that the Windows Firewall is connected to "Domain networks".
- Jaimito_0433Sep 05, 2024Copper Contributor
rpaz61 - Thnx for this. Worked perfectly. 👍
- ChrisAtMafSep 06, 2024Steel ContributorVery common issue - see the accepted answer here https://learn.microsoft.com/en-us/answers/questions/400385/network-location-awareness-not-detecting-domain-ne