Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In a windows 2003/2008 mixed domain, is it possible to find out where on the network a particular account is logged into?

The account keeps getting locked out, and we think the account may be logged in somewhere, but we don't know where.

share|improve this question
Couldn't you just look at the client information in the lockout events? Coming up with "where are all the places this account is in use" is incredibly difficult, but "what system is locking this account" is very easy. – Shane Madden Oct 21 '11 at 19:30
FYI: I figured what was locking my account. We use a tool called mRemote to manage multiple RDP sessions. When you create a profile for a machine, if you don't put in a password, it will try to pass in a null password when attempting to log in. Try to log into 3 servers and bang, my account was locked. Thanks for your help – Dave Nov 16 '11 at 17:54
up vote 8 down vote accepted

Sounds like you want the Account Lockout tools

Allows you to run a query against a domain controller's security logs to search for particular users - for example, to show where the failure audits are coming from.

share|improve this answer
I'm going to try this as soon as I get into work on Monday! Thanks – Dave Oct 22 '11 at 1:28
Sorry for the delay. The instructions state that you need to install ALockout.dll on the computer that generated the lockout error message. How do I determine that? – Dave Oct 26 '11 at 18:39
Err I don't think you do. I've always just run it from my PC, against a domain controller. Just run EventCombMT and put the username as the search string – George Hewitt Oct 29 '11 at 7:46
I found that logs on the DC and it says the source is my own computer. I added the ALockout.dl for xp, but the logs are 0 kb. I think that it's because I'm using xp 64 bit. – Dave Oct 30 '11 at 12:33
I'm giving you the answer because these are obviously the right tools. Thanks, I appreciate the help. – Dave Oct 30 '11 at 12:34

You can use UPing tool. It collects information about users logons to database (just put uping.exe to startup script). And after that you can query the database jussk like ping: uping

share|improve this answer

If you wanted, you can store the current logged in user and write it to AD. This would allow you to easily search for it in the future. Here is a short guide:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.