Can't Join the domain

[rrdavis07]

We have a new Win2003r2 domain controller with a new domain. This site did not have an AD domain prior to now. We are in the middle of joining the cadre of existing computers to the domain. Most of the XP Pro computers join successfully. A few of the XP Pro and all of the W2K computers will not join the domain, with the error stating that the domain either cannot be found or does not exist. Yes, the computers in question can ping and otherwise navigate to the DC.

Steps we've taken:

1. reboot server. This seems to allow 1 or 2 computers to join, but no more until the next reboot.

2. Mess with DNS Server. Something was corrupt with the DNS service, as there were no SVR (service location) records. Follow another tek-tips thread to restore those. Directly after this, 1 W2K machine joined the domain, but haven't been able to get others to join.

3. The domain was created as a single label domain. There is a kb article detailing problems with single-label domains that we've followed.

We're still having problems, though. Any ideas would very much be appreciated.



Randy Davis, MCP
Southwind Technology Solutions

 

[pgaliardo]

I know you said you did something with DNS on the server side, but are the clients correctly configured for DNS? They should be pointing to the DNS server in your domain, most likely, the first domain controller.

 

[tfg13]

What DNS servers are the clients pointing to?

 

[rrdavis07]

Clients are pointing to the correct DNS server. The DNS server and the DC are one in the same.

Randy Davis, MCP
Southwind Technology Solutions

 

[rrdavis07]

OK, more inforamation.

The domain in question is a single label domain. Have gone to kb300684 and followed it. After a /flushdns and /release /renew, several of the W2k machines allowed themselves to be added to the domain, be we still have a stubborn few...



Randy Davis, MCP
Southwind Technology Solutions

 

[tfg13]

Just as a kicker, on the ones that are still having issues, add a "pointer" in the host file. Just wondering if there are still DNS issues....By the way, are these receiving IP's via DHCP? If so, are they receiving them from the new DC, or from another DHCP server?

 

[u080570]

When you are adding them to your domain, are you using a FQDN (ie: mycompany.com) for the domain name - we have some issues sometimes where we have to do that...

 

[ncotton]

ipconfig /release
....
....
....
ipconfig /renew

try joining again

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[dberg35]

I have had a similar issue and it was an easy fix. Is your domain a .com or .local? Either way all I had to do is when typing in the domain name mydomain is what I normally did on a few machines I had to put the .local after it. Also once I had the proper forwarders in DNS things seemed to be ok.

 

[markdmac]

DNS Settings:

Configure the server NIC to only list itself or other DCs, no ISP DNS gets configured on the NIC TCP/IP properties.

In DHCP, set the DNS scope option to only provide the IP of your local DNS server

For any statically configured IPs, make sure the DNS only lists local DNS servers and not ISP DNS.

In the DNS snap-in on the forwarders tab enter your ISP DNS.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

 

[rrdavis07]

Thanks for everyone's reply. I'll begin looking into the ones that I've not already tried.

I think that the way the domain was originally set up--as a single-label domain (no .local or .com after the domain name) is part of the problem. As I mentioned earlier, I followed microsofts advice configuring clients for a single-label domain name. Worked with some, not others.

I'll try adding the "pointer" to the host file

The PDC (there is only one DC, it is the PDC) serves as the only DHCP server. It points DNS to the correct DNS server.

Randy Davis, MCP
Southwind Technology Solutions

 

[rrdavis07]

problem solved. Goes to show you how a "simple thing" can be overlooked. A tech had put in the wrong subnet mask when installing the server. This put some of our computers on the wrong subnet, and some were on the right one.


Randy Davis, MCP
Southwind Technology Solutions