Troubleshooting AD Replication error 1908: Could not find the domain controller for this domain.

Applies to: Windows Server 2019, all versionsWindows Server version 1803Windows Server Datacenter Core More

Symptoms


1.REPADMIN.exe reports that replication attempt has failed with status 1908.

REPADMIN commands that commonly cite the 1908 status include but are not limited to:
·      REPADMIN /ADD
·      REPADMIN /REPLSUM *
·      REPADMIN /REHOST
·      REPADMIN /SHOWVECTOR /LATENCY
·      REPADMIN /SHOWREPS
·      REPADMIN /SHOWREPL

Sample output from "repadmin /syncall" command:

Syncing all NC's held on CONTOSO-DC02.
Syncing partition: DC=ForestDnsZones,DC=Contoso,DC=com
CALLBACK MESSAGE: Error contacting server 1b136427-14f0-448a-965c-
9cbb61400fcd._msdcs.Contoso.com (network error): 1908 (0x774):
    Could not find the domain controller for this domain.

Sample output from "repadmin /showreps" command:

DC=ForestDnsZones,DC=Contoso,DC=com
HQ\Contoso-DC02 via RPC
DC object GUID:1b136427-14f0-448a-965c-9cbb61400fcd._msdcs.Contoso.com/
Last attempt @ <DATE> <TIME> failed, result 1908 (0x774):
Could not find the domain controller for this domain.
<# consecutive failure>
<Last Success>

2. NTDS KCC, NTDS Replication events with the 1908 status are logged in the directory service event log.

Active Directory events that commonly cite the 1908 status include but are not limited to:


Event SourceEvent CategoryEvent IDEvent TypeEvent String
NTDS KCCKnowledge Consistency Checker1926WarningThe attempt to establish a replication link to a read-only directory partition with the following parameters failed.
NTDS KCCKnowledge Consistency Checker1925WarningThe attempt to establish a replication link for the following writable directory partition failed.
NTDS ReplicationReplication1943ErrorActive Directory was unable to remove all of the lingering objects on the local domain controller. However, some lingering objects might have been deleted on this domain controller before this operation stopped. All objects had their existence verified on the following source domain controller.
NTDS ReplicationSetup1125ErrorThe Active Directory Domain Services Installation Wizard (Dcpromo) was unable to establish connection with the following domain controller.
These events will contain the following sub Error Value:
Additional Data
Error Value:
Could not find the domain controller for this domain. 1908

3. When trying to force replication in Active Directory Sites and Services console (dssite.msc) via the "Replicate now" option, we may receive the error below:

Dialog title text: Replicate Now

Dialog message text: The following error occurred during the attempt to synchronize naming context <Naming Context> from Domain Controller <Source-DC-Name> to Domain Controller <Destination-DC-Name>:  Could not find the domain controller for this domain.

Failure Message: Could not find the domain controller for this domain.

Buttons in Dialog: OK

4. Domain Controller Promotion/Demotion

Dialog Box on Dcpromo.exe Failure:

Dialog title text: Active Directory Installation Wizard

Dialog message text: Active Directory could not create the NTDS Settings object for this Domain Controller CN=NTDS Settings,CN=<DC_Name>,CN=Servers,CN=<SiteName>,CN=Sites,CN=Configuration,<DomainDN> on the remove domain controller <Remote_DC_FQDN>.  Ensure the provided network credentials have sufficient permissions.

Failure Message: Could not find the Domain Controller for this domain.

Buttons in Dialog: OK

DCPromo.log file reports(%windir%\debug\DCPromo.log):

[INFO] Error - Active Directory Domain Services could not create the NTDS Settings object for this Active Directory Domain Controller CN=NTDS Settings,CN=CONTOSO-DC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Contoso,DC=com on the remote AD DC contoso-dc01.Contoso.com. Ensure the provided network credentials have sufficient permissions. (1908)
[INFO] NtdsInstall for Contoso.com returned 1908
[INFO] DsRolepInstallDs returned 1908
[ERROR] Failed to install to Directory Service (1908)

Cause


Error Code 1908 represents the error ERROR_DOMAIN_CONTROLLER_NOT_FOUND which displays as "Could not find the domain controller for this domain."  This error has two primary causes:

1.       The destination DC is unable to contact a Key Distribution Center(KDC)

2.       The computer is experiencing Kerberos related errors


An important concept to understand for this scenario is that the KDC used for replication operations may be:

a. The destination DC
b. The source DC
c. An entirely different DC (not the source or destination DC).

Resolution


1. Verify the Key Distribution Service is running on the Target Domain Controller

Discover the Kerberos Key Distribution Center you are contacting. This can be discovered by using a packet capture program like Network Monitor 3.4 (Available here.)

1. Use Network Monitor to capture the reproduced error message. (You may need to stop the DNS client service first so that you see the DNS query traffic)

 2. Review the packet capture for the DNS query for a KDC:
Sample Address Queries:

_kerberos._tcp._<SiteName>._sites.dc._msdcs.<Domain>.com
_kerberos._tcp.dc._msdcs.<Domain>.com

3. Review for any DCLocator Traffic:
Sample Network Monitor 3.4 capture of DcLocator Traffic. In this example 10.0.1.11 is the KDC we discovered and 10.0.1.10 is the client requesting a ticket. This uses the default Network Monitor Column layout.

Frame #Time and DateTime OffsetSource IPDestination IPDetails
423/7/20123.6455760 10.0.1.10   10.0.1.11LDAPMessage LDAPMessage:Search Request, MessageID: 371 *** This packet is a UDP LDAP call for DC Locator looking for Netlogon***
433/7/20123.6455760 10.0.1.1110.0.1.10   NetLogon NetLogon:LogonSAMPauseResponseEX (SAM Response when Netlogon is paused): 24 (0x18)
4. Verify that 10.10.1.11's KDC and Netlogon services are running.
On discovered Domain Controller(10.0.1.11) verify the KDC and Netlogon service status with SC Query

Example - Query the KDC service with: "SC Query KDC" and the Netlogon Service with: "SC Query Netlogon"
These commands should return "State: Running"


2. Verify that the destination Domain Controller is Advertising as a Key Distribution Center
Use DCDIAG.exe to verify that the destination Domain Controller is advertising.  From a CMD.exe prompt run the following:

C:\DCDiag.exe /v /test:Advertising /test:SysVolCheck

Verify that the Domain Controller passes the Advertising and SYSVOLCHeck tests and is advertising as a Key Distribution Center and SysVol is ready.  If SysVol is not ready, the server will not be able to advertise as a Domain Controller. 


Testing server:<SiteName>\<DC Name>
Starting test: Advertising
The DC <DC Name> is advertising itself as a DC and having a DS
The DC <DC Name> is advertising as an LDAP server
The DC <DC Name> is advertising as having a writeable directory
The DC <DC Name> is advertising as a Key Distribution Center
The DC <DC Name> is advertising as a time server
The DS <DC Name> is advertising as a GC.

Starting Test: SysVolCheck
       * The File Replication Service SYSVOL ready test
       File Replication Service's SYSVOL is ready
       ..<DC Name> passed test SysVolCheck 

3. Verify that source computer and target computer are within 5 minutes of each other.

4. Check for any Kerberos failures 
a. Enable Kerberos Event Logging on Client Machine and Domain Controllers in site.
b. KB: 262177 How to enable Kerberos event logging
c. Troubleshooting Kerberos

More Information



This error is one of the featured exercises in the following TechNet hands-on lab:
TechNet hands-on lab: Troubleshooting Active Directory replication errors
In this lab, you will walk through the troubleshooting, analysis and implementation phases of commonly encountered Active Directory replication errors. You will use a combination of ADREPLSTATUS, repadmin.exe and other tools to troubleshoot a five DC, three-domain environment.  AD replication errors encountered in the lab include -2146893022, 1256, 1908, 8453 and 8606.
http://go.microsoft.com/?linkid=9844718