Active Directory Replication problem on W2K Server
Posted on 2002-04-23
I have 2 window 2000 servers hosting 2 separate domains for our local network. The basic configuration is ServerA.domainA.<registered domain name>
ServerB.domainB.<registered domain name>
I cannot add users from domainB to groups in domainA, although I can do vice versa. When I try, I get the error "The specified user was not found. If the user exists on another domain controler in the enterprise, it may take 15 minutes or more for the user to be replicated to the global catalog."
I have been looking at my Active Directory Replication. When I try to manually replicate from Active Directory Sites and Services this is what I get:
On ServerB attempting to replicate ServerB to ServerA, I get "RPC Server is unavailable" (The service is running)
On ServerB attempting to replicate ServerA to ServerB, I get "DSA operation unable to proceed because of DNS lookup failure" (DNS seems to be working OK - Both servers are DNS servers)
On ServerA attempting to replicate ServerA to ServerB, I also get "DSA operation unable to proceed because of DNS lookup failure"
On ServerA attempting to replicate ServerB to ServerA, it works.
Perhaps there is a DNS problem on ServerA? I do get an error in DNS event log on ServerA when DNS tries to do a Dynamic Update. The error is shown below, and I have tried to fix it, but unsuccessfully.
"DNS Server has updated its own host (A) records. In order to insure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.
If this DNS server does not have any DS-integrated peers, then this error should be ignored.
If this DNS server's ActiveDirectory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.
To insure proper replication:
1) Find this server's ActiveDirectory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the ActiveDirectory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data."