Discussion Locked

accounts locking

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
For the last day or so, I'm getting users' domain accounts locked out just by logging in on their Win9x machines. This is an NT4 domain with about 20 BDCs. Bad password limit is set to three and I'd hate to bump it up any more. Any suggestions?

9 replies

by rserao

Had a similar problem that turned out to be a hammered client.. Un-installed the client, rebooted, re-installed client and all was well with the world.. Had it happen to about 15 clients on the same segment...

by shanghai sam

I've had removing/adding the client work in most cases, but in this case I did that on about a dozen machines and the next morning some of those accounts were locked again. Still investigating...

by bhrdwh

NT has option to reset blocked passwords after certain time limit (say 2 mints). Set that & your thru. Identity which users / systems are causing this problem, isolate them.
20 BDCs !! Good god, it would be a problem to synch the entire SAM database on your domain. I suggest you have 1 PDC & about 4-5 BDCs at most, no more.
Akash

by uffe.sommerlund

Hi there

I have also been working in such an inviroment, what you can do.

In the NT Policy set the unlock account after 15 Min, this will save you for a lot of trouble.

by kerst11

Try this: Go to the Win9x machine that the user keeps getting locked out of the domain on and delete his/her .pwd file. It should be in C:\Windows. Then unlock the account on the Domain Controller and have them log in on their machine.

by randylyman

Removing the .pwl files is an excellent suggestion; it makes sense if the stored password is different. Unfortunately, it didn't help in this case since most searches for *.pwl came up empty. The problem seems to be that our Win2000 NAS server was not properly seen in our NT4 domain and was trying not to allow connections. After upgrading the PDC to Win2000 server and having the NAS leave/join the domain, the problem seems to have gone away (fingers crossed). Thanks for the input!

This discussion is closed to new replies.