|
Question : NTDS Replication error: Missing 'service principle name' - Event ID 1645
|
|
I am having replication issues reported:
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1645
Date: 11/16/2006
Time: 5:43:53 PM
User: Everyone
Computer: SERVER2
Description:
The Directory Service received a failure while trying to perform an authenticated RPC call to another Domain Controller. The failure is that the desired Service Principal Name (SPN) is not registered on the target server. The server being contacted is 094fb434-d91b-4002-acf9-1df06e0eac39._msdcs.domain.lan. The SPN being used is E3514235-4B06-11D1-AB04-00C04FC2DCD2/094fb434-d91b-4002-acf9-1df06e0eac39/domain.lan@domain.lan.
Please verify that the names of the target server and domain are correct. Please also verify that the SPN is registered on the computer account object for the target server on the KDC servicing the request. If the target server has been recently promoted, it will be necessary for knowledge of this computer's identity to replicate to the KDC before this computer can be authenticated.
I found KB 308111 to be accurate: "A missing service principle name may prevent domain controllers from replicating"
http://support.microsoft.com/kb/308111/en-us
But step 2 in the workaround doesn't appear to work for me: the 'setspn' command
"'setspn' is not recognized as an internal or external command,
operable program or batch file."
Any ideas on where to head from here?
|
Answer : NTDS Replication error: Missing 'service principle name' - Event ID 1645
|
|
|
|
|
|
|
