FWIW , I’ve never set this locally for DHCP connections. Unless you are 
statically addressing clients, I’d suggest you’d want to leave this blank and 
instead manage centrally by pushing DHCP scope option 015. 

 

I do this and it’s never been an issue…

 

-sc

 

 

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Chenault
Sent: Tuesday, March 11, 2014 9:13 PM
To: [email protected]
Subject: Re: [NTSysADM] unable to join domain

 

Check that the domain name in DNS setting for the localhost matches the domain 
you're trying to join. Don't leave it blank: fill it in. 

 

I've come across the exact situation before and that usually fixes it. 


On Mar 11, 2014, at 17:05, "J- P" <[email protected]> wrote:

        thought of that, changed the pc name a couple times already no dice
        
         
        
         

________________________________

        Date: Tue, 11 Mar 2014 16:56:37 -0700
        From: [email protected]
        To: [email protected]
        Subject: Re: [NTSysADM] unable to join domain

        Computer account already exists in Active Directory?

        --
        Kevin Kelly
        Director, Network Technology
        Whitman College

         

        
________________________________


        From: "J- P" <[email protected]>
        To: [email protected]
        Sent: Tuesday, March 11, 2014 4:31:30 PM
        Subject: [NTSysADM] unable to join domain

        Have a new pc (vostro 270) delivered to our field office, they did a 
win 7 pro downgrade,
        I spent the better part of the day (off and on) trying to join the 
domain, continuously got the  "could not contact a domain controller...." it's 
not in English I'm not going to copy paste the error.
        
         
        remote office has a 2008r2 DC/DNS/GC;
        1. can ping by name and ip (both ways)server to workstation and vice 
versa;
        2. we are VPNd to HQ and the can ping the FSMO over VPN;
         3. can remote desktop both ways. 
        4.did a manual config of IP and DNS servers 
        5. turned off firewall bot server and workstation
        6. tried manually applying DNS of HQ Domain Controllers
        7. Can browse network and connect to the servers share (with alternate 
credentials of course)
         
        is there any possibility, that there is an issue with the OS 
installation? 
         
        I have joined PC's remotely before to this and all field offices and 
have never had this issue
        
        I'm going to try netmon when I get home later
         
        but getting a bit frustrated

         

Reply via email to