We had to create a new domain. Since the user base was less and had no in-house Exchange at that, we didn't bother to rename the domain or fix it. We created an new domain from scratch.
Regards Liby Philip Mathew From: [email protected] [mailto:[email protected]] On Behalf Of CSSU NetAdmin Sent: Tuesday, March 11, 2014 5:22 PM To: [email protected] Subject: Re: [NTSysADM] Active Directory DC replication issue Sounds like our issue. How did you resolve it? On Tue, Mar 11, 2014 at 4:07 AM, Liby Philip Mathew <[email protected]<mailto:[email protected]>> wrote: Hi, We had a similar situation 5-6 years back. The issue was that we were using an internal domain xxxx.com<http://xxxx.com> that was already registered on the Internet. All the internal DNS, replication were trying to sync / connect with this externally registered domain / IP. Regards Liby Philip Mathew From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Tiago Viana Sent: Monday, March 10, 2014 8:25 PM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Active Directory DC replication issue Oh nooo... Somehow I haven't read the line ", when we ping a parent DC from the DC with the issue, it returns an outside IP address not associated with us at all."... Sorry about that! Well, while it doesn't hurt to check the secure channel... name resolution seems to be the issue (as well pointed by Rami and yourself before) :) Regards, Tiago Ribeiro S. A. Viana From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Tiago Viana Sent: 10 de março de 2014 16:32 To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Active Directory DC replication issue Oftenly it's caused by the Secure Channel being corrupted between the two DC's. If the replication is not only working between those two DC's, I'd check that out, too. Cumprimentos, Tiago Ribeiro S. A. Viana From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rami SIK Sent: 10 de março de 2014 16:23 To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Active Directory DC replication issue Check the followings: Host file DNS forwarders Make sure conditional forwarders are correct if there are any DNS search order in the network configuration properties tab For troubleshooting, use nslookup and its "set debug = 9" feature, I did not remember the exact style now, though In the worst case, compare all these related configurations side by side with the fine-working DC. Good luck, Rami From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of CSSU NetAdmin Sent: Monday, March 10, 2014 5: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! ________________________________ Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] P Protect our planet: Do not print this email unless necessary.
