How to force active directory replication from one DC to another

active-directorydomain-controllerreplicationwindows-server-2008-r2

I am having issues replicating AD from one DC to another. Both servers are Windows Server 2008 R2 SP1. I have used the GUI option in sites and service to force replication. I have also tried repadmin, and ntsdutil.

The command for repadmin that I tried:

repadmin /replicate mars zeus dc=CS,dc=local

I get the error when I try repadmin:

Repadmin can't connect to a "home server", because of the following error. Try specifying a different home server with /homeserver:[dns name]

I have downloaded the Active Directory Replication Status Tool from [here]: I have recived the following error after I ran the replication status.1

AD Tool Error
AD Tool Error 2

I have created a youtube video, better explaining my issues: The video here

I was hoping someone could help me replicate my two DC with AD. I am really not sure what to do next, or what else to try.

Best Answer

It probably is a recent addition of LiveQoS NDIS Filter Driver.

Uncheck the filter on your IPv4 NIC and reboot your servers to be sure. I bet that fixes your problem.

Related Solutions

Domain – Active Directory/DNS problem

To see if this is host based firewall related, turn off the domain, public and private profiles temporarily. Do you have multiple interfaces as in Windows Server 2008 the most restrictive profile is in effect. Run this from elevated command prompt

netsh advfirewall set publicprofile state off
netsh advfirewall set privateprofile state off
netsh advfirewall set domainprofile state off

The memory usage can be misleading. Often its used but freed when necessary. Look at the resource exhaustion detector operational event log (open eventvwr and go to applications and services/microsoft/windows/resource exhaustion detector/operational) to determine if running out of memory.

Use Process Explorer to see the memory usage and see whats available. If available looks low, check with RAMMap from Syinternals to get an idea of usage. See RAMmap explained at http://blogs.technet.com/b/askperf/archive/2010/08/13/introduction-to-the-new-sysinternals-tool-rammap.aspx because I have had instances where metafile was "consuming" it. But it was expected behaviour.

Error 81 in DCDiag implies LDAP server was inaccessible. Do you have any 3rd party product on the DC itself providing bundled Antivirus + Firewall behaviour? If you can access LDAP while locally on the DC but not remote and if you are sure no host based firewall is in use, I'd check if any intermediate network devices are filtering/dropping packets.

Powershell – Force active directory replication after joining a server to a domain

Assuming that you're not having problems with DNS replication to begin with (have you confirmed this ...? ) :

You will also need to know the source DC (where the DNS record first exists) and target DC (the one being used by the developers) to make sure you're actually replicating the record that you care about.

How to speed up AD integrated DNS zone replication? Server 2008 r2

Per Simon Catlin:

I've used this to do pretty much the same thing. Don't replicate everything, you only need to replicate the dnsDomain partition (i think the DN is dc=domaindnszones,dc=yourdomain,dc=co,dc=uk).

Example of repadmin:

%SystemRoot%\System32\repadmin.exe /replicate <target_dc> <source_dc> DC=DomainDnsZones,DC=domain,DC=co,DC=uk

Repadmin doesn't require a server reboot, I have no idea what would lead you to think that it does.

Best Answer

Related Solutions

Domain – Active Directory/DNS problem

Powershell – Force active directory replication after joining a server to a domain

Related Topic