Network Location Awareness not Detecting Domain Network from Offsite Location

Ftr16

The issue occurred after we started migrating our offsite workstations to Win 10. After joining computers to domain, computers show unidentified network connection instead of domain network connection. Computer is located at offsite location and was migrating to Windows 10. NLA is working normally when it was still Windows 7 workstations.

Network Profile is Showing as Private Instead of DomainAuthenticated in Domain Controller

Ftr16

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.