Windows Server 2019 DC network keeps on private

Today I noticed a problem with a single domain controller. Whereas the domain controller kept on connecting to the private network instead of a domain network. I tried to figure out what caused this problem.

Firstly I thought it was related to the boot sequence of the hyper-v server. Unfortunately, this wasn’t the problem, with rebooting the domain controller it-self didn’t solve the issue either. I tried to look up and found a solution in the end. It’s a simple solution, however, it has to be done with caution. It’s possible you screw up a lot of things on the domain controller which you don’t want.

There is a workaround to restart the NLA services every time after a reboot. This is not the best solution to use. Unless you want to keep yourself busy.

To solve the problem you have to login to the server.

  1. Go to the registery (start > type regedit )
  2. Go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc
  3. Find the REG_MULTI_SZ key DependOnService
  4. Edit this registry string.
  5. Add Netlogon to the list which is already there.

The default list is:

In the end the line should look like:

When you changed this setting, click ok. You get probably a warning message to see. Click ok. and close the regerstry window.

Reboot the server to see if the change worked. You will notice that the network link shows the domain name which is configured in the DNS.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.