Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 25506
  • Last Modified:

How to Force Replication in AD with incomplete DC replicating Partners

AD problem in Windows 2003.
Q. How do you force replication between DCs that are all listed in Sites and Services, but only partial lists in each DC's NTDS i.e. no one DC's NTDS listing has all of the DCs listed, but there are at least 2 DCs listed in each NTDS as replication partners.
I have 4 DCs (DC1 and DC2) and 2 of them resolve DNS (NS1 and NS2)
i.e. in Sites and Services, under each DC's NTDS are listed the following:
DC1 <>NS2
            DC2
DC2 <> DC1
            NS1
NS1 <>DC2
            NS2
NS2 <>DC1
            NS1  
           
Running replmon shows NS1 and DC1 are not replicating properly and NS2 and DC2 not replicating properly. Toplogy confirms this.

Trying command line: repadmin /syncall /force etc. gives the following error:
DsReplicaSync() failed with status 8452 (0x2104):
    The naming context is in the process of being removed or is not replicated from the specified server.

Tried ntdsutil metadata cleanup but there was nothing to do

How does one fix this?
Thanks
0
PWyatt1
Asked:
PWyatt1
  • 4
  • 3
  • 2
  • +1
2 Solutions
 
ChiefITCommented:
You might be missing the host A records of the new or rebuilt server.

A quick way to tell is DCdiag.

A quick way to fix is

Run DCdiag /fix.DNS
Go to the command prompt, and run ipconfig /registerDNS
Stop netlogon service
Start netlon service.

Then try to force replicate.
0
 
ChiefITCommented:
Forgot to tell you DCdiag reports will have errors that say ""DcGetname"" for missing Host A records.

0
 
PWyatt1Author Commented:
Checked my DNS records and everything is OK w/ A records.
I forgot to tell you I had run a dcdiag /fix with no errors and the report shows conectivity between all partners is OK.
Your dcdiag /fix.dns is an invalid syntax :)
Anyway, DCDIAG is clean.
I went ahead and did the net stop netlogon and start again and force replicate and it came up with the same error:
DsReplicaSync() failed with status 8452 (0x2104):
    The naming context is in the process of being removed or is not replicated from the specified server.
Any other suggestions?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
thenoneCommented:
Yes go to sites and services and for each site right click on each ntds and click check topology. This should correct itself. I have deleted the ntds before and check topology has brought it back.
0
 
PWyatt1Author Commented:
G-r-r-r. Didn't work. I am going to go to each DC and do a "push" replication /force then go back to S&S and check topology. But first I'm going out for a bite to eat. I'm starving! AD problems can wait 1 hour :)
0
 
Zenith63Commented:
You can easily add and remove those NTDS connections if you want, this allows you control the replication topology.  Those two on each DC are created by default but you can add them the other DCs to each one if you want, creating a full mesh relay topology, or you could create a ring, whatever suits.

The first thing I'd do though is delete ALL the connections from each DC and add them back in again.  This often solves replication problems assuming your DNS is OK.  So literally select each one, delete it, then create a new connection to the other DC.

Now in replmon force replication and see what happens.  Also replmon should give a reason for the replication failure?
0
 
thenoneCommented:
Zenith that is pretty much what I had said.
0
 
PWyatt1Author Commented:
Finally! Deleted all of them.
Added them back in.
Went to replmon and "synchorized each directory partition..." for each DC.
Went to topology and saw all servers were lnked, although two of them have only one link implying either a missing inbound or outbound link. (I'll check this later).
I went back to S&S and was able to replicate all servers to each other.
Thanks for the help. You get the points.
0
 
thenoneCommented:
Thanks for the points
0
 
PWyatt1Author Commented:
Sorry, thenone:
You were not supposed to get the points. I tried to split between CiefT and Zenith63, but something screwed up. I will request the admin to award the points accordingly.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now