AD Lockout when user's computers resume from sleep

AD environment with Kerberos.  We are noticing an increased level of AD lockouts.  Users are stating this occurs after they wake their computers from sleep or move from one area of the campus to another (via WiFi).  AD account is locked and logs indicate KERBEROS failure.  

Any input on which path to go down?  Once the computer is back up and the AD account is unlocked the issues will not present itself again until the laptop is woken up again after some time (usually the next day).
Sean WilliamsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
What is your password policy set to for the amount of failed login attempts?

Do you have Directory Service Logging Enabled?

Is the machine actually locking out from the machine that was asleep?

Enabled Directory Service Auditing
http://www.wsit.ca/how-tos/active-directory/configure-active-directory-auditing/

Also checkout Active Directory Auditing by Lepide which will help you pin-point where it is locking out exactly.

http://www.lepide.com/lepideauditor/active-directory.html

Will.
Sean WilliamsAuthor Commented:
-We allow 5 failed attempts within a short time period.

-Service logging is enabled- not source IP or hostname is showing in the events.

-Machine is not locking while asleep- but when it resumes within a few minutes they lock out
Will SzymkowskiSenior Solution ArchitectCommented:
If you have all of the correct logging enabled it should show where the account is locking out on IP and or Host name. If it does not then not all of the correct logging has been configured.

Will.
Sean WilliamsAuthor Commented:
Issue was found to be from routing, thus explaining why the Kerberos client addresses were not correct in the logs.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sean WilliamsAuthor Commented:
I found the solution myself
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.