Why can't we join our Windows XP machine to our Win2003DC's domain without adding the ".com" suffix?
February 20, 2008 1:06 PM Subscribe
Why can't we join a brand-spankin-new, from-scratch-install-of Windows-Xp-Sp2 machine to a brand spankin new Win2003 Domain without needing the .com suffix?
Basically, we've got a switch set up, with a couple test pc's all plugged into it (and we're sure all the ports are good, nics are good, etc). There's no other domains, it's not part of another network, not of the systems were ever part of another network. There's nothing on 'em but the o.s.
I.e., if we create the machine we are going to add, first, on the server in AD, then try to join it to the domain from the XP box, it says "no domain controller can be found". UNLESS! we add the ".com" suffix to the domain name. Then we can join just fine.
What is also weird is - if we then make say, another from-scratch test system, and install Windows Server 2003 on it, instead of XP,and say, just make that a file server - THAT system can join the test DC's domain just fine. No need for the .com suffix.
DNS is live on the DC (this is a test mini domain we're using, with only a single brand new DC), and the XP box easily gets a DHCP'ed IP from the DC.
???
Basically, we've got a switch set up, with a couple test pc's all plugged into it (and we're sure all the ports are good, nics are good, etc). There's no other domains, it's not part of another network, not of the systems were ever part of another network. There's nothing on 'em but the o.s.
I.e., if we create the machine we are going to add, first, on the server in AD, then try to join it to the domain from the XP box, it says "no domain controller can be found". UNLESS! we add the ".com" suffix to the domain name. Then we can join just fine.
What is also weird is - if we then make say, another from-scratch test system, and install Windows Server 2003 on it, instead of XP,and say, just make that a file server - THAT system can join the test DC's domain just fine. No need for the .com suffix.
DNS is live on the DC (this is a test mini domain we're using, with only a single brand new DC), and the XP box easily gets a DHCP'ed IP from the DC.
???
When you specify the FQDN of the domain controller, the client resolves the name using DNS. When you don't, it uses WINS if that exists, or NetBIOS broadcasts if it doesn't, if I recall correctly. I'm guessing that you aren't running WINS, and that your switch is blocking broadcast messages. This is based on my admittedly hazy memory of Windows Networking, so I welcome any corrections.
However, you should just use DNS resolution and be done with it.
posted by me & my monkey at 5:47 PM on February 20, 2008
However, you should just use DNS resolution and be done with it.
posted by me & my monkey at 5:47 PM on February 20, 2008
This thread is closed to new comments.
posted by phil at 3:09 PM on February 20, 2008