Resetting Domain Controller Secure Channel

15 בOctober 2017

תגיות:
אין תגובות

Over last weeks I got annoying error event on my customer’s domain controller, for some reason, the replication stopped, some clients who were connected to DC01 got errors like incorrect password while interesting their password or while trying to access the network resources and even I wasn’t able to log in the DC01 server, no matter what I tried, however, If I would try to login with the same password to DC02 it is worked, most likely restarting the server does solve this issue, but this issue repeats and appear within couple of hours again.

  • This issue could happen when one of your DC’s was power off for a while and hasn’t synced with others.
  • Could happen to a client which was down for a while as well.
  • Could happen due to incorrect DNS settings on clients.

and this message showed up several times:

Log Name: System
Source: NETLOGON
Event ID: 5722
Level: Error
Computer: DC02.XXX.CO.IL

Description

The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server Dcxx$. The target name used was xxxxxxxxx._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.

Phare number 1:

The first step was to force replication using the following command:

repadmin /syncall /AePdq.

Phare number 2:

Try to purge kerberos tickets:

klist purge

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

Phare number 3:

Resetting secure channel  using the following command

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

Completed restart should be better.

הוסף תגובה
facebook linkedin twitter email

Leave a Reply

Your email address will not be published. Required fields are marked *