Have you verified that the IP address that the FQDN resolves to is correct? Have you tried pinging DC1 from DC2 by IP and by name, and vice-versa? Run repadmin /showrepl locally on each DC and get the GUID from the top of the output. Are there any errors in repadmin? Try to nslookup the GUID from the other DC. Other people have already recommended running dcdiag, also run netdiag /v /fix. Let us know of any pertinent errors. Good luck.
-Andrew -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Sent: Wednesday, September 28, 2005 12:07 AM To: [email protected] Subject: [ActiveDir] Domain controllers not replicating I have a strange one. I have two sites in different cities, that are in one Domain. Both sites are setup to replicate through a domain controller at each site. Both servers were talking and performing replication a week ago. Now both sites are not replicating. I can ping both Domain controllers from any workstation in both sites. I can also ping from the Domain controller to any workstation at any site. I can also ping the other servers at both sites, except for the Domain controller at the other site that it is setup to replicate with. Both of these Domain controllers cannot ping each other, but they can ping all other computers in both sites. These two servers will talk to everyone else except to each other. When I ping the FQDC of the opposing Domain controller, it does resolve the IP address, but I get a request timed out. __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
smime.p7s
Description: S/MIME cryptographic signature
