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.
Could you share get-netadapter, and get-netipconfiguration, please?
Wes808 my case with MS is still being reviewed. I have good news. The Microsoft engineering team was able reproduce it! That's a good sign. I figured people would start upgrading their DCs and take down their network essentially.... There's a workaround. Do a restart-netadapter * to bring the proper profile back. Set that up as a scheduled task to run at startup for now. More to come.
JamfSlayer what was the outcome of your SR?
- Thanks Jamf. Yeah I already set up a startup script gpo for those boxes so they can function in the meantime. Good to hear MS has a repro. Look forward to hearing more!