Site Replication taking excessively long

  • Thread starter Thread starter Kevin Anderson
  • Start date Start date
K

Kevin Anderson

I've got an Active Directory structure that includes 6
domain controllers throughout 4 sites.

Our Corporate office has 3 servers (including the
operations masters), as well as our Exchange server.

We have 3 external sites, each of which has 1 domain
controller each.

My problem is when a user is created at a remote site, it
can take up to 6 hours for this user to be replicated over
to the other sites. Internally at the Corporate office,
replication is done via RPC. Our external sites are all
connected via IP set at a 30 minute interval.

In the Event Viewer, there are multiple Events with the ID
of 1311. I've talked with a few other engineers, and
they've suggested converting all replication over to IP,
instead of keeping the corporate office replicating
internally using RPC and all external sites IP. Is there
anything I might be overlooking here?
 
We have 3 external sites, each of which has 1 domain
controller each.

My problem is when a user is created at a remote site, it
can take up to 6 hours for this user to be replicated over
to the other sites. Internally at the Corporate office,
replication is done via RPC. Our external sites are all
connected via IP set at a 30 minute interval.
Click to expand...

You need to provide more Site and Site Link information....

What Schedule? Are you open 24 hours a day (schedule) to replication
on all Site Links?

Also ensure that each DC can reach the other Site DCs (bridgehead
servers) through any firewalls & filters you use -- incomplete or badly
routed replication (due to unreachable DCs) can cause replication delays.

Run DCDiag on every DC and capture the output of each to a file.
Search these files for FAIL, WARN, IGNORE and fix or report any
problems.
In the Event Viewer, there are multiple Events with the ID
of 1311. I've talked with a few other engineers, and
they've suggested converting all replication over to IP,
instead of keeping the corporate office replicating
internally using RPC and all external sites IP. Is there
anything I might be overlooking here?
Click to expand...
Error 1311 - There are currently no logon servers available to service the
logon request
[It would really help if you posted the TEXT version of Event ID
1311 (so everyone doesn't have to go search out the details.)]

Converting local LANS from intrasite RPC to intersite is NOT the solution
to such problems -- you do that only if you need to REDUCE or RESTRICT
the times and frequency of replication (by setting Frequency and Schedule as
well as Cost for multi-hop replication calculation.)

The above implies you have "no logon servers" (and is only peripherally
related
if at all to the replication problems).

Given you have both, the most likely place to look is in your DNS -- do you
have your DNS zone setup correctly:

Dynamic Zone
ALL DCs pointed (in NIC properties) to that Dynamic DC (set)
All Clients pointed there as well
NO DC or Client pointed "outside" the set (don't try to use multiple
settings for both internal and external resolution on the
clients.*)
Make sure you Secondary DNS server are all replicating
If you are using AD Integrated DNS you need to make sure AD is
fully replicating BEFORE you depend on it to replicate DNS **

*Remember: DCs, even DNS servers, are DNS clients too -- use the DNS
forwarder tab if you need to setup EXTERNAL resolution.

** AD replication is dependent on DNS, but if you integrate then DNS
replication is also dependent on AD (and they must BOTH work or will
mutually
fail.)

Have you tried running RepAdmin or ReplMon?
 
Back
Top