RE: ID Monitoring??

[Bryann Thomas]

Is he connecting to network resources and then changing his password? W2K will re-establish network drives at a regular interval using the credentials that were supplied when first connected. If he's changed his password since manually connecting to shares, this can cause a lockout. We've had a few users here having the same problem. Always logout and back in again after a password change to be on the safe side. -----Original Message----- From: Kelly Borndale [mailto:[EMAIL PROTECTED]] Sent: 22 August 2001 13:21 To: NT System Admin Issues Subject: Re: ID Monitoring?? Why not just change the password to what he thinks he it is?  Is he able to login at all?  Are you able to see where the bad logins are coming from?  Could he have possibly installed a service on the win2k machine using a different password? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ K.Borndale   [EMAIL PROTECTED] -home email ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ----- Original Message ----- From: Winsor, Marc [IBM] To: NT System Admin Issues Sent: Wednesday, August 22, 2001 9:00 AM Subject: ID Monitoring?? I have a user who is constantly getting locked out of his account.  He claims that he isn't typing in a bad password 3 times (the lockout number) but that it just suddenly happens.  What is the best way to monitor his ID to determine what and when the bad password attempts are happening?  In checking through the event logs on the BDC's I don't see anything, or else I'm not recognizing it for what it is. I am in an NT4 domain.  We have multiple BDC's.  The user is having this problem when they log on locally to the network and also when RASing in. They have 2 machines, a W2K and a Win98 machine that they use. Any help is appreciated. Marc http://www.sunbelt-software.com/ntsysadmin_list_charter.htm http://www.sunbelt-software.com/ntsysadmin_list_charter.htm http://www.sunbelt-software.com/ntsysadmin_list_charter.htm Any views or opinions are solely those of the author and do not necessarily represent those of Channel Four Television Corporation unless specifically stated. This email and any files transmitted are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify [EMAIL PROTECTED]