Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Added first 2008R2 DC to 2003 domain - replication issues

Status
Not open for further replies.

acl03

MIS
Jun 13, 2005
1,077
US
I have a 2003 forest with a single domain. Functional level is Windows Server 2003.

I just did the schema update (forestprep followed by domain prep).

One of our remote site's 2003 DC failed. I did the metadata cleanup and I am attempting to add a replacement DC with the same name, but 2008 r2.


After letting the schema updates replicate, I ran dcpromo on my new windows 2008 r2 (SP1) server in a remote office. The new server is also a DNS server. The connection objects are not being created in "sites and services" in my main office, so replication is not working. I also see errors in the DNS log in my main office:

The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.

Directory partition:
CN=Configuration,DC=newdc,DC=company,DC=com

There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.

Code:
User Action 
Use Active Directory Sites and Services to perform one of the following actions: 
- Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option. 
- Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site. 
 
If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

There are other various errors in different places as well. Any ideas how to get DNS & replication working?

Thanks,
Andrew

[smarty] Hard work often pays off over time, but procrastination pays off right now!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top