USERS REPEATEDLY LOCKED OUT

  • Thread starter Thread starter Alexander.Koppelman
  • Start date Start date
A

Alexander.Koppelman

Hi!,

we are working at the folowing problem:
In our domain(win2000server, AD) there are some problems with users
accounts beeing locked repeatedly. Even a few times a week. We are
looking at the following things:
- Drive mapping on logon, maybe windows maps drives bofor logon with wrong
credentials
- bootlog, if there are some irregularities
- Possible Errors in loginscript
- IE advanced settings
- Permissions user accout
- Account setup errors/neglencies

These are the things we asked for at the helpdesk concerning these users,
to start looking. Maybe anyone has encounterd this problem before and can
give us a new insight or some ideas,

Thanks in advance,

Alex
 
Had this occur once when a service was running under the same account as a
domain admin user. when the domain admin user changed his password, the
service kept locking out his account when it tried to start up.
 
Understood, but we work with users within a very restriced environment,
so no admins there. can it be that windows tries mapping a drive before
the user loggs on|?









From: "Paul Hadfield" <[email protected]>

Subject: Re: USERS REPEATEDLY LOCKED OUT

Newsgroups: microsoft.public.win2000.networking



Had this occur once when a service was running under the same account as
a
domain admin user. when the domain admin user changed his password, the
service kept locking out his account when it tried to start up.
 
I don't know how long this has been happening but FYI Microsoft recommends
that if you use account lockout to use no less of a threshold of ten bad
attempts as a single bad logon attempt by a user can cause several bad logon
attempts at the domain controller. Other things to check are if the use is
using stored credentials for XP Pro computers, Scheduled Tasks, applications
that can store user credentials, drive mappings with persistent credentials,
being logged onto multiple computers after a password change, bad keyboard
or user trying with cap locks on, other users attempting to use that user's
credentials, or even malware. The link below can help and you may want to
try to use netlogon logging to see where the failed logon is originating
from by checking the log for failed logons via transitive logon. --- Steve

http://www.microsoft.com/downloads/...9C-91F3-4E63-8629-B999ADDE0B9E&displaylang=en
 
Hi!

Thanks a lot for your reply. Ill explain what our plan of attack will
be. We try to load the ALTools from microsoft.com, This way well get
some, we beleive, valuable log information.
We realized that we still not know enough of this problem.

TNX

Alex
 
Back
Top