Set all DNS servers to point to HQ. And yes, you may still have some remnants in DNS of the old server.
From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Thursday, July 24, 2014 12:34 PM To: NT Subject: RE: [NTSysADM] Polling wrong DC That was the DC- we had an issue with the router so there was no VPN tunnel for a few months. Jean-Paul Natola ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Polling wrong DC Date: Thu, 24 Jul 2014 16:25:37 +0000 Are there a DC in the remote sites? Is AD sites and services configured correctly? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of J- P Sent: Thursday, July 24, 2014 9:18 AM To: NT Subject: [NTSysADM] Polling wrong DC Hi all, Quick background - we have 5 remote locations all tunneled to HQ in "star" topology if you will; HQ- 192.168.0.0 site1- 10.0.0.0 site2- 10.0.1.0 site3- 10.0.2.0 site4- 10.0.3.0 site5- 10.0.4.0 I'm trying join a server from site 2 (10.0.0.0) to our domain site 1 (192.168.0.0) , the issue that I'm having is that the server is trying to authenticate against the DC in site 5. Since there is no tunnel between the remote sites it fails, what I'm failing to understand is WHY it isn't trying to authenticate against the DC's at HQ- The server in the remote site has the HQ DNS servers as primary and secondary Ping back and forth via both IP and Name work and the TTL is only under 300ms I have flushed DNS Registered DNS rebooted Even when i ping the domain name it come back with the correct DC, yet when i try to join it back to the domain i get the "no domain controllers could be contacted" and Netmon traces cleary show it's looking for the wrong DC
