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.
12,083 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,822 questions
0 comments

11 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. JB306yxe 256 Reputation points
    2022-01-21T16:00:25.677+00:00
    0 comments
  2. Dave Patrick 426K Reputation points MVP
    2022-01-21T16:03:15.657+00:00

    Have you performed the steps here?
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares

    Another method is to move roles off, demote, reboot, promo again the problematic one.

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

  3. JB306yxe 256 Reputation points
    2022-01-26T22:30:59.793+00:00

    Hi all, I had to back bench this issue for a few days because I was running around with my hair on fire. All good now
    I've just demoted SVR2a from the domain, restarted and all looks good. I am going to restart the SVR1 tomorrow morning. SVR2 was just restarted. So far all looks good. I'm going to leave SVR2a as a domain server but have nothing to do with AD. Once I get SVR1 restarted, I will let it settle for the day and then run through all of those diagnostics and create the reports, assuming that there are still issues.
    Thanks for the support so far, much appreciated.

  4. JB306yxe 256 Reputation points
    2022-01-27T20:06:40.063+00:00

    Today, I removed SVR2a, demoted it, removed everything from it, AD and DNS. After that, I went through the DNS and cleared any occurrence of that server.

    The only error now in the dcdiag log file is the following

    ////////////////////////////////////////
    Starting test: DFSREvent 

         The DFS Replication Event Log. 
     There are warning or error events within the last 24 hours after the

     SYSVOL has been shared.  Failing SYSVOL replication problems may cause

     Group Policy problems. 
     A warning event occurred.  EventID: 0x80001396

        Time Generated: 01/26/2022   14:54:35

        Event String:

        The DFS Replication service is stopping communication with partner SVR2A for replication group Domain System Volume due to an error. The service will retry the connection periodically.

    ////////////////////////////////////////

    So, somewhere else, I need to remove SVR2a from a list or config file.

    0 comments
  5. Dave Patrick 426K Reputation points MVP
    2022-01-27T20:19:06.453+00:00

    You can remove the remnants from active directory by following along here.
    https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
    https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

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