Gabe9527
2410 pts. | Sep 7 2009 12:33PM GMT
Have you made any changes lately to your AD environment?
Do you have any policies that could be at fault?
anything realy to help in finding the solution……
Gabe9527
2410 pts. | Sep 7 2009 12:37PM GMT
This may help you in finding out what is happening….
Account Lockout Tools
<a href="http://technet.microsoft.com/en-us/library/cc738772%28WS.10%29.aspx" title="http://technet.microsoft.com/en-us/library/cc738772%28WS.10%29.aspx" target="_blank">http://technet.microsoft.com/en-us/libra…</a>
This will give you the following informaiton
# DC Name: Displays all domain controllers that are in the domain.
# Site: Displays the sites in which the domain controllers reside.
# UserState: Displays the status of the user and whether that user is locked out of their account.
# Bad Pwd Count: Displays the number of bad logon attempts on each domain controller. This value confirms the .domain controllers that were involved in the account lockout.
# Last Bad Pwd: Displays the time of the last logon attempt that used a bad password.
# Pwd Last Set: Displays the value of the last good password or when the computer was last unlocked.
# Lockout Time: Displays the time when the account was locked out.
# Orig Lock: Displays the domain controller that locked the account (the domain controller that made the originating write to the LockoutTime attribute for that user).
With this you might get hints as to what is doing this.






