troubleshooting Question

Active Directory 'KCC' errors related to configuring ip site links on Windows Server 2K3 and 2000

Avatar of atyar
atyar asked on
NetworkingActive DirectoryDHCP
13 Comments1 Solution25127 ViewsLast Modified:
I have a simple active directory domain with 4 sites, and a total of 5 domain controllers.  It works, but my 2003 Servers, of which there are 2 (the other 3 are 2000 Servers), are ridiculously finicky about having the site links setup just so in Active Directory Sites and services.  If anything is out of whack (even having too many site links configured), the knowledge consistency checker gets all out of whack and spams my event viewer with error messages about not being able to form a complete spanning tree topology, and as a result, 1 of the other offices is unavailable, yada yada yada.

My problem is, I create the site links on each of the domain controllers to reflect the wan design as follows:
1)A to B, with cost 100 and freq 60.
2)A to C, with cost 100 and freq 60.
3)A to D, with cost 125 (D has a slower internet connection) and freq 60.
4)B to C, with cost 100 and freq 60.
5)B to D, with cost 125 and freq 60.
6)C to D, with cost 125 and freq 60.
(I tried naming the site links exactly the same on all domain controllers, too.)

At first this is ok.  Within a few minutes, however, the site links get replicated to the other domain controllers, who wind up with a total of like 10 or 12 different site links, the 'extra' ones that were replicated from the other d.c.'s having funky names like A-B(box)CNF:as234kdbf8k234kfb.....

The 2000 servers don't seem to mind this too much, but the 2003 servers get spammed with kcc errors in event viewer and say they can't see the other site with 2003 server, and vice versa.  Does anyone know how you're supposed to setup these site links to they don't replicate all over the domain and cause these kcc errors? I thought if I made them exactly the same on each domain controller, they wouldn't replicate and add to each other.

Come to think of it, the thought occurs to me - are you rather supposed to setup the site links on each domain controller that apply to that d.c. only?  like, on A, I would configure site links for AB, AC, and AD, and then on B, I would configure BA,BC, and BD, and so on?  Still, I'd guess when they replicate that A would wind up with site links AB and BA, and then kcc would get all bent out of shape.....Just a thought...

Any tips would be greatly appreciated.  Just when I get the event viewer clean of active directory errors, I start to feel all warm and fuzzy.....then, the kcc errors come in force and I feel stupid again...*sigh*

incidentally, all 4 sites are connected directly to each other via vpn tunnels.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 13 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 13 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros