Discussion Locked

NT4 server cannot join to AD

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I try to join the NT4 server into the Windows 2000 Active Directory Services but got an error message:
"The domain controller for this domain cannot be located."
I can ping the DNS server by its ip address, netbios name and FQDN. I also created the computer object and user account for the NT4 server in AD, still dosn't work.
PLEASE HELP!

7 replies

by raffi_

Wow.
There is just so much that you did not say. Is the NT server a PDC? BDC? Stand-alone? Remote? Local? Same subnet?

Anyway - you are getting some communication between the two. That's a good thing. Try this KB article:

http://support.microsoft.com/support/kb/articles/q242/4/32.asp

If that does not apply you have some research to do. I would suggest this site as one of the best resources I have come across:

http://www.labmice.net/ActiveDirectory/default.htm

Regards
Raffi_

by ian mclaws

Try installing an active directory services client on the 4.0 server. Nt 4.0 didn't come with one, by default.
However, a Windows 2000 AD setup also has at least one domain controller, usually the first one loaded, running a service called the PDC emulator, that allows NT 4.0 clients to access what they think is the PDC. As long as your server is not a domain controller (if it is, you have no choice but a reload), it should be able to connect to the domain using this service. Make sure that your DNS setup has the DC entries in it, so that the NT 4.0 server can find it.

Good luck,

Ian

by andygm

I assume your DNS is your active directory enabled DDNS?? When you run DCPROMO if it cannot located a DDNS capable server it will ask you to create one.. Within your DDNS snap in do you have the following under your main.. Domain Forward Lookup folder tcp and a few other folders?? When you ran DCPROMO if you named your active directory domain without a .com or other then these folders are not created.. And DNS does not work propely and you will get RPC errors and others. Microsoft recomends that if you do not want to have your domain with the . whatever after it (I dont like it) to name it domainname.local -- If you dont like this then their is a win2k server resource kit utility that is a .vbs script that you run and will create these folders for you manually and you should be able to install the new server within your AD domain no problem.. As one of the other gentleman said if it is a PDC or a BDC you will need to demote-- Their is a not well known utility out their Called UPROMOTE that will move member server to BDC or PDC and vice versa, I have used it with much success in NT 4 world....

This discussion is closed to new replies.