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.
Most of my DCs are VMs on Hyper-V, with static IPs, on the same subnet. This didn't happen when the servers were 2022. Only started when they became 2025. Also didn't matter new build or in place upgrade. I wanted to make sure I saw this behavior no matter what. It's even in the non prod forest, with all VM DCs. Also it happens on a NUC, standalone, on its own, as it becomes the first DC in a brand new domain. Resetting the NIC after boot either with GPO startup script or scheduled task is the only way to get the domain profile back on the NIC and make it start working again.
Same for us on all counts