Rejecting replication errors

[Englishman]

Hi,
We have a root domain and a child domain. Each domain configured as a
seperate site. NTDS objects were automatically created by the KCC. However we
are experiencing serious replication problems. Errors generated using
repadmin/showreps are:
the destination server is currently rejecting replication requests.
On the other site, the erros are:
the source server is currently rejecting replication requests.

In adsiedit I have confirmed that the enterprise domain controllers have
"replicate directory change all"

Please help

[Paul Williams [MVP]]

Is this all naming contexts or just one or two?

Does replicating manually work? Have you disabled replication using
REPADMIN? Are you able to connect to the DC in question? Has more than 60
days elapsed?

[Englishman]

Hi Paul,
This happens to all servers in the other site. Intra-site replication is
fine but inter-site fails with the errors mentioned.
Manual replication also generates the same error including:
event ID 1925 and 1926 - source NTDS KCC

I have used repadmin /options Server_name -DISABLE_INBOUND_REPL

And yes I can connect to the servers in the othe sites, using AD and remote
desktop etc.

It has not yet been 60 days. In fact one server became a DC just a few days
ago.

Any ideas

Post by Paul Williams [MVP]
Is this all naming contexts or just one or two?
Does replicating manually work? Have you disabled replication using
REPADMIN? Are you able to connect to the DC in question? Has more than 60
days elapsed?
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

[Paul Williams [MVP]]

Those errors (1925 & 1926) usually signify DNS lookup problems.

Point the DC that is currently acting as the bridgehead for that site to a
DC in the central site for DNS (and remove any others from the list) and
restart NETLOGON [1].

This will register SRV records in DNS on the remote side. You can then
again try replicating. Use REPADMIN or REPLMON.


Another thing you could look at, as the error you get isn't quite the same
as the usual "RPC Server Unavailable", is ensure that the bridgehead server
is up and running. Perhaps you have manually configured this?

If both of these fail, you need to manually check the options bit for each
site:
-- http://support.microsoft.com/?id=242780


---
[1] Assuming DHCP Client Service is running and TCP/IP properties set to
dynamically register in DNS (and the zone is able to accept dynamic
updates).

[Englishman]

Hi Paul,
Thanks for your assistance.
I managed to resolve the problem by using the methods you proposed. But the
main problem I discovered was that one server was moved into a different
site. In AD sites and services on all other DC's, the move was updated, but
in AD sites and services on the moved DC, it still remained in the old site.
Because it was a bridgehead server, it couldn't replicate with other servers.

After removing the object from the old site, everything started working.

Kind regards,
Praniel

Post by Paul Williams [MVP]
Those errors (1925 & 1926) usually signify DNS lookup problems.
Point the DC that is currently acting as the bridgehead for that site to a
DC in the central site for DNS (and remove any others from the list) and
restart NETLOGON [1].
This will register SRV records in DNS on the remote side. You can then
again try replicating. Use REPADMIN or REPLMON.
Another thing you could look at, as the error you get isn't quite the same
as the usual "RPC Server Unavailable", is ensure that the bridgehead server
is up and running. Perhaps you have manually configured this?
If both of these fail, you need to manually check the options bit for each
-- http://support.microsoft.com/?id=242780
---
[1] Assuming DHCP Client Service is running and TCP/IP properties set to
dynamically register in DNS (and the zone is able to accept dynamic
updates).
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net