Forum Discussion
Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"
MicrosoftThank you everyone for reporting this issue! A fix for it is in the works and should be coming soon. In the meantime, resetting the network adaptor by running "restart-netadapter *" OR "Restart-Service NlaSvc -Force" via PowerShell or CMD Prompt is a workaround.
I appreciate a functional workaround, but this issue has been present (particularly for single DCs) for many years now. Previously, the solution was restarting the "Network Location Awareness" service.
One of Microsoft's biggest and oldest server features should not be broken out of the box for this long!
Fix is "in the works"? Wow, just wow! ! I mean, this issue has been reported ever since Server 2022 has been released (Google "AlwaysExpectDomainController" to get a clue, perhaps), lots of people opened a case with MS to no avails as usual. In fact, MS has done nothing but making the problem even worse by making the restart of nlasvc impossible / broken even in 2022 somewhere mid-2023 (the Services console does not work, the PS command you suggest does not work if you bothered to test, the only way to restart the process is to forcefully kill the process).
In addition, MS has broken the known registry workarounds floating around the internet in Server 2025.
Now you come with restarting network adapters hack. Sheeesh. Get your act together, seriously.
🤯
Hi Eleanor, I have a case open with the product team, and it has been escalated, but would you mind telling them to add this little issue to that bug list, it's not present on that list. Thanks in advance!
- Eleanor_Little
Unfortunately, I can't ask for your case to be updated or provide issue details about your case to the product team on your behalf. You will want to update and provide information yourself about the issue if you are experiencing it in your open case.
Yes, it has been reported since April 2024, when Windows Server was still in Preview (Beta). And Microsoft realizes it now!!! What support and customer service!!! Thank goodness Microsoft listens to users.
Where is this issue publicly addressed so that we can track the progress of the fix?
- Eleanor_Little
When the fix is published, it will be listed in the relevant KB but there is no separate public documentation for this issue currently.
pathetic
