Name: NCD Date: June 25, 2005 at 22:07:52 Pacific Subject: Account lockout problems OS: Win NT CPU/Ram: P-III (512mb)
Comment:
Hi, I am facing problems connecting to the Win NT server from a Win 98SE workstation. There are over 15 computers that access the server using the same username password. Recently, the account has started getting lockedout in the middle of the session without attempting wrong passwords. The account has been setup for 7 bad logon attempts. But, the server locks the account in the middle of the session. The network was perfectly fine until few days back. The problem has arised suddenly and has been occuring regularly. To enable the account back, I have to manually logon to the server as the admin and unlock the account. Can anyone explain me the reason for the problem with suggestions to resolve it. Thanks.
This may be a reach but you may have a virus or spyware attempting to use the password or a brute firescanner. make sure you scan wtih adaware and spybot search & Destroy on the entire network. Also update your AV and scan
Thanks for your reply. But, I scanned all the computers for any kinda virus etc. ... but the results are coming out clear. The AV are updated to the date and so are OS patches. I tried to look around for a similar problem on the web, but in vain. Any suggestion is appreciable. Thanks.
if no one is typing it in wrong then there is either someone trying to guess it and typing it in wrong or someone is changing it. Have you or anyone else been working with group policies as that could cause it if done incorrectly. I have to ask though, why do you have multiple users with the same username and password? That defeats the entire purpose of passwords.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE