AD not replicated

[Guest]

Hi all,

I have one additional domain controller that I put in different site. Right now it doesn't update the content. when I try to replicate it manually, this error message appear: 'the following error occured during the attempt to contact the domain controllers: the RPC server is too busy to complete this operation'
Is there something I can do with this error?

TIA
Echo

 

[Dave Shaw [MVP]]

If this DC is in a different site from other DCs, ensure you have the
following things in place:

In AD Sites and Services -

Ensure servers are in their respective sites
ensure there is a Site Link containing the sites
Ensure there is a distinct subnet or subnets identified and assigned to the
sites
Ensure the Site Link is operational (Interval, Cost, Schedule)
Ensure the DCs can appropriately query DNS servers hosting that domain's SRV
records

etc.

-ds

 

[Herb Martin]

Hi all,

I have one additional domain controller that I put in different site.

Right now it doesn't update the content. when I try to replicate it
manually, this error message appear: 'the following error occured during the
attempt to contact the domain controllers: the RPC server is too busy to
complete this operation'

That sounds like they are in the same site (depending on the
tool you are using) since AD Sites and Services (for one)
gives something like 'intersite replication has been requested
at next optunity...'

Is there something I can do with this error?

Almost all replication and authentication problems are really
DNS problems -- assuming you have basic network functionality
and haven't done a PARTIAL site setup.

Without Sites at all, you DCs will replicate inefficiently but
once you make sites ensure that you have a Site Link between
them [Transports->IP(or RPC-IP)]

DNS:
Dynamic
ALL clients (which includes DNS servers and DCs) NIC settings
must point SOLELY to the internal (dynamic) DNS server (set.)
Restart Netlogon service if you mess with either of these
(avoids the need to reboot.)