I have a small directory where the AD is now failing to replicate. I have checked on KSD1 the dcdiags and things seem fine there. This is the PDC. On the 2 DC KSD2 things aren't repliacating and it's telling me the Target Principal Name is incorrect so I followed the TID http://support.microsoft.com/kb/288167?wa=wsignin1.0 and this didn't work. Here is the dcdiag file from KSD2 and I'm at a loss as to how to get things talking again. Any help would be greatly appreciated. Thank you
Domain Controller DiagnosisPerforming initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site\KSD2
Starting test: Connectivity
......................... KSD2 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site\KSD2
Starting test: Replications
[Replications Check,KSD2] A recent replication attempt failed:
From KSD1 to KSD2
Naming Context: CN=Schema,CN=Configuration,DC=kahlotus,DC=wednet,DC=edu
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2012-12-09 20:48:04.
The last success occurred at 2012-12-08 02:47:59.
42 failures have occurred since the last success.
[KSD1] DsBindWithSpnEx() failed with error -2146893022,
The target principal name is incorrect..
[Replications Check,KSD2] A recent replication attempt failed:
From KSD1 to KSD2
Naming Context: CN=Configuration,DC=kahlotus,DC=wednet,DC=edu
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2012-12-09 21:27:51.
The last success occurred at 2012-12-08 03:38:29.
100 failures have occurred since the last success.
[Replications Check,KSD2] A recent replication attempt failed:
From KSD1 to KSD2
Naming Context: DC=kahlotus,DC=wednet,DC=edu
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2012-12-09 21:35:35.
The last success occurred at 2012-11-19 13:34:04.
29859 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
KSD2: Current time is 2012-12-09 21:37:39.
CN=Schema,CN=Configuration,DC=kahlotus,DC=wednet,DC=edu
Last replication recieved from KSD1 at 2012-12-08 02:47:59.
CN=Configuration,DC=kahlotus,DC=wednet,DC=edu
Last replication recieved from KSD1 at 2012-12-08 03:38:29.
DC=kahlotus,DC=wednet,DC=edu
Last replication recieved from KSD1 at 2000-11-19 13:34:03.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
......................... KSD2 passed test Replications
Starting test: NCSecDesc
......................... KSD2 passed test NCSecDesc
Starting test: NetLogons
......................... KSD2 passed test NetLogons
Starting test: Advertising
......................... KSD2 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: KSD1 is the Schema Owner, but is not responding to DS RPC Bind.
[KSD1] LDAP bind failed with error 8341,
A directory service error has occurred..
Warning: KSD1 is the Schema Owner, but is not responding to LDAP Bind.
Warning: KSD1 is the Domain Owner, but is not responding to DS RPC Bind.
Warning: KSD1 is the Domain Owner, but is not responding to LDAP Bind.
Warning: KSD1 is the PDC Owner, but is not responding to DS RPC Bind.
Warning: KSD1 is the PDC Owner, but is not responding to LDAP Bind.
Warning: KSD1 is the Rid Owner, but is not responding to DS RPC Bind.
Warning: KSD1 is the Rid Owner, but is not responding to LDAP Bind.
Warning: KSD1 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: KSD1 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... KSD2 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... KSD2 failed test RidManager
Starting test: MachineAccount
......................... KSD2 passed test MachineAccount
Starting test: Services
......................... KSD2 passed test Services
Starting test: ObjectsReplicated
......................... KSD2 passed test ObjectsReplicated
Starting test: frssysvol
......................... KSD2 passed test frssysvol
Starting test: frsevent
......................... KSD2 passed test frsevent
Starting test: kccevent
......................... KSD2 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 12/09/2012 20:45:40
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 12/09/2012 20:52:08
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 12/09/2012 20:52:39
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 12/09/2012 21:10:27
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 12/09/2012 21:32:51
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 12/09/2012 21:32:51
Event String: The kerberos client received a
......................... KSD2 failed test systemlog
Starting test: VerifyReferences
......................... KSD2 passed test VerifyReferences
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : kahlotus
Starting test: CrossRefValidation
......................... kahlotus passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... kahlotus passed test CheckSDRefDom
Running enterprise tests on : kahlotus.wednet.edu
Starting test: Intersite
......................... kahlotus.wednet.edu passed test Intersite
Starting test: FsmoCheck
......................... kahlotus.wednet.edu passed test FsmoCheck