Windows account locking itself

In particular my account.

After testing a fingerprint scanner my account is locking every time.
I've managed to track it down to my desktop that's causing it, but cannot see what it is.

I'm getting the following event log on the domain controller:

Kerberos pre-authentication failed.

Account Information:

   Security ID:  ACME\administrator
   Account Name:  Administrator

Service Information:

   Service Name:  krbtgt/acme

Network Information:

   Client Address:  ::ffff:10.42.42.224
   Client Port:  50950

Additional Information:

   Ticket Options:  0x40810010
   Failure Code:  0x18
   Pre-Authentication Type: 2

Certificate Information:

   Certificate Issuer Name:  
   Certificate Serial Number:  
   Certificate Thumbprint:

Certificate information is only provided if a certificate was used for pre-authentication.

Pre-authentication types, ticket options and failure codes are defined in RFC 4120.

If the ticket was malformed or damaged during transit and could not be decrypted, then many fields in this event might not be present.

Keep me up-to-date on the Windows Security Log.
Email*:  
  Submit

ideas?

Thanks
LVL 1
CHI-LTDAsked:
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.

Muhammad BurhanManager I.T.Commented:
Sometimes User/Machine it self force user's credentials to do something like Task Scheduling or access SMB (to or from)etc. When AD users change its password it doesn't impact on the services which uses previous credentials.
Event Forwarding with Advance Auditing enabled is the easiest way to troubleshoot these kind of hidden issues. Once all of the logs gathers in DC or somewhere else. Comparing machine's logs with DC's, resolves many of them.

check that scanner's service properties in services.msc may be it uses credentials of administrators.

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
CHI-LTDAuthor Commented:
was a number of services and applications,
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
Windows Server 2008

From novice to tech pro — start learning today.