new 2019 Windows AD server with an error running DCDIAG

JB306yxe 256 Reputation points
2022-01-19T21:24:19.95+00:00

I have to DC's now, one a 2012R2 (SVR1) and 2019 DC (SVR2). I've added a 3rd one called SVR2A. I am removing AD services from SVR1 because we are going to move it to a 2019 server down the road.

DCDIAG fails just on this one. Passes on everything else. So SVR2a also does not have the NetLogon folders because of this.

Testing server: Default-First-Site-Name\SVR2A 

  Starting test: Advertising

     Warning: DsGetDcName returned information for

     \\SVR1.mydomain.ca, when we were trying to reach SVR2A.

     SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.

     ......................... SVR2A failed test Advertising

Any idea on how to fix this?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
8,850 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
3,973 questions

11 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 341.8K Reputation points MVP
    2022-01-19T21:26:02.09+00:00

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\dc3.txt

    then put unzipped text files up on OneDrive and share a link.

  2. JB306yxe 256 Reputation points
    2022-01-19T23:13:44.51+00:00
  3. Dave Patrick 341.8K Reputation points MVP
    2022-01-19T23:14:34.243+00:00

    Still need the other three files. You can work through this one for the missing netlogon, sysvol shares.
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  4. Thameur-BOURBITA 15,816 Reputation points
    2022-01-19T23:40:04.733+00:00

    Hi,

    Check the required ports for sysvol replication is already opened between new domain controller and its replication partner. If it's not the case and you still have the same issue, you should launch non-authoritative restore for sysvol replication:

    force-authoritative-non-authoritative-synchronization

    Please don't forget to mark helpful reply as answer

  5. Limitless Technology 37,526 Reputation points
    2022-01-21T10:12:33.68+00:00

    Hello JohnBowden

    You can follow the troubleshooting approach suggested in the next thread: https://social.technet.microsoft.com/Forums/lync/en-US/6713c55f-0bc5-4d74-a18b-b867ccc9d059/server-is-not-responding-or-is-not-considered-suitable-ad2008r2-failed?forum=winserverDS

    --If the reply is helpful, please Upvote and Accept as answer--