Account lockout with no record of the failures in security, why?
Posted on 2010-08-25
We have a stand alone pc in a remote site that does not authenticate to the domain when users normally use it. But we have one user who's login is the same as his domain login he uses for terminal services connection to a server for data entry.
The account locks out apparently as soon as he logs into his local pc, as I had him call before trying the terminal service login and sure enough his account shows locked.
But there is no record in Active Directory if any failures so I am stumped as to why, my gut says that somehow because his password is most likely different on the local login that somehow AD is picking this up as a failure or a password change timeout since my guess is his local login was at one time his domain login also.
Anyone want to venture a guess?