Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 266
  • Last Modified:

Account lockout with no record of the failures in security, why?

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?
0
dpcsit
Asked:
dpcsit
  • 2
1 Solution
 
lost_enigmaCommented:
this may be caused by the viruses (we have such situation)
Use this utility to monitor the reason why it is lockout
http://www.microsoft.com/downloads/details.aspx?FamilyId=7AF2E69C-91F3-4E63-8629-B999ADDE0B9E&displaylang=en
If you have additional questions let me know.
0
 
SteveCommented:
its an interesting one. it does sound like something on the PC is trying to connect to the domain and causing a problem.

Does the PC have any shared printers from the server or any mapped drives etc?


use ALockout.dll from the tools shown above on the client PC (not the server) and see where the account access originates from.
0
 
dpcsitAuthor Commented:
It is an issue with the local account, I reset the password of the domain account to match the local and the lockouts stopped.

Now the question is why AD would pick up a local account credential and use it, granted it is the same name but I would have thought the local account and the domain account would be totally different.
0
 
SteveCommented:
this is a throwback to older systems. windows 98 an earlier OSs didn't support domains so some loopholes had to be left for them to connect. if you set a local account to match user/password of a domain account you can gain access to some domain resources, unless the domain functional level has been upgraded to phase out the support or the domain security policy prevents it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now