Domain Controller The Target Principal Name Is Incorrect

You can see dc 01 and dc 02 are fine but dc 03 has replication errors and shows the error message the target principal name is incorrect resetting the domain controllers computer account using the following steps resolved the replication issues.

Domain controller the target principal name is incorrect. When we finally got it back i recreated the routing and plugged the server back in so that i could run a dcpromo and take it down gracefully. The domain controller was offline for more than a month. This is why a secure channel between the domain controller between the branch and the headquarters did not exist any longer.

Any help would be greatly appreciated. The target principal name is incorrect. In addition the following event id messages may be logged in the system log.

This system prevents the user from accessing the account. Failed to authenticate with domaindc a windows nt domain controller for domain domain. Upon checking dns as well as the setspn commands to check both dcs seem to have entries on each other so i am not sure what i am doing wrong or what the next steps are.

It was always the same domain controller in use for the replication. Try a manual replication over the ad gui on the affected faulty domain controller in my scenario it only worked sometimes. The target principal name is incorrect.

Fixing the issue step 1. On the domain controller disable the kerberos key distribution center service kdc. Identify the dc which owns the pdc role.

First of all stop the kdc service on the affected domain controller. However the chances are that it is limited to a single account. The reason for the message was that a vpn connection between the headquarters and a branch office was disconnected for several weeks.