Discussion Locked

Adding a 2000Pro to a NT domain

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

When trying to add a computer to the NT domain we receive the following error
"Your computer could not be joined to the domain becuase the following error has occured: Invalid Signature"
We are using domain administrator rights to add the computer after logging into the computer with local administrator rights. Tried to add the computer through Server Manager.

13 replies

by nicholasp

Try adding the PC with a diffrent name. Make sure that the name you are giving the PC is not already part of the domain

by jennisonn

I have 9 other computer with the same problem and different names, these computer were ordered from a big name company, and of course they are no help.

by jack republic

if the computer has out of date bios ,than
this problem occures.if this is the case contact the motherboard menufactare for update.

by joseph moore

My thought is to check the security profile the 2KPro boxes are using.
If they are configured to use the Highly Secure security profile (hisecws.inf) you will not be able to connect to NT4 servers, since that level of security will only use Kerberos, not NTLM.
Make sure the 2KPro boxes are configured to use the basic security profile (basicwk.inf).

Article ID: Q234926 talks about the different security profiles.

Hope this helps.

by mphoffar

Just a thought, but maybe running something like ghstwalk or newsid to create a new sid on the machine before adding it...

Mark

by curlergirl

Have you tried adding the computer from the workstation end instead of through Server Manager? On the workstation, right click on My Computer, click Properties, go to Network Id. tab, then click Network ID to run the wizard. This will walk you through joining the domain and adding the computer account to the server at the same time. I've never tried it the other way - adding a Win2K machine from Server Mgr. - but I've never had a problem doing it from the client end. Hope this helps!

by ovidiu

Had the same problem, and I realised that i was using the Join to a Network wizard, by using the administrator account for the domain controller i had in my company. Try using the administrator account for the local machine instead, and run the Jointo a Network wizard, by following each of the steps U walk through. Be aware of adding the local Administrator account to the Administrator group, and in the moment the wizard asks U for the account with privileges to add a computer to the domain, use the domain controller administrator account.
Check to see if U don't have already a machine with that name in the domain.
Good luck.

This discussion is closed to new replies.