Discussion Locked

Windows 2000 AD Replication Problems

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Windows 2000 AD network running in mixed mode. We have 1 home office and 5 regional offices connected to the home office via a T1 line. The home office and two regional offices have WIN 2000 DCs and 3 other regional offices have NT 4. We are in the process of moving all to servers WIN 2000. The last regional office that I upgraded (last week) to WIN 2000 has no outbound replication partners. The inbound replication partners seem fine because it is replicating with the two servers for inbound traffic. I tried using repadmin as follows: (repadmin /syncall /force). I get the following error ?the naming context is in the process of being removed or is not replicated from the specified server?. I get the same error when I try to replicate via Active Directory Sites and Services. I found MS article 281485 and it says to obtain the latest service pack, I already have all patches in place and I am at SP4 on all WIN 2000 DCs. The article says the problem was first fixed with SP3 and to contact Microsoft for the patch. I have spent the last three days on this scouring the web and none of the articles that I have found are any help. The event log IDs are pointing me in the wrong directions. IN DNS ?allow dynamic updates? is set to yes. Has anyone else had this problem? Do you know where I can get the patch without contacting Microsoft? Any other way around this?

2 replies

by joseph moore

In the Technet article you listed, it mentions running NTDSUTIL from Directory Services Restore Mode. Did you do that? Did you run it to try and repair the AD database?
I have not seen this error before personally, but I have run NTDSUTIL to fix things, and it does work.

by joseph moore

And if you did try NTDSUTIL, did you see this article, right here at TR:
http://tinyurl.com/2ptp2
It talks about how a Domain Controller has 2 NICs, and that mangled the AD database, causing your exact problem.
Check it out!

This discussion is closed to new replies.