Discussion Locked

Account Locked Out Problems

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

We recently moved out of our Windows NT Small Business Server into a Windows 2000 Server Domain with 2 Domain Controllers.
I am having a problem with one of the user accounts in that it gets locked out frequently. The user has not put bad passwords in, but the user can go for about 2 hours at the most before the Account gets locked out again. There were no problems getting the user on the domain. The user has also shutdown the PC at night and when the PC is started up in the morning the user's account shows that is is locked out again. When I set the user's account to unlocked I go ahead and force the replication between the 2 servers. None of the other users in the office are having this problem. There have not been any Event Viewer messages about accounts being locked out or any problems pertaining to that. I am at a loss here on what could be the problem. Any suggestions regarding this topic would be greatly appreciated. Thanks for the help.

19 replies

by tim

What is the client OS and are you running Proxy or Exchange on the server or on a different server within the domain? I have seen similar problems but the solution depends on some variables not detailed here.

by bschmelz

Client OS = Windows 2000 Pro w/ SP2. Both servers also have Win2K SP2 on them. We are running Exchange 2K SP1 on the 2nd Domain Controller. The 1st Domain Controller basically just has Active Directory installed on it and was the 1st one we installed AD on (Primary). We installed AD on the 2nd one in order to replicate the AD and to use AD w/ Exchange.

We also have an ISA Server that is acting as our Proxy Server, but it does not have Active Directory installed on it.

Thanks for the reply.

by mikek

We recently upgraded our PDC to Windows 2000, and have 2-3 accounts that just seem to automatically lock on their own. I was told this can affect a 95, 98 or 98se client, and have to do with how the O/S's handle network shares vs the Windows 2000 server. Apparently Microsoft has a fix but I have not been able to find it.

by daniely

Same here guys. Running Win2k Servers and I'm running Win95B. My acct will locked itself out even if I'm not using my PC. Hope someone has an answer or the direction to go to.

by ryansmith

Hi,

I am currently experiencing the same problem.
Accounts are randomly being locked out but I have no way of determining wheather it is a user problem or a Windows Problem.

I suspect a windows problem but am not sure where to go from here. Did you ever find a solution to this problem?
If so please could I ask you to let me know your solution.

Thanks and regards,
Ryan

by ryansmith

Hi,

I am currently experiencing the same problem.
Accounts are randomly being locked out but I have no way of determining wheather it is a user problem or a Windows Problem.

I suspect a windows problem but am not sure where to go from here. Did you ever find a solution to this problem?
If so please could I ask you to let me know your solution.

Thanks and regards,
Ryan

by monte admin

I have 2-3 accounts that randomly lock out. Replaced the computer for one, user but they still use Win98 for a legacy application. Please help.

Bryan

by misssysadmin

My problems didn't start until I imposed password policy of expiration in 90 days. Only a few people get locked out almost like clock work during the day. They all run Windows '98 SE with both domain controllers running Windows 2000. I don't have a problem with my logon account until I log on to one of the known problem machines and bam! I get locked out as well. If anybody finds a fix for this it would be really appreciated!

by nichol.ma

We've been a bit slow moving to Windows 2003 Server, hope this is still useful to someone. We encountered the lockout problem ourselves. A single account would continously get locked out and nothing would show up in the event logs. We re-created the account (same name) and the problem persisted. We made a new account (different name) and the problem was gone. When we renamed the new account to the original name, the problem came back. We deduced that the user was logged in to another machine that he didn't regularly log into. We found it sitting in a closet in another building. He was still logged in and had been for weeks. When that machine was shut down, the problem went away. Presumably the user had changed his password and the logged in machine was no longer able to automatically re-authenticate disconnected drives (guessing). Sorry, we're mostly a Novell shop and used Novell utilities to determine that the user was connected in more than one place and to get the IP. I don't know how to do it in Windows.

by nichol.ma

The problem I mentioned above was on a Windows 2000 Professional workstation connecting to NT4 Domain.

by mr_cadman

I had a machine logged on with a non-admin account but had used an admin account to map a network drive (large format printer logging purposes). When I changed my password, the computer with the mapped drive did not get updated, therefore my account kept getting locked out. I reconfigured the logging process, and no longer needed the mapped drive, then my lockout problem went away. Hope this gives someone some ideas.

by ndcold1

Have the user log out then do an nbtstat -a (username), this should tell you where the login is if that is the problem.

by deny

Knowledge Base

Locked-Out Account That Is Reset at a Different Domain Controller May Be Locked OutArticle ID: 278299

Article Last Modified on 9/26/2005

--------------------------------------------------------------------------------
APPLIES TO

Microsoft Windows 2000 Service Pack 1
Microsoft Windows 2000 Service Pack 2
Microsoft Windows 2000 Advanced Server SP1
Microsoft Windows 2000 Advanced Server SP2

--------------------------------------------------------------------------------

This article was previously published under Q278299
SYMPTOMS
When you are using account-lockout policies in a domain with more than one domain controller (DC), if an account was previously locked out and then unlocked by an administrator, the account may be locked out after only one bad password attempt.
CAUSE
This problem can occur because Windows 2000 maintains a bad-password count for each user. This count is the number of bad password attempts that have been made since the last successful logon. When user account details are replicated between DCs, the locked-out state is replicated. However, bad-password counts are not replicated between DCs.

If a user is locked out by exceeding the maximum bad-password count that has been configured by a policy on the authenticating DC, the user account is marked as locked out, and the locked-out state is replicated to other DCs.

If an administrator then unlocks the account, the bad-password count for the user is set to zero on the DC that is processing the unlock request, and the unlocked state is replicated to other DCs, but the bad password count (now zero) is not replicated to other DCs.

Because of this, if the DC that authenticates the user's next logon attempt is the DC that originally locked out the user and the user account was unlocked on a different DC, the authenticating DC sees an unlocked account that has a bad-password count at the lockout threshold that has been set by a policy.

Under the preceding conditions, one bad password attempt is sufficient to lock out the same account again.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

Date Time Version Size File name
-----------------------------------------------------------------
5/31/2001 11:13p 5.0.2195.3663 501,520 Lsasrv.dll(56-bit)
5/31/2001 03:30p 5.0.2195.3649 354,576 Advapi32.dll
5/31/2001 03:37p 5.0.2195.3649 519,440 Instlsa5.dll
5/31/2001 03:31p 5.0.2195.3649 142,608 Kdcsvc.dll
5/30/2001 02:55p 5.0.2195.3649 209,008 Kerberos.dll
5/29/2001 09:26a 5.0.2195.3649 69,456 Ksecdd.sys
5/29/2001 09:26a 5.0.2195.3649 501,520 Lsasrv.dll
5/29/2001 09:26a 5.0.2195.3649 33,552 Lsass.exe
5/31/2001 03:31p 5.0.2195.3652 908,560 Ntdsa.dll
5/31/2001 03:31p 5.0.2195.3649 382,736 Samsrv.dll

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
MORE INFORMATION
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product

For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Additional query words: kbDirServices

Keywords: kbhotfixserver kbqfe kbbug kbdirservices kbenv kbfix kbnetwork kbsecurity kbwin2000presp3fix kbwin2000sp3fix KB278299

--------------------------------------------------------------------------------

Send feedback to Microsoft

? Microsoft Corporation. All rights reserved.

by francisjakee

It turns out that when she changed her password, the problem started.

Here is what I did, I've ask the user to give me the old password she/he used before.

Upon entering the old password, no more lockups. You can give it a try.

by rwright142

I know this topic was started many years ago but I am having this problem with users now. Two of them are on Vista and have recently changed their passwords. I have others on XP that have changed theirs but are not reporting this.
One user received her new laptop (with Vista) early in the week and had no problems at all. I reset her password so I could configure the laptop for her and she changed it afterwards. No problems for a week. Then on Monday she we getting locked out. After she rebooted all is ok and no more problems with her.
One other user on Vista had the problem and he cleared all "stored passwords" and everything was ok. He started having the problems today too. He was logged in, sending emails to me and was trying to log into a terminal server. My policy is 5 attempts then lockout for 10 minutes. He tried logging into the terminal server 1 time and was told he was locked out. I unlocked him and he was ok and no more problems so far.
We are running server 2003. I have over 35 users but only 2 have had this the most and it's never because they entered the password more than the 5 times. I'm watching the logs and it's not showing where they typed it in wrong more than the 5. It is being logged because I see some failed attempts just not the 5 before the "locked out" message.
Any ideas?

by echikoz

i have experienced that before, but some those problems have been resolved by resetting the user's password. however, i have not fully understood what causes the locking of the account in that manner.

by nasir.naeem

Search for Microsoft lockout account administration on the microsof.com website.

By using the tool you will be able to do both server side and client site tracking. Personally speaking found more success by running on the machine suffering from the problem. Just copy the ALxplockout.zip contents into the windows\system32 folder and restart.

Thanks

by bhenganda

Your account has been locked 81003003

Please send us instruction how to unlock my account blaupunkt_18@yahoo.com.Asap ty

This discussion is closed to new replies.