We help IT Professionals succeed at work.

How do you check login attempts/bad password windows 2003 domain user?

1,807 Views
Last Modified: 2014-08-27
Is there any easy way to check user login times, bad password attempts for a normal user on a windows 2003 domain?
Comment
Watch Question

Commented:
Hey,

In the event viewer of the DC's all logon attampts to the domains are logged.. If you have a large amount of users it will be huge though.

Author

Commented:
Thanks. Any easier way though? Got lots of DCs.

Commented:
Without extra software or money? Not really. You can use "forwarded events" to get them all to one place but without extra software i don't think you can.
systechSenior Technical Lead
CERTIFIED EXPERT

Commented:
Hi,

You can configure this security setting by opening the appropriate policy (default domain policy) and expanding the console tree as such: Computer Configuration\Windows Settings\Security Settings\Local Policies\Audit Policy\

Once you enabled the policies, you can go to Event Viewer and check the Security logs for the following events;
Event ID 24
A user account was created.
627
A user password was changed.
628
A user password was set.
630
A user account was deleted.
631
A global group was created.
632
A member was added to a global group.
633
A member was removed from a global group.
634
A global group was deleted.
635
A new local group was created.
636
A member was added to a local group.
649
A local security group with security disabled was changed.
650
A member was added to a security-disabled local security group.
651
A member was removed from a security-disabled local security group.
652
A security-disabled local group was deleted.

There are lot more apart from this. This is how companies perform audit. I would suggest to go for this instead of purchasing 3rd party tools.

Good luck
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Excellent. Just the job.

Author

Commented:
Yes got that but it just gives times for user per DC.
CERTIFIED EXPERT

Commented:
Yeah, once you get the dc name and time stamp, check audit failure logs in security event logs of that dc for the exact time given in that tool. Once you find that event, it will show you client ip which is the source of bad password. If you need to analyze further, check event logs of client ip for the exact same time where you will get pid of bad pass generating process which in turn can be identified through task manager.
This is complicated but it depends on you how far you want to dig just the source ip or exact root cause.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.