Forum Discussion
Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"
MicrosoftWhen the fix is published, it will be listed in the relevant KB but there is no separate public documentation for this issue currently.
pathetic
Do not expect any fix. This problem has been known for ages, and all they did was making it worse. Read e.g. these 2021 threads:
https://www.reddit.com/r/sysadmin/comments/p86mjb/has_anyone_else_had_problems_with_nla_on_server/
https://learn.microsoft.com/en-us/answers/questions/400385/network-location-awareness-not-detecting-domain-ne
Different issue, unrelated to NLA (which is not used in the same way in 2025 and isn't even started/automatic), but you're spot on about the "do not expect any fix" part. Typical post-covid Microsheet.
We've been fighting this for years. I can tell you it absolutely is related to NLA and the bad workflow regarding how Windows determines network profiles and never bothers to re-check until you pull the network plug. I'm just testing 2025 so I accidentally hit this thread, years after we've experienced the problem.
I frankly wouldn't give a heck about whether the network location is detected as domain, public, private, uknown or Deep Space 9, except that it breaks things heavily due to incorrect firewall profile being applied.
