Discussion Locked

User account constantly locked out...

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

Hello,

I have a user that has his user account constantly locked. I'll unlock him then after a couple of hours, the account becomes locked again. The user isn't logging in incorrectly. It just seems to happen. We have an NT 4.0 domain and the user is on a Windows 2000 PC. Any thoughts on how to fix this?

Thanks

7 replies

by haagr

Are you being hacked? I found that hackers busted into one of our Windows 2000 machines and locked out the Administrator account, so only their "admins" account could log in. See if typical hacker services like firedaemon.exe or DWRCS.exe are running.

by rabbit_runner

I believe that the user has recently changed his password. This same user also has a service or application, which uses his user account, assigned to it. Since the password has been changed, it will also need to be changed on the particular service or application using his user account. This service / application attempts to start, but fails. After a number of times (specified by your account policies) the account becomes locked out. Note: I have also had this happen if the user is logged into another computer and simply locked the workstation. The account is still using the old password.

One way to check is to view the event logs. Find out which computer the error or problem is coming from. Also check with the user, what computers he uses, what services may use his user account, or what application is dependant on his user account.

You will need to do some reserach to find where the problem is.

Best of luck.

by tke402

Found out user was logged on to several test machines on the LAN. User changed password but was still logged on to the test machines with different password.

by alioop

We had a similar problem. It turned out to be related to the use of Terminal Services which were closed rather than logged out. This kept causing a lock-out. When we made sure that we logged out of Terminal Services correctly, the problem went away. Hope this helps.

This discussion is closed to new replies.