So there are two ways I normally tackle these: 1) Enable enhanced KCC logging, see if you can determine it from that. You can enable this by changing the value of "1 Knowledge Consistency Checker" to 4 or 5 (no reboot required) which is located in HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics. From there, you'll find that next time KCC generates these errors many others are also generated in that same log which may give you a clue. 2) People sometimes send me a full ldif dump of their config container and I can pick through it. In this case, that probably would not be fruitful as the 1566 indicates connectivity issues. An 1126 (not enough site connectivity) would be an error where I do this.
Also, starting a network trace, performing ipconfig /flushdns then kicking KCC manually may be fruitful as well. If there is a problem of some other sort (DNS being a likely culprit) that may be viewable there. You would first want to ensure you're pointed to another DC for DNS though, as otherwise you wouldn't see the DNS query that the DC issues for name resolution. It could be any sort of connectivity, DNS is just the most common. ~Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Seet Sent: Tuesday, February 24, 2004 10:24 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] KCC complain for sites with 2 different domains Sure thank you. The errors go -------------------------------------------------- Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1566 Date: 2/24/2004 Time: 5:42:15 PM User: N/A Computer: NARU Description: All servers in site CN=Parkway,CN=Sites,CN=Configuration,DC=corporate,DC=company,DC=com that can replicate partition CN=Configuration,DC=corporate,DC=company,DC=com over transport CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=corporate,DC=company,DC=com are currently unavailable. -------------------------------------------------- Event Type: Error Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1311 Date: 2/24/2004 Time: 5:42:15 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=company,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=company,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. -------------------------------------------------- Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1566 Date: 2/24/2004 Time: 5:42:15 PM User: N/A Computer: NARU Description: All servers in site CN=Parkway,CN=Sites,CN=Configuration,DC=corporate,DC=company,DC=com that can replicate partition DC=corporate,DC=company2,DC=com,DC=sg over transport CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=corporate,DC=company,DC=com are currently unavailable. -------------------------------------------------- Event Type: Error Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1311 Date: 2/24/2004 Time: 5:42:15 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 DC=corporate,DC=company2,DC=com,DC=sg, 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 DC=corporate,DC=company2,DC=com,DC=sg 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. -------------------------------------------------- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman Sent: Tuesday, 24 February 2004 23:11 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] KCC complain for sites with 2 different domains For those of us new to the list (such as myself :-)) can you give us the full problem description with KCC errors you're getting? I do these KCC errors a *lot* which is why I ask. :-) ~Eric 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/
