Score:1

Windows Firewall selects wrong profile after restart (PRIVATE / PUBLIC / DOMAIN)

in flag

At some servers we have the problem that after restart Windows Server selects a PRIVATE domain profile in stead of DOMAIN.

enter image description here

enter image description here

We can solve the problem by resetting the Network Adapater:

Restart-NetAdapter Ethernet0

Does anyone have a permanent solution?

We tried:

  1. Run the Powershell script above a couple of minutes after boot (using Task Scheduler), but that somehow doesn't work.

  2. Verified that the Domain Controller can be found using

nltest /dsgetdc:domain.lan

  1. Verified that DNS was able to find the domain-controllers:

nslookup _ldap._tcp.dc._msdcs.domain.lan

I'm also aware of some registry-settings that can be modified (NegativeCachePeriod, AlwaysExpectDomainControllert and AlwaysExpectDomainController) as stated here: https://learn.microsoft.com/en-us/answers/questions/400385/network-location-awareness-not-detecting-domain-ne.html but I didn't want to just try this in a production environment.

I have once reserved an entire evening to try a couple of suggestions on a production server with this issue and that evening I could restart the server multiple times without the problem happening at all. So it's difficult to replicate.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.