I currently have 2 sites in my 2003 AD with 3 DCs. Two at one plant and one at another. I am having issues replicating between the sites, it seems like it may be a dns issue, but I cant put my finger on it. I receive the following error messages...
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042
Date: 8/8/2005
Time: 10:32:46 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SC
Description:
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine's views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2005-04-02 14:31:54
Invocation ID of source:
00e3f844-f834-00e3-c80a-e40494e09304
Name of source:
bb38d329-9c55-4452-aba9-017380596ffc._msdcs.Davis.loc
Tombstone lifetime (days):
60
The replication operation has failed.
User Action:
Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:
1. Demote or reinstall the machine(s) that were disconnected.
2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner
and...
Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 4
Date: 8/8/2005
Time: 11:03:08 AM
User: N/A
Computer: SC
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/eng.davis.loc. The target name used was LDAP/21ff7ace-8147-47dc-8e2d-9ebfc1d924fc._msdcs.Davis.loc. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (DAVIS.LOC), and the client realm. Please contact your system administrator.
Any help would be greatly appreciated.
Thanks.
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042
Date: 8/8/2005
Time: 10:32:46 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SC
Description:
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine's views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2005-04-02 14:31:54
Invocation ID of source:
00e3f844-f834-00e3-c80a-e40494e09304
Name of source:
bb38d329-9c55-4452-aba9-017380596ffc._msdcs.Davis.loc
Tombstone lifetime (days):
60
The replication operation has failed.
User Action:
Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:
1. Demote or reinstall the machine(s) that were disconnected.
2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner
and...
Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 4
Date: 8/8/2005
Time: 11:03:08 AM
User: N/A
Computer: SC
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/eng.davis.loc. The target name used was LDAP/21ff7ace-8147-47dc-8e2d-9ebfc1d924fc._msdcs.Davis.loc. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (DAVIS.LOC), and the client realm. Please contact your system administrator.
Any help would be greatly appreciated.
Thanks.