Solution: No ports needed to be open since sonicwall VPN's allow all traffic by default. I just pointed the client machine's primary DNS to the DC and it worked.
Thanks guys, great site. -Will
How can I create a static entry, so when the computer tries to connect to our domain, it will be pointed to the DC (10.0.0.21). I would rather not involve a DNS server in this.
I tried setting the DC as my secondary DNS within TCP/IP settings but that didn't work.
The exact error is as follows: "AN AD DC for the domain "x" could not be contacted. Ensure it was typed correctly."
"The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "X.com":
The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.X.com"
The two networks are connected over the internet by SonicWall VPN Routers. Do I need to unblock any ports?
1) using a KB article from 3 years ago written for an OS 2 revisions behind the one you are using generally is not going to work.
2) What is your DNS server? If you can talk to the DC via ICMP are you doing it via IP or DNS?
3) You need to make sure you have the proper ports allowed through your firewalls/vpn config.
4) What is the exact error you are getting when you try to connect the machine to the domain?
The LMHOSTS file would be used for Netbios names. Your Windows 7 machine will need to resolve the FQDN (DNS name) of the domain you need to add it to. The DNS server you are using on your Windows 7 should be able to resolve (or forward to a DNS server that can resolve) the Domain in question. If neither of those are true then a quick fix would be to add the full domain name i.e.
coolest.dude.com to the HOSTS file using the IP you can ping.
You will also need to ensure that traffic is open from your subnet to the remote location DC.
User contributions licensed under CC BY-SA 3.0