• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2044
  • Last Modified:

Failed login attempts - how to determine source

Have over 200 failed login attempts daily on an AD account and not sure where they are coming from.  Whats the easiest way to see what the source is?

1 Solution
Joseph MoodyBlogger and wearer of all hats.Commented:
check on the event viewer for

Event Type: Audit Failure
Event Source: Security
Event Category: Account Logon
Event ID: 680
Here's some pretty helpful tools for tracking what machine is causing the lockout: http://technet.microsoft.com/en-us/library/cc738772(v=ws.10).aspx
7 new features that'll make your work life better

It’s our mission to create a product that solves the huge challenges you face at work every day. In case you missed it, here are 7 delightful things we've added recently to monday to make it even more awesome.

I had this same exact issue. The one way I was able to find the problem workstation causing one of my users account to get locked out was to use Network Monitor on my of my DC's. Unlock the users account and monitor the the users account status. As soon as the users account locked I stopped network monitor and filtered the results bases on authentication traffic.

good luck,,,
Try the 30 day trial from this place .. easiest I have seen around .
Prashant GirennavarCommented:
If you are talking about logon attempts made on the server , then you can easliy trace this out in security event logs.

Just to security event log which is got falied, Double click on it. It will show who has attempted to login.

If a user is trying to login to domain using workstation and not able to login , and security events are getting generated on a domain controller , then you can use Lockout.exe tool from microsoft which will tell on which DC the account got locked. GO to the DC, check the security event logs.

Security Event Logs will tell From which workstation accounts are logging in and producing problem.

Hope this Helps.


Leon FesterSenior Solutions ArchitectCommented:
You can enable debug logging on the Netlogon service. This should help you locate the source of the logon requests. You'll need to enable logging on all your DC's where these users can be authenticated.

In the event veiwer; When doing auditing you see all the events, however when viewing the logs in event viewer, simply right-click the log, click properties, select the filter tab and then only select the required filter for your view.
rhwimmersAuthor Commented:
great, thanks!
rhwimmersAuthor Commented:
Update -
The account getting locked out - but having hundreds of these every day

event id 529
login type 8
call process 1640

IP seems to be from (an exact one would be  The source port is different every time.
The tools mentioned thus far don't really help since the user is not being locked out.
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

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

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