I'm confused by the question. There is a second DC. The entry says that site2 cannot replicate to site1. Is that ok for your environment (I wouldn't think so)?
If they're part of the same forest, they need to share the configuration partition. If they can't, then the KCC is going to complain and other issues may or may not arise in your environment. Better to fix it. Is your VPN always on? Does this answer the question? -----Original Message----- From: Aaron Seet [mailto:[EMAIL PROTECTED] Sent: Friday, January 02, 2004 1:08 AM To: [EMAIL PROTECTED] Subject: [ActiveDir] KCC complain for sites with 2 different domains I have an environment that goes: Site1: home to domain corporate.company1.com; forest root; 1 DC. Site2: home to domain corporate.company2.com; separate tree of same forest; 1 DC. They are connected via router-router VPN of RRAS. I suspect the lack of a second DC for corporate.company1.com in Site2 is causing these errors. ------------------------------------------------------------ Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1566 Date: 1/2/2004 Time: 1:49:49 PM User: N/A Computer: NARU Description: All servers in site CN=Parkway,CN=Sites,CN=Configuration,DC=corporate,DC=company1,DC=com that can replicate partition CN=Configuration,DC=corporate,DC=company1,DC=com over transport CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=corporate,DC=company1,DC=com are currently unavailable. ------------------------------------------------------------ Event Type: Error Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1311 Date: 1/2/2004 Time: 1:49:49 PM User: N/A Computer: NARU Description: The Directory Service consistency checker has determined that either (a) there is not enough physical connectivity published via the Active Directory Sites and Services Manager to create a spanning tree connecting all the sites containing the Partition CN=Configuration,DC=corporate,DC=company1,DC=com, or (b) replication cannot be performed with one or more critical servers in order for changes to propagate across all sites (most often due to the servers being unreachable). For (a), please use the Active Directory Sites and Services Manager to do one of the following: 1. Publish sufficient site connectivity information such that the system can infer a route by which this Partition can reach this site. This option is preferred. 2. Add an ntdsConnection object to a Domain Controller that contains the Partition CN=Configuration,DC=corporate,DC=company1,DC=com in this site from a Domain Controller that contains the same Partition in another site. For (b), please see previous events logged by the NTDS KCC source that identify the servers that could not be contacted. ------------------------------------------------------------ MS KB214745 talks of the SiteLink object which I have right from the start defined and configured. Is there anything I can do to alleviate this, or is this actually a non-issue since there's no second DC anyway? thanks, Aaron List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
