Network Location Changing on Domained and undomained machines randomly


  1. Posts : 3
    Windows 10
       #1

    Network Location Changing on Domained and undomained machines randomly


    Hello,
    What is going on with Windows 10 and Netowork locations? I work in an enterprise environment and have computers that are domained and some that are not. About 3 or 4 machines out of the 30 or so that run Windows 10 have weird network location issues. There is one machine that is not on the domain running WinX Education 64bit and every time the only local user profile on the machine logs in it sets both Ethernet connections as Public. One ethernet on that machine is to the network and is DHCP and the other is to a piece of DAQ equipment with a static address. I have the set-netconnectionprofile... powershell command in a batch running off task scheduler, but takes time in startup to run the script, so file share and net discovery are active. I know the work around, but what is the problem? I also had a machine that is on the domain show up as a public net location after login. It showed the connection to the domain, but net location was public. I don't have any Group Policy rules pertaining to net locations as it has not been an issue until winX started making it's rounds. I have over 100 machines on this floor and 6 VLANs, so I see a decent cross section of issues, but I cannot find any information other than workarounds or how to's on setting the net location. I want the root of the problem. Anyone?

    Thanks in advance!
      My Computer


  2. Posts : 3
    Windows 10
    Thread Starter
       #2

    Ok, I dug further and found my own answer. The issue is in a service called Network Location Awareness. What can happen on login or config change of a connection is that NLA will check and reset the location to public if it unsure what kind of network it is connected to. Public network location setting will cut off Network discovery, fileshare and locks down the firewall. Anyways what can happen is upon login if your domain controller or another server is slow to respond to the location inquiry from NLA it will automatically go into a Public location and lock down everything making you either reset the location with powershell or unjoin and rejoin the domain. ANNOYING!
    HOW TO FIX
    Push windows key + r
    type services.msc press enter
    scroll down to Network Location Awareness in the list on the right hand side and double click
    In the dialogue box you should see a drop down menu set to Automatic
    Click that drop down and set it to Automatic Delayed or Manual and click apply then exit out of services.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:11.
Find Us




Windows 10 Forums