You may also need to check the IP configuration itself on the trouble DC to see what it's using for DNS servers. Check the hosts file too, just in case.
Charlie Sullivan Sr. Windows Systems Administrator From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Monday, March 10, 2014 9:08 AM To: [email protected] Subject: RE: [NTSysADM] Active Directory DC replication issue Check your forwarders and any conditional forwarders. Also look for any manually entered domains or static IP's. Based on what you say the child DC is set up wrong somehow. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of CSSU NetAdmin Sent: Monday, March 10, 2014 9:05 AM To: [email protected]<mailto:[email protected]> Subject: Re: [NTSysADM] Active Directory DC replication issue We did flush the DNS with no change. When we do an NSLookup it comes up with an external IP address for anything about the parents but for those servers at the child level, it returns the correct response. The other child DC returns correct IP addresses with NSLookup for anything in the forst. On Mon, Mar 10, 2014 at 8:46 AM, Kennedy, Jim <[email protected]<mailto:[email protected]>> wrote: Ipconfig /flushdns and see what a new ping brings. Then do an NSLookup on it for the domain and see what it returns. It is getting the wrong IP address somewhere. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of CSSU NetAdmin Sent: Monday, March 10, 2014 8:45 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Active Directory DC replication issue We have an Win2008R2 forest. There are two parent DC's and two child DC's. One of the child DC's is not replicating correctly. It seems to be OK with its child partner but it doesn't not sync with either of the parent DC's. The problem seems to be with DNS. When we run - REPADMIN /SHOWREPL * /CSV >showrepl.csv - on the box, it returns an LDAP error 81 (Server Down) Win32 Err 58 error message. Interestingly, when we ping a parent DC from the DC with the issue, it returns an outside IP address not associated with us at all. It pings its sibling fine. DNS looks like it is configured OK. The children point to each other and the parents point to each other and the other three can ping all of the DC's correctly. Any ideas for this issue would be appreciated. Thanks!
