HELP! NO Teachers laptops can login Network mis-identified

[chazzy2501]

OK, all the teacher laptops think they're not connected to the domain! The NLA places them in the guest or private network, as the firewall rules are pretty strict they can not connect to SMB shares or the internet!

 

I've taken a few laptops and restarted the NLA service but it places the laptops back into guest. The laptops all have correct ip settings, can ping all servers (I left the ICMP thank goodness) The firewall settings haven't changed in over a month (according to the GPO) so I think a short powercut on Saturday has changed something about the network that confuses the NLA service... Servers and all wired machines fine, pupil laptops (with no public or private firewall settings configured as they don't go off site) correctly identify the network. (this maybe due to the firewall being able to remediate if at first it incorrectly identifies)

 

I*n summary:

 

Anyhow what do I need todo to get them to correctly identify the network? This happens to only teacher laptops that have restricted private and guest settings (in the firewall) on wired or wireless networking. The firewall settings haven't been altered recently.

 

wih

[ReadTheNetwork]

Have you resolved this? Did you look at the certificate? Also long shot but do you use Direct Access?

[Duke5A]

Give this a read: https://blogs.technet.microsoft.com/networking/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles/

 

It's a lot of fun during power burps if your domain controllers don't come up before everything else does. Other servers and clients sometimes get stuck on the public firewall profile and lock everything down as a result.

 

Give a look under the Local Security Policy editor on the laptop. Under 'Network List Manager Policies' you should be able to alter location settings for previously identified networks. I guess you could try deleting the registry key for the network too and let the system try and identify it again.

 

HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Group Policy\History\NetworkName

[mattpant]

Hi,

 

Did you find a fix for this, I’ve gone into work today with exactly the same issue!! Reading the original post was almost as if I had written it based on what I found today!

 

Devices showing up as Guest / Private and not Domain.

 

We do use DirectAccess.

 

Help?!?!?

 

Matt

[mattpant]

Sorted - it turned out with our issue that the councils certificate had expired on the NLS server which was causing the issue! New certificate created and we were back in business!