Something very odd is happening. We have a Windows Server 2003 computer that is NOT part of our domain. It is simply just serving up files via file shares (don't ask me why they used Win 2k3 for a simple fileserver).
Anyways I'm attempting to join it to our domain and it's giving me the dreaded
A Domain Controller for the domain <domain> could not be contacted
Clicking details it's giving me:
The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR)
Which is very odd because I can use nslookup to successfully query the NS for the DC's FQDN and it comes back with the right IP.
nslookup -q=srv _ldap._tcp.dc._msdcs.<domain>
Brings back the correct info:
Server: <dc name>.<domain> Address: xxx.xxx.xxx.xxx _ldap._tcp.dc._msdcs.<domain> SRV service location: priority = 0 weight = 100 port = 389 svr hostname = <dc name>.<domain> <dc name>.<domain> internet address = xxx.xxx.xxx.xxx
I can ping the DC from the fileserver and I can ping the fileserver from the DC.
What the heck is going on?! Why can't my fileserver join our domain?
We only have 1 DC set up on our small network (less than 20 users). Surely, I'm missing something?
EDIT: Oh, yeah, the DC is also the DNS server and on the fileserver it's primary DNS server is the DC. EDIT2: The DC is a Win Server 2k3 box