Question

Locked

Computer account disabled?

By TonytheTiger ·
Two machines in two days failed to login with "Domain not found or Computer account disabled" message.

I logged on as local admin and got IP address, internet access, etc.

Active Directory Manager did not show computer account disabled.

I fixed it by:

From the computer, remove from domain, restart, rename computer, restart ...

From Active Directory Manager: create new AD computer account, delete old account ...

From the computer: Join domain, restart, rename computer to old name, restart.

What causes this? Is there an easier way to fix it in the future?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

More info here...

http://technet2.microsoft.com/windowsserver/en/library/91a98c38-38c5-49dc-83bf-e69d8e1dbbfa1033.mspx?mfr=true

http://technet2.microsoft.com/windowsserver/en/library/2ee8cf56-7dcc-4c79-af46-737c40abbf8b1033.mspx?mfr=true

http://support.microsoft.com/kb/263936

http://support.microsoft.com/kb/320187

Please post back if you have any more problems or questions.

Collapse -

Actually I tried ...

by TonytheTiger In reply to More info here...

"Reset Account", but it didn't seem to help.

What I don't understand is how it happened. Both computers are daily use machines, never turned off (but rebooted once in awhile) that have never been disconnected long enough for the machine passwords to get out of sync.

Good info though... Thanks!

Collapse -

Then somewhere on the server..

There must be some box(s) that are not ticked for saving the settings IE. passwords, remote settings etc. Just a hunch.
:)

Please post back if you have any more problems or questions.

Collapse -

I'll look into it.

by TonytheTiger In reply to Then somewhere on the ser ...
Collapse -

I have seen a few causes of this.

by Kenone In reply to Computer account disabled ...

Check your event viewer on the server, look especially for DNS errors, DHCP errors and Journal wrap errors. I have seen combinations of all three and almost any two cause this behavior. Easiest fix till you get the server squared away, drop out of the domain and join a workgroup, reboot, rejoin domain. Don't let them reboot again until you get the server fixed.

Back to Networks Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums