Yep , everthing eas defined properly as this was a dc that was for removed, then readded/promoted.
Date: Wed, 6 Aug 2014 07:31:58 -0400 Subject: Re: [NTSysADM] Polling wrong DC From: [email protected] To: [email protected] Are the subnets for the ad sites defined and in ad and that the DC object is assigned to the correct site instead of the default first site? Z On Jul 24, 2014 12:18 PM, "J- P" <[email protected]> wrote: 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
