Re: [ActiveDir] KCC Woes

[Tim HInes]

RPC Server Not Available This error can occur either because creation of the replication link failed or because of connectivity issues. Failure to Create a Replication Link In this scenario, repadmin /showreps shows no inbound neighbors, so the repadmin output does not indicate the type of error. To see the cause of the failure, go to the Directory Service event log in Event Viewer. The following event will be logged: Event ID 1265 The attempt to establish a replication link with parameters Partition: DC=branches,DC=corp,DC=hay-buv,DC=com Source DSA DN: CN=NTDS Settings,CN=HubDC1,CN=Servers,CN=DMZ- Administration,CN=Sites,CN=Configuration,DC=corp,DC=hay- buv,DC=com Source DSA Address: 62d85225-76bf-4b46-b929- 25a1bb295f51._msdcs.corp.hay-buv.com Inter-site Transport (if any): CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=corp,DC=hay-buv,DC=com failed with the following status: The RPC server is unavailable. The record data is the status code. This operation will be retried. Replication Link Exists-Connectivity Issues There may be connectivity issues when a replication link exists between the two domain controllers, but replication does not occur (as described in the first section). The output from repadmin /showreps shows inbound neighbors. The status of the last replication for one or more naming contexts returns "Last attempt at <date - time> failed" with the "Target account name is incorrect" error. When the output gives these details, no event is logged in the event log. To test for connectivity problems, ping the GUID-based DNS name displayed in the content of the message. This name is composed of the GUID of the NTDS Settings object of the replication partner, followed by _msdcs.corp.hay-buv.com. It is shown on the DNS server of the forest root as an alias name pointing to the domain controller name. For example, at a command prompt you would type: ping 62d85225-76bf-4b46-b929-25a1bb295f51._msdcs.corp.hay-buv.com Pinging HubDC1.branches.corp.hay-buv.com [10.10.20.99] with 32 bytes of data: Reply from 10.10.20.99: bytes=32 time=94ms TTL=124 ... From the output of the ping command, ensure that the <GUID>_msdcs record can be properly resolved by the DNS server at the root of the forest. This is true provided that the output shows "Pinging " followed by the fully qualified domain name of the domain controller. If a "Request timed out" error is returned, continue to look for connectivity issues. After the ping command works, replication should work properly Tim Hines, MCSA, MCSE (2000 & NT4) ----- Original Message ----- From: Byrne, Steve To: [EMAIL PROTECTED] Sent: Monday, September 30, 2002 7:54 PM Subject: [ActiveDir] KCC Woes Hello everyone, has anyone seen this message? I am getting tons of these in a new DC I have just built. Anyone know what is going on?   There also doesn't appear to be any technet articles about this problem, unless I can't find it..   Thanks       ================================   Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1265 Date:  9/30/2002 Time:  6:01:18 PM User:  N/A Computer: RAG Description: The attempt to establish a replication link with parameters   Partition: CN=Schema,CN=Configuration,DC=domain,DC=com Source DSA DN: CN=NTDS Settings,CN=dc,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configurati on,DC=domain,DC=com Source DSA Address: 68e53ed6-4db9-450c-a602-b0ef7bac7005._msdcs.domain.com Inter-site Transport (if any):   failed with the following status:   The RPC server is unavailable.   The record data is the status code.  This operation will be retried. Data: