Forum Discussion
When is Network Profile Issue for Domain Controllers going to be at least acknowledged?
I did hear back from my Microsoft contact on what it exactly is that's causing it. It's an LDAP packet that's trying to get to ::1 (Loopback) over the IPv6 interface, and it's being dropped, and one thing that breaks 2025 out of the box, is turning off IPv6, or even setting it to prefer IPv4 using the proper registry keys, not turning it off in the IP stack settings in the NIC configuration. Never turn off IPv6 in the NIC configuration settings.
This condition is leading to a timeout with connection to loopback being dropped, and therefore it is causing this behavior of the domain controller taking an extended time to boot as well as have the improper NLA detection for the NIC and firewall profile.
It was first recognized in Windows Server 2019, but fixed in 2022, and it's surfaced again in 2025. They state pretty much what you line up with in a fix coming very soon, but they have to be certain before it rolls to global distribution channels.
Wes808 I did so as you wished. Temporarily at least. Please clarify your point why you disagree with this as a workaround?
Thanks Karl. It's not applicable to this specific win2025-only-and-domain-controller-only bug - win2025 doesn't use the NLA service at all. The only workaround is to script the nic disabling then re-enabling (we do this using a gpo startup script).
This is a different bug than the years-long-still-not-fixed bug that affects all Windoze OSes (but not just DCs) and is generally fixed by an NLA restart. Some day Microsoft might get arounud to fixing one or both of these bugs, but given the pathetic response thus far, I'm not holding my breath.