Re: Windows 2000 users accounts get locked out

From: Steven L Umbach (sumbach_at_N0spam.ameritech.net)
Date: 05/18/04


Date: Tue, 18 May 2004 12:35:52 -0500

Hi again Merrick.

If you have not done such, set your account lockout threshhold for number of
bad attempts to at least ten. You should be seeing failed logon attempts
such as Event ID 529 on some computers in the domain. These failed logons
could be on any computer in the domain - not just domain controllers. Be
sure you have auditing of "logon events" for failure which is different than
account logon events enabled in Domain Security Policy and Domain Controller
Security Policy. You may also need to configure it at the OU level if you
are using Organizational Units with their own Group Policies that have
auditing disabled. You can check the Local Security Policy of any domain
computer and look at the "effective" settings for auditing to see if it is
enabled. Those failed logon events will give a lot of helpful info on why
the logons are failing and from what computers the logon attempts are coming
from.

In addition I would run some diagnostics on the domain controller and then a
couple domain computers. First run netdiag on the domain controller looking
for any failed tests/errors/warnings particularly relating to dns, domain
membership, and dclist. Then run dcdiag on the domain controller looking for
failed tests again. After that do the same with netdiag on one of the domain
members. On the domain controller and domain member run " netdiag
/test:ipsec " which will show if an ipsec policy is assigned that can cause
problems in a domain. You can post results here in a reply if any problems
are found. Those tools are found on the install cdrom in the support/tools
folder where you will need to run the setup there. -- Steve

"Merrick" <anonymous@discussions.microsoft.com> wrote in message
news:e7fb01c43cb0$4343bd40$a001280a@phx.gbl...
> Hi guys! thanks for the help. I have scan my firewall as
> suggested by Steven and all my ports are secured. I have
> also increase my password threashold to 10 minutes. I have
> patched all my software for my servers and users. All my
> users are using Windows 2000 only. I have also rename my
> administrator for my server. I have downloaded EventCombMT
> from MS and managed to search all my events log. I have a
> long list of event ID: 644. Yet when i go through the list
> I still don't understand why my users are getting locked
> out! This happened suddenly and I have never changed any
> thing to my servers. My accounts is still getting locked
> out and yet I still dont know why! Please help. Many
> thanks in advance!
> Merrick



Relevant Pages

  • Re: User Logon ID
    ... Logging onto the domain or just the domain controller?? ... controller enable auditing of logon events in Domain Controller Security ...
    (microsoft.public.win2000.security)
  • Re: Recording logon details
    ... You could enable auditing for logon events on the domain controller which ... > following data at user logon and logoff: ... Is third party software required? ...
    (microsoft.public.win2000.security)
  • Re: account logon events
    ... Account logon: A domain controller received a request to validate a user ... > Account Logon auditing events relate solely to local account login, ... > need to audit domain logon events to audit logons through AD ...
    (microsoft.public.cert.exam.mcsa)
  • Re: Cannot logon to "(local machine)"
    ... So you are not able to logon at all as that user?? ... enable auditing of logon events on the computer in question and account ... logon events in Domain Controller Security Policy to see if any logon ... Also check that the user has permissions to their local profile ...
    (microsoft.public.win2000.group_policy)
  • Re: Auditing User logon/logoff events.
    ... u say in the document like i enabled "Account logon events" only in domain ... Then i am getting 672,673 event ids in my domain controllers event viewer. ... can see this log in domain controller security log. ...
    (microsoft.public.win2000.security)