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.
have you disabled IPv6 or all "stock config"?
What is your external DNS in DNS forwarder on each of the DCs?
Without it the machines cannot see the internet. Test-Connection www.google.de should fail.
Agreed this should not affect the network profile (NLA). but worth looking into.
I can confirm the easy fix for the issue related in your article is to simply define a local IPV6 address for the NIC. It appears windows attempts to ping the IPV6 adapter as part of it’s integrated NLA process for a Domain Controller, regardless that NLA service is purposefully shut down.
For example, set the IPV6 to this for both the IP and DNS: fd12:3456:789a:0001:0000:0000:0000:0063 /64
My adapter on the test Windows 2025 Domain Controller immediately switched from a ‘Network 2’ profile to the 'test.local' domain and persisted after reboot!
Yes, set a local IPv6 solve the problem.👍
