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.
Untill they fix it, I'm simpy bouncing the cards at bootup.....
Server 2025 Network Profile Wrong After Reboot
It's a bit primitive, but it works
</P>
No need for caveman theatrics. 😉The simple fix is to enter a static local IPV6 address on the adapter.
Read the link and the article - then read the comments, that approach was also unsuccessful
I have it working in a lab. The moment I added the static IPV6 and DNS entries, the NIC status switched to the test.local domain and persisted multiple reboots.
I have identical setup (only difference is my domain name) - I am not seeting the same, setting a local IPv6 address makes no difference. Only bouncing the card at starup works for me.
Version 24H2 (OS Build 26404.5000) Fully updated
VMware Virtual Maching vmxnet3 NIC
