Primary Domain is missing

[cthreepo]

Please can you help.

At random intervals client PC's are displaying the message; "The system cannot log you on to this domain because the systems account in its primary domain is missing or the password on that account is incorrect".

What does this mean?

The password for the account in question is fine i.e. it works on other PC's.

Thanks.

let's help one another, not hinder.

 

[Xemus]

http://support.microsoft.com/defaul...port/kb/articles/Q244/6/71.ASP&NoWebContent=1

http://www.jsiinc.com/SUBN/tip6700/rh6744.htm

Any luck?

http://www.closedsocket.com

 

[cthreepo]

No, I am using Windows 2000 Server not NT4 but thank you for the link. I will see if theris anything I can apply from it.

Cheers

let's help one another, not hinder.

 

[Xemus]

You might try logging in as local admin, removing the machine from the domain, and readding it to the domain. Note that I mean the client that is having connection issues, not the server.

http://www.closedsocket.com

 

[cthreepo]

That seems to work, thanks.

Any ideas why the problem is occuring? The PC's seem to be dropping like flies at the moment!

Cheers

let's help one another, not hinder.

 

[CluelessJon]

Are you sure this is this not a network connection issue ?





Regards

Jonno BrainDump Specialist
MCSE(NT) MCSA(2k) CCNA

 

[cthreepo]

No I'm not sure. How can I tell this for sure?

Thanks

let's help one another, not hinder.

 

[cthreepo]

Weird, just went into one of the IT rooms and at least 5 PC's are now displaying "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 just inspected the NIC card and cable and all seems fine.

Any ideas anyone?


let's help one another, not hinder.

 

[CluelessJon]

Can you ping the DC from a suspect PC ?

Have you removed a computer account and recreated it on the server and tried ?

Have you removed a suspect computer from the domain, changed ti to work group then re-added it to the domain ?

Anyway I paused the netlogon service on the BDC and try ?

Just some idea's



Regards

Jonno BrainDump Specialist
MCSE(NT) MCSA(2k) CCNA

 

[CluelessJon]

The best way to troubleshoot the logon time is to enable Userenv Debug
Logging to see what is going on during the logon process.

Here is an article that will help you enable userenv debug logging:

221833 How to Enable User Environment Debug Logging in Retail Builds of
Windows

http://support.microsoft.com/?id=221833

Regards

Jonno BrainDump Specialist
MCSE(NT) MCSA(2k) CCNA

 

[cthreepo]

Hi Jon,
This am I was able to to remove and then add to the DC a PC that was causing problems initailly. This cured the problem for that particular PC, but I then found that 3 other PC's then decided to to display the same message regarding the Primary Domain. I do not understand why and now it seems that many PC's are just 'dropping' all over the place.

I will have a look at the link you sent as soon as I've sent this.



let's help one another, not hinder.

 

[BOFH1]

Are there any NT4 servers in the domain of id it pure 2K active directory?

If it's 2K i think a problem with the stations not sychronising with the DC can cause this problem, i'm not certain but it's work looking into.

 

[BOFH1]

Oh sorry i also meant to say that if you are maintaining an NT4 PDC for compatibility this can occur.

 

[cthreepo]

Well, there is a CD Server that sits on NT4 and this is part of my network.... are we saying that this could be my problem????

let's help one another, not hinder.

 

[BOFH1]

Only if it's still configured as a PDC. I've not seen this problem first hand but i've read about it.

 

[search66]

We had this problem on our network, and there are a number of things you can check out.

1. Make sure DHCP is running and configured properly.
2. Depending on how you have DHCP configured, you may need to manually put in the DNS and WINS entries into your workstations (or use an LMHOST file).

Another way to check for problems, is to log in locally... and do an ipconfig /all

See if the IP is in your range or not. Release/renew... reboot.

 

[cthreepo]

No, it's in 'Open Access Mode' which essentially means that it is neither a PDC or BDC. The workstation literally see it as another CD drive. Users do not log into it as such.

BOFH1 is there anything you can remember reading that pointed towards a solution for this problem? The reason I ask is that it is a real pain. I'm having to remove and then add again computer accounts to get PC's logged on!

Thanks.

let's help one another, not hinder.

 

[BOFH1]

Sorry i can't find the doc that i saw it in.

Have you made and changes recently network wise?

or rebuilt any of the stations or Ghosted them?

 

[cthreepo]

All of my client PC's have been ghosted recently but all were working fine. Occasionally the odd PC would report this error but it was managable. Now the problem is happening with dozens of PC's.

Would ghosting be an issue if all PC's were SYSPREP'd and had different names and different static IP's given to each one?

let's help one another, not hinder.

 

[BOFH1]

Any error messages in the event log?

I'm stumped to be honest.

I think the system account automaticly changes its password every 7 days, mabe there is a problem the first time it is trying to do this.

We Ghost all our stations but i've not encountered this before.