Friday , October 20 2017

Resetting Domain Controller Secure Channel – The target principal name is incorrect

Two Domain Controllers lost sync as secondary domain controller was turned off for a period of time due to power failure.

Once the Secondary Domain Controller is back online, PDC doesn’t want to sync (Primary Domain Controller) as the Kerberos ticket would have expired. From the Secondary Domain Controller I am not able to access the sysvol,Netlogon shares between machines – It failed with Access Denied errors

Step 1 –

Tried Forcing Replication (No luck)  – Error : The target principal name is incorrect.

PS C:\> repadmin /syncall /AePdq

Syncing all NC’s held on TOB10-POS-DS001.

Syncing partition: DC=ForestDnsZones,DC=careexchange,DC=IN

SyncAll reported the following errors:

Error contacting server CN=NTDS Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=careexchange,DC=IN

(network error): -2146893022 (0x80090322):

The target principal name is incorrect.

Step 2 –

Tried purging the kerberos tickets – (No luck)

C:\>klist purge

Current LogonId is 0:0x75fb1
Deleting all tickets:
Ticket(s) purged!

Step 3  –  (SOLUTION)

Resetting secure channel  –

netdom resetpwd /server:secondarydomaincontroller /ud:domainname\administrator /pd:password

Restarted Below Services after resetting the secure channel in my Secondary Domain Controller

Kerberos Key Distribution Center

Active Directory Domain Services.

Active Directory Replication started working .

 

Reference Events –

Log Name: System
Source: NETLOGON
Event ID: 5722
Level: Error
Computer: SecondaryDC.careexchange.in

Description:

The session setup from the computer PDC(Primary Domain Controller) failed to authenticate. The name(s) of the account(s) referenced in the security database is PDC$. The following error occurred:

Access is denied.

Source: Microsoft-Windows-Security-Kerberos
Event ID: 4
Level: Error
Computer: SecondaryDC.careexchange.in

Description:

The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server DS$. The target name used was LDAP/0F4C2201-12F8-4499-BCCB-193517A42293._msdcs.careexchange.in. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (careexchange.in) is different from the client domain (careexchange.in), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Exchange Server MVP , Publisher of CareExchange.in Supporting/Deploying/Designing Microsoft Exchange for some years. Extensive experience on Microsoft Technologies.

Check Also

Automate Run Summarization via PowerShell in SCCM

Without Delegating System Center Configuration Manager Deployment Rights. We can Update the Summarization Automatically via ...

5 comments

  1. Hi Satheshwaran,

    I have domain and additional domain controller everything working fine , except i cannot see the computer accounts in computer container in domain , but it is available in additional domain.

    Thanks in advance

  2. It’s truly very difficult within this busy life to listen news on TV, so I simply
    use the world wide web for that reason, and obtain the hottest information.

  3. o man thank you so much I really appreciate your help you are genious

  4. I also facing same isse:
    Two Domain Controllers lost sync as secondary domain controller was turned off for a period of time due to power failure.

    Once the Secondary Domain Controller is back online, PDC doesn’t want to sync (Primary Domain Controller) as the Kerberos ticket would have expired. From the Secondary Domain Controller I am not able to access the sysvol,Netlogon shares between machines – It failed with Access Denied errors

Leave a Reply

Your email address will not be published.