Article ID: 816577 - View products that this article applies to.
For a Microsoft Windows 2000 version of this article, see 328701
A Windows Server 2003 domain controller cannot replicate the configuration or the schema partitions with replication partners that belong to another domain of the forest. If the domain controller is a global catalog server, it also cannot replicate the other domain partitions with these replication partners.
Additionally, an event similar to the following is logged every 15 minutes in the Directory Services event log:
Event ID: 1265
Event ID: 63
If you run the dcdiag command on MYDC1, you may receive output similar to the following:
CN=Configuration,DC=mydomain,DC=com MySite\MYDC2 via RPC objectGuid: a6999e16-99b5-432f-9bc5-3eecf5dc192f Last attempt @ 2003-03-28 00:05.30 failed, result 1326: Logon failure: unknown user name or bad password. Last success @ 2003-03-27 23:15.14. 3 consecutive failure(s).
DC Diagnosis [Replications Check,DC-LV1] A recent replication attempt failed: From MYDC2 to MYDC1 Naming Context: CN=Configuration,DC=mydomain,DC=com The replication generated an error (1326): Logon failure: unknown user name or bad password. The failure occurred at 2003-03-28 00:09.09. The last success occurred at 2003-03-27 23:15.14. 3 failures have occurred since the last success. Kerberos Error. The machine account is not present, or does not match on the destination, source or KDC servers. Verify domain partition of KDC is in sync with rest of enterprise. The tool repadmin/syncall can be used for this purpose. ...
This problem can occur when the password of the inter-domain trust account is not synchronized on both sides of the trust relationship.
To resolve this problem, reset the trust relationship.
Note In the sample messages and the examples presented in this article, MYDC1 is a domain controller that belongs to the mydomain.com domain. MYDC2 is a replication partner of MYDC1 that belongs to the subdom.mydomain.com domain.
Step 1: Install Windows Support ToolsTo install Windows Support Tools, follow these steps:
Step 2: Reset the Trust RelationshipTo reset the trust relationship, follow these steps:
Step 3: Verify That Replication Occurs CorrectlyYou can use the Repadmin or Replmon replication tools to verify that replication occurs correctly. For detailed information about the syntax of the repadmin command, type repadmin /? at the command line, and then press ENTER. To verify that replication occurs correctly if you are using the Repadmin tool, do the following:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
You can use either of the following two methods to view the trust relationship between the two domains:
DC1 must authenticate against DC2 before DC1 can replicate from DC2. To authenticate, DC1 sends a Kerberos KRB_TGS_REQ request to the key distribution center of the subdom domain. The service principal name that DC1 uses for this authentication is the service principal name that DC1 uses for replication.
The key distribution center of the child domain returns the following KRB_ERROR error message to this request:
This error message means that the key distribution center cannot decrypt the data included in the request. Most of the time, this data is the ticket-granting ticket (TGT). Because the key that is used to decrypt this data is derived from the password of the inter-domain trust account, when you reset the key, the passwords are resynchronized on both sides.
Message stream modified.
Article ID: 816577 - Last Review: February 28, 2007 - Revision: 3.3