Apps and services running on the domain controller could become inaccessible or fail unless admins execute the workaround. Credit: Shutterstock Microsoft is warning IT administrators that their Windows Server 2025 domain controllers (DC) may lose network connectivity after they are restarted. In a Windows release health dashboard update posted Friday, the company said that, after a restart, “Windows Server 2025 domain controllers (such as servers hosting the Active Directory domain controller role) might not manage network traffic correctly,” rendering them inaccessible on the domain network, or possibly allowing “incorrect access” over ports and protocols that should have been blocked. As a result, it said, “applications or services running on the domain controller or on remote devices may fail, or remain unreachable on the domain network.” The post said that the issue is caused because the DCs did not use the domain firewall profile when rebooted, instead reverting to the standard firewall profile. There is as yet no patch. Microsoft says it is working on a fix, which will be provided in “an upcoming release.” There is, however, a workaround that admins must execute each time the server is restarted. It’s a simple one: restart the network adapter. This can be done manually in various ways, including via the PowerShell command Restart-NetAdapter *. However, Microsoft suggests creating a scheduled task to automatically perform the restart each time the server is rebooted. More by Lynn Greiner: Spy vs spy: Security agencies help secure the network edge Linux kernel tweak could cut data center power usage by up to 30% Data centers go nuclear for power-hungry AI workloads Data CenterServers SUBSCRIBE TO OUR NEWSLETTER From our editors straight to your inbox Get started by entering your email address below.