Discussion Locked

NT 4 To Adv Server 2000 Help

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

Ok,
I have been told that NT Server 4 is very bad, so I upgraded to Windows 2000 Advanced Server and I am now having some problems.

I had a Domain setup with NT 4, with no problem, now with AD I am getting all sorts of problems.

All I want isa Domain that I can allow PC's to join, What do I need to do to set this up? I know the dcpromo, but AD don't seam to like to allow PC's to join, says something about the path cannot be found. I want everything to be local.

5 replies

by smeogul

the first thing to do is ensure your dns is set up properly. this is imperative with w2k. if you have set up the zones go in and check that you have a _tcp zone with a record for ldap server, this is essentially your DC.

you also have to be a user allowed to add machines to the domain, in w2k this is "any authenticated user", which by the way is something you should be changing in a big hurry to domain admins or something similar. I always set this to "installuser" and disable the account until I know we are adding machines... that way nobody will be adding anything without your knowledge.

by timwalsh

One other possibility may be the domain name you are using to add the workstations.

If you are adding a client that is pre-Win2K, you MUST use the NetBIOS domain name when asked to specifiy the domain to join. In your case, the NetBIOS domain name should be the same as your old NT4 domain name. If you try to join a Win2K or newer client, you must specify the full AD domain name .

This discussion is closed to new replies.