Stuck with AD DS Config Wizard

Marcel Schneider 11 Reputation points
2024-04-18T18:41:59.29+00:00

Hi, There are 2 AD DS in a domain X. One is left over from a previous AD DS FSMO in domain X that is no longer existing. The other is a new AD DS to be built in the same domain X. Since days I'm stuck at the AD DS Config Wizard - "Select the deployment options - Add a DC to an existing domain". Selected is domain X. The error msg is "An AD DC for the domain X could not be contacted".

Both servers can be pinged with name and IP, ping and nslookup works for domain X.

The old server is Windows Server 2019 Standard, V 10.0 (17769) and the new (planned) server is Windows Server 2025 Standard V 10.0 (26085).

According to response from an MS engineer, it should not be a compatibility issue btw the two OS's.

This error msg prevents me from installing the new DC and promote it to an FSMO. Any suggestions how to solve it are very welcome. Can send dcdiag output.

Best regards

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,156 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,881 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Marcel Schneider 11 Reputation points
    2024-04-22T04:50:06.8533333+00:00

    Below more information on the setup:

    There are 2 AD servers in domain X: A and B.

    A is Windows Server 2025 Standard V 10.0 (26085) and should become a new FSMO. It is stuck with AD DS Configuration Wizard which shows "An Active Directory Domain Controller for domain X could not be found". Server Manager (SM) in A displays 2 private addresses (169.xxx and 192.xxx) in addition to the public address. Except for SM, these 2 private addresses cannot be found anywhere else.

    B is a leftover from a previous FSMO-pair in domain X but not working correctly. SM displays another server not server B as addresses found. And command "Resolve-DNSName <server b> -Type A" displays the correct Public IP address plus one private address (169.xxxx).

    DCDIAG /test:DNS displays: "B failed test connectivity. The host 074e89ab .... cbc89beef24a0._msdcs.X could not be resolved to an IP address". This host 074e89ab was found 2 times in DNS Forward Lookup Zones msdcs.X and was both times deleted, the server rebooted, and the entry disappeared. DCDIAG still finds it. In addition, DCDIAG shows "No LDAP connectivity / No host records (A or AAAA) found for this DC". And B "is not responding to directory service requests". DCDIAG /fix is not successful. "B failed test DNS, B passed test LocatorCheck, B passed test FSMOCheck, B passed test Intersite".

    Unknown where the private IP addresses stem from and unclear where host 074e89ab appears from and cannot be deleted. Please help. Best Regards.

    0 comments
  2. Marcel Schneider 11 Reputation points
    2024-04-23T05:32:24.87+00:00

    The command "Get-ADComputer B" outputs "CN=B, OU=Domain Controllers, DC=X" which looks ok.

    The problem is that DCDIAG finds that strange "host" "host 074e89ab .... cbc89beef24a0._msdcs.X [that] could not be resolved to an IP address" and which cannot be found after deletion in DNS Forward Lookup Zones msdcs.X. It is no longer there. But it still shows in DCDIAG.

    Please help in resolving this issue. Any help is highly appreciated. Best regards

    0 comments