|
Question : Replication Issue: The target principal name is incorrect
|
|
Hi experts,
A while back, I set up a 2K3 machine in anticipation of a new branch opening - the opening date got moved a few months back and now when I started it up after a few months being shut down, I am having replication problems. Everything was working before I shut it down. The new office is in a different site. Specifically, when I try a manual replicate in AD sites and services from any server in the first site I get the error message, "The following error occurred during the attempt to contact the domain controller Server01. The target principal name is incorrect". As well, when I enter the UNC path to any other machine, I get this error, " Logon failure: the target account name is incorrect". I thought the problem might have occurred because of the daylight savings change - but even after I installed the patch the same problems occurred. I only have one domain in total - no child domains. The event viewer is filled to the brim with KCC and Kerbios errors - specifically, " 1865", "1311", "1566". I can ping the other machines fine, even put their IP address in place of UNC and I will get a share listing of the remote computer.
I ran a dcdiag on it and got these results:
C:\Program Files\Support Tools>dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Branch2\SERVER04
Starting test: Connectivity
......................... SERVER04 passed test Connectivity
Doing primary tests
Testing server: Branch2\SERVER04
Starting test: Replications
[Replications Check,SERVER04] A recent replication attempt failed:
From SERVER01 to SERVER04
Naming Context: DC=ForestDnsZones,DC=ourdomain,DC=ca
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2007-03-13 19:53:29.
The last success occurred at 2006-10-31 08:45:48.
20 failures have occurred since the last success.
[Replications Check,SERVER04] A recent replication attempt failed:
From SERVER01 to SERVER04
Naming Context: DC=DomainDnsZones,DC=ourdomain,DC=ca
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2007-03-13 19:53:28.
The last success occurred at 2006-10-31 08:45:48.
20 failures have occurred since the last success.
[Replications Check,SERVER04] A recent replication attempt failed:
From SERVER01 to SERVER04
Naming Context: CN=Schema,CN=Configuration,DC=ourdomain,DC=ca
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2007-03-13 19:53:28.
The last success occurred at 2006-10-31 08:45:48.
20 failures have occurred since the last success.
[Replications Check,SERVER04] A recent replication attempt failed:
From SERVER01 to SERVER04
Naming Context: CN=Configuration,DC=ourdomain,DC=ca
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2007-03-13 19:53:27.
The last success occurred at 2006-10-31 08:45:48.
20 failures have occurred since the last success.
[Replications Check,SERVER04] A recent replication attempt failed:
From SERVER01 to SERVER04
Naming Context: DC=ourdomain,DC=ca
The replication generated an error (-2146893022):
The target principal name is incorrect.
The failure occurred at 2007-03-13 19:53:27.
The last success occurred at 2006-10-31 08:45:48.
20 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
SERVER04: Current time is 2007-03-13 20:42:48.
DC=ForestDnsZones,DC=ourdomain,DC=ca
Last replication recieved from SERVER01 at 2006-10-31 08:45:48.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SERVER03 at 2006-10-31 07:50:15.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=DomainDnsZones,DC=ourdomain,DC=ca
Last replication recieved from SERVER01 at 2006-10-31 08:45:48.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SERVER03 at 2006-10-31 07:50:15.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Schema,CN=Configuration,DC=ourdomain,DC=ca
Last replication recieved from SERVER01 at 2006-10-31 08:45:48.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SERVER03 at 2006-10-31 07:50:15.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Configuration,DC=ourdomain,DC=ca
Last replication recieved from SERVER01 at 2006-10-31 08:45:48.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SERVER03 at 2006-10-31 08:05:23.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=ourdomain,DC=ca
Last replication recieved from SERVER01 at 2006-10-31 08:45:48.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SERVER03 at 2006-10-31 08:31:42.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
REPLICATION-RECEIVED LATENCY WARNING
Source site:
CN=NTDS Site Settings,CN=HomeNetwork,CN=Sites,CN=Configuration,DC=brodi
enet,DC=ca
Current time: 2007-03-13 20:42:48
Last update time: 2006-10-31 08:05:08
Check if source site has an elected ISTG running.
Check replication from source site to this server.
......................... SERVER04 passed test Replications
Starting test: NCSecDesc
......................... SERVER04 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER04 passed test NetLogons
Starting test: Advertising
......................... SERVER04 passed test Advertising
Starting test: KnowsOfRoleHolders
[SERVER01] DsBindWithSpnEx() failed with error -2146893022,
The target principal name is incorrect..
Warning: SERVER01 is the Schema Owner, but is not responding to DS RPC
Bind.
[SERVER01] LDAP bind failed with error 8341,
A directory service error has occurred..
Warning: SERVER01 is the Schema Owner, but is not responding to LDAP Bi
nd.
Warning: SERVER01 is the Domain Owner, but is not responding to DS RPC
Bind.
Warning: SERVER01 is the Domain Owner, but is not responding to LDAP Bi
nd.
Warning: SERVER01 is the PDC Owner, but is not responding to DS RPC Bin
d.
Warning: SERVER01 is the PDC Owner, but is not responding to LDAP Bind.
Warning: SERVER01 is the Rid Owner, but is not responding to DS RPC Bin
d.
Warning: SERVER01 is the Rid Owner, but is not responding to LDAP Bind.
Warning: SERVER01 is the Infrastructure Update Owner, but is not respon
ding to DS RPC Bind.
Warning: SERVER01 is the Infrastructure Update Owner, but is not respon
ding to LDAP Bind.
......................... SERVER04 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER04 failed test RidManager
Starting test: MachineAccount
......................... SERVER04 passed test MachineAccount
Starting test: Services
......................... SERVER04 passed test Services
Starting test: ObjectsReplicated
......................... SERVER04 passed test ObjectsReplicated
Starting test: frssysvol
......................... SERVER04 passed test frssysvol
Starting test: frsevent
......................... SERVER04 passed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8000061E
Time Generated: 03/13/2007 20:42:02
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 03/13/2007 20:42:02
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 03/13/2007 20:42:02
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 03/13/2007 20:42:02
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 03/13/2007 20:42:02
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 03/13/2007 20:42:02
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 03/13/2007 20:42:02
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 03/13/2007 20:42:02
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 03/13/2007 20:42:02
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 03/13/2007 20:42:02
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 03/13/2007 20:42:02
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 03/13/2007 20:42:02
Event String: The Knowledge Consistency Checker (KCC) was
......................... SERVER04 failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 19:50:52
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 19:50:52
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 19:59:36
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:00:06
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:15:28
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:23:42
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:24:18
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:25:09
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:25:10
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:25:13
Event String: The kerberos client received a
An Error Event occured. EventID: 0xC0001B6E
Time Generated: 03/13/2007 20:25:35
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/13/2007 20:25:52
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/13/2007 20:25:54
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/13/2007 20:25:56
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:26:00
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:26:00
Event String: The kerberos client received a
An Error Event occured. EventID: 0x00000457
Time Generated: 03/13/2007 20:26:17
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:27:55
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:36:30
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:42:49
Event String: The kerberos client received a
An Error Event occured. EventID: 0x40000004
Time Generated: 03/13/2007 20:42:49
Event String: The kerberos client received a
......................... SERVER04 failed test systemlog
Starting test: VerifyReferences
......................... SERVER04 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
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 : ourdomain
Starting test: CrossRefValidation
......................... ourdomain passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ourdomain passed test CheckSDRefDom
Running enterprise tests on : ourdomain.com
Starting test: Intersite
......................... ourdomain.com passed test Intersite
Starting test: FsmoCheck
......................... ourdomain.com passed test FsmoCheck
C:\Program Files\Support Tools>
A gracious 500 points to anyone who can solve this issue.
Thank you kindly,
Max
|
Answer : Replication Issue: The target principal name is incorrect
|
|
yes we are both on the same page :) format the old server completely and rebuild it from scratch
Then clean AD
|
|
|
|
|
