Forum Discussion
BehBeh55
Dec 04, 2019Copper Contributor
Unidentified Network
in every member windows server 2012R2,2016 box we experience the following, after a reboot, The network profile changes to public from domain. if I restart the "Network Location Awareness" service"...
Dave Patrick
Dec 05, 2019MVP
When NLA starts to detect the network location, the machine will contact a domain controller via port 389. If this detection is successful, it will get the domain firewall profile (allowing for correct ports) and we cannot change the network location profile. If the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.
So I'd check the domain controller and problem client have the static address of DC listed for DNS and no others such as router or public DNS
You can also try restarting the Network Location Awareness service then check the profile again. Its possible on the first DC that NLA did checks before active directory domain services were available.