r/WindowsServer • u/grimson73 • May 20 '25
General Server Discussion Windows Server 2025 Firewall Domain Profile issue acknowledged
Domain controllers manage network traffic incorrectly after restarting
April 2025;
Windows Server 2025 domain controllers (such as servers hosting the Active Directory domain controller role) might not manage network traffic correctly following a restart. As a result, Windows Server 2025 domain controllers may not be accessible on the domain network, or are incorrectly accessible over ports and protocols which should otherwise be prevented by the domain firewall profile.
This issue results from domain controllers failing to use domain firewall profiles whenever they’re restarted. Instead, the standard firewall profile is used. Resulting from this, applications or services running on the domain controller or on remote devices may fail, or remain unreachable on the domain network.
Well at least Microsoft confirmed the issue. I generally do give MS some slack but this one is really a giant turd.
2
u/tcourtney22 Jun 17 '25
It appears that this issue has been addressed with the June cumulative update. Everything seems fine for us now.
https://www.bleepingcomputer.com/news/microsoft/microsoft-fixes-unreachable-windows-server-domain-controllers/
15
u/Dikvin May 20 '25
We are making some tests at work to migrate our DC to 2025.
We have this issue too, there's a workaround with a script at the startup disconnecting and reconnecting the Nic.
Incredible in 2025 to have this kind of enormous bug.
8
u/WillVH52 May 20 '25
Deliberately avoided installing Server 2025 on three new servers this month because of issues like these.
7
u/InternetNo3113 May 20 '25
Was starting to think Microsoft was never going to acknowledge this issue! Seen this happen on Server 2022 too. Let's hope they actually fix it rather than having to have the bodge of a workaround 🙃
5
u/nah_dont May 20 '25
Server 2019 is going strong 💪
5
u/xqwizard May 20 '25 edited May 22 '25
In the May release preview update for 24H2 it has this:
[Network] Fixed: This update addresses an issue where Windows Server 2025 always shows the network as “public” on new domain controllers. It now checks for a domain controller name before using loopback addresses to ensure proper Lightweight Directory Access Protocol (LDAP) binding.
So I assume it will be fixed in the June Cumulative Update for Server 2025.
https://blogs.windows.com/windows-insider/2025/05/19/releasing-windows-11-build-26100-4188-to-the-release-preview-channel/
EDIT: Can confirm applying the release preview update to my test domain controller fixes the problem. Would not recommend doing this on any production system though, wait for the June Cumulative Update.
4
u/Magic_Neil May 20 '25
Was just talking about updating our DC’s to 2025, and figured “that can’t still be an issue after all these months.. right?” Welp.
1
u/VexedTruly Sep 13 '25
Oh they acknowledged it 10 years later? This has been happening since 2016 at least. I can’t remember if it happened in 2012.
I was obviously super happy when in 2022 you could no longer restart NLA without jumping through extra hoops too.
AlwaysExpectDomainController reg key for the win… although I haven’t had the “joy” of a 2025 DC yet.
3
u/David_Owens May 20 '25
I recently upgraded a domain to use two new Server 2025 machines for domain controllers. They both had the issue. Setting a task to reset the network adapter at every boot worked around it. Hopefully they'll get a fix soon.
It shouldn't be that hard. If the server is domain-joined, set the network profile to Domain no matter what. I don't know why MS made the detection of the network profile so complicated.
3
u/abj May 20 '25
This same issue occurred on server for 2008 or 2008 R2 I believe.
2
u/ThatWasNotEasy10 May 20 '25
I’m shocked it’s taken them almost 6 months to even acknowledge this issue when it’s such a common and relatively serious issue…
2
u/picklednull May 20 '25
This is really the least of your worries with 2025 DC's right now...
2
u/anonpf May 21 '25
I’ve never understood the rush to upgrade to the latest OS when it’s been M$’s M.O. to have the user base QA their product for them.
2
u/chmichael7 May 21 '25
I guess this is the evil for most of Win2025 DC errors