2000 Server - client computer can't login to domain

Schoolies

Senior member
Oct 9, 1999
495
0
76
I have Windows 2000 server installed with active directory, dhcp, dns... the works. Everything works fine. I have three other computers that I have connected to it logging in using domain user accounts. All three were working at one time but then I started messing around with group policies and stuff like that, now one computer (doesn't matter what username i put in) will not log on to the server. It can log in locally.

The message I get is:
"The system cannot log you on to this domain because the systems' computer account in its primary domain is missing or the password on that account is incorrect"

I have gotten rid of all the GPOs and i have deleted and put back the computer account and user account many times.

I renamed the computer name and still nothing.

Any help is appreciated.
 

zetter

Senior member
May 6, 2000
328
0
0
On the PC that's misbehaving, remove it from the domain (add to some bogus workgroup).

Remove all entries relating to that PC from the server.

Go back on to the PC again and add it back in to the domain again.

That should do it.
 

Woodchuck2000

Golden Member
Jan 20, 2002
1,632
1
0


<< I have gotten rid of all the GPOs and i have deleted and put back the computer account and user account many times. >>


Once you deleted the account from the OU, you'll have to re-join the computer. You can't just create an account with the right name and hope it'll work. Do what zetter says and you should be fine.
 

Vegito

Diamond Member
Oct 16, 1999
8,329
0
0
yeah, once a while i get that too, w/o messing with policies... something weird.. but after dis-join and rejoin, everything works again.. good luck
 

Schoolies

Senior member
Oct 9, 1999
495
0
76
Ok, now I get a Network Identification error when I try to rejoin the domain.

It says:

The following error occurred attempting to join the domain "mynetwork":
No mapping between account name and security IDs was done.


I tried changing the machine name and changing account names but it gives me the same message.

Before I did this, I did get rid of the computer and accounts that were associated with the problem PC and I did move that machien to a bogus network.