We have a user who is very often reporting that she cannot check her email. Each time she calls it is because her account is locked out in AD. I went to her desk and used her password to successfully unlock windows, and establish credentials with our exchange server. Though while using her PC, I remotely checked AD and lo and behold she became locked again.
Clearly, there is something attempting to authenticate with a bad password using her user name.
I've done as much research as I can and I stumbled upon Account Lockout Tools:
http://www.microsoft.com/downloads/...9C-91F3-4E63-8629-B999ADDE0B9E&displaylang=en
Quick comment on this: Awesome package.
I have been playing with EventComb and AccountStatus and they are very, very useful.
After refreshing account status a few times I notice that the bad password attempt increases over a matter of minutes until it was locked out.
Some of the steps I have already taken:
Reinstalled Outlook.
Removed any thing saved in "manage passwords" under user account control.
Checked mapped drives to ensure access across all.
I then used EventComb to pull the security log for all events pertaining to bad password attempts and lockouts. It pulled events from our domain controller which the IP pointed to our exchange server.
So it clearly has something to do with email, I just don't get why this is happening. Are there any other steps I can perform?
Clearly, there is something attempting to authenticate with a bad password using her user name.
I've done as much research as I can and I stumbled upon Account Lockout Tools:
http://www.microsoft.com/downloads/...9C-91F3-4E63-8629-B999ADDE0B9E&displaylang=en
Quick comment on this: Awesome package.
I have been playing with EventComb and AccountStatus and they are very, very useful.
After refreshing account status a few times I notice that the bad password attempt increases over a matter of minutes until it was locked out.
Some of the steps I have already taken:
Reinstalled Outlook.
Removed any thing saved in "manage passwords" under user account control.
Checked mapped drives to ensure access across all.
I then used EventComb to pull the security log for all events pertaining to bad password attempts and lockouts. It pulled events from our domain controller which the IP pointed to our exchange server.
So it clearly has something to do with email, I just don't get why this is happening. Are there any other steps I can perform?