We’ve run into this on a pretty common basis in our remote offices. To the best of my knowledge every instance so far has been resolved by forcing the dns search list to contain the domain we’re trying to join and making it first on the list. Because of some client related configurations we actually have domains on the search list that aren’t on our network and sometimes people get the machines configured with one of those first in the list and it screws things up.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of Christopher Bodnar
Sent: Thursday, March 13, 2014 8:56 AM
To: [email protected]
Subject: Re: [NTSysADM] unable to join domain
Did you resolve this yet?
If not how are you specifying the domain on the client when trying to join?
FQDN or NetBIOS? Did you try both?
Is the client's IP address in a subnet that is defined in Sites and Services?
Is there a DC for that subnet in Sites and Services?
From the client can you lookup the srv records for the domain controllers? For
example if you do this from the client, do you get the expected results (change
for your domain of course):
nslookup -type=srv _LDAP._TCP.dc._msdcs.contoso.com
To me this sounds like a DNS issue at the client side, somehow the client isn't
getting the right SRV records for the domain controllers.
Christopher Bodnar
Enterprise Architect I, Corporate Office of Technology:Enterprise Architecture
and Engineering Services
Tel 610-807-6459
3900 Burgess Place, Bethlehem, PA 18017
[email protected]<mailto:>
[cid:[email protected]]
The Guardian Life Insurance Company of America
www.guardianlife.com<http://www.guardianlife.com/>
From: J- P <[email protected]<mailto:[email protected]>>
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>,
Date: 03/11/2014 07:33 PM
Subject: [NTSysADM] unable to join domain
Sent by:
[email protected]<mailto:[email protected]>
________________________________
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
________________________________
----------------------------------------- This message, and any attachments to
it, may contain information that is privileged, confidential, and exempt from
disclosure under applicable law. If the reader of this message is not the
intended recipient, you are notified that any use, dissemination, distribution,
copying, or communication of this message is strictly prohibited. If you have
received this message in error, please notify the sender immediately by return
e-mail and delete the message and any attachments. Thank you.
<<inline: image001.jpg>>
