Re: Account Lockout...

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 11/14/04 

Date: Sun, 14 Nov 2004 12:31:05 -0500

Ketta wrote:
> I have domain, local, domain controller policies all set to lockout an
> account after 3 invalid logon attempts. None of our users are
> logging into the domain, only through Outlook for Exchange. When
> they enter the wrong password more than 3 times the account is not
> locked, does anyone know why this is? Every workstation is using a
> local account and operates completely independant of the domain.
>
> Thank you,
> Mike Stiers

Well, if they're using local accounts, this makes perfect sense. Why are
they using local accounts anyway? This is not a good practice - what's the
client OS? If they're using XP Home, upgrade them to XP Pro. XP Home doesn't
belong on a domain.

For the domain accounts, don't set lockout. It's more trouble than it's
worth - just make sure you force regular pw changes & enable complex
passwords.

Relevant Pages

  • Re: Username Vulnerability???
    ... Open Server Manager> highlight the PDC ... Password Policy and Account Lockout Policy are both ...
    (microsoft.public.windows.server.general)
  • Re: OU group policy and how to use ldapsearch to find GPO settings
    ... The account is a domain account. ... Account Policies effective for all domain accounts. ... Your ldap query is seeing the settings that are in use for the domain. ... If I configure the account lockout policy in the default domain policy, ...
    (microsoft.public.windows.group_policy)
  • Re: Replication of password resets/unlocks
    ... Assuming that the reg key AvoidPDCOnWan isn't set passwords will be sent immediately out of band to the PDC when changed on a local machine. ... I haven't dug into the specifics but I believe that occasionally it will check with the PDC to see if the account has been unlocked but not for every auth attempt, this is so a PDC will not be overwhelmed by attempts to auth a locked account. ... The idea behind auto lockout is to prevent brute force systems from sending thousands of passwords an hour to crack a password, if that is the case, then setting the lockout policy to 25 bad attempts and locking the account out for say 5 minutes is just as good from a security perspective; it will seriously impact the ability for a brute force attack. ... From the usability standpoint, it will only lockout users who have really screwed up with their password and give them just enough time to realize they really screwed up but take less time than a call to the helpdesk for an unlock and replication of the unlock meaning that if they call the helpdesk for a rest, the only mechanism that comes into play is the one in the first paragraph above which works fine. ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 Server Client/Delegation and Data Issues
    ... "reveal" the read and write lockout time permissions. ... I have an account that I ... default - no mention of domain users. ...
    (microsoft.public.windows.server.active_directory)
  • Re: lockaccount flag in userAccountControl does not change
    ... Neither has explicit support for dealing with lockout though. ... The IADsUser interface in ADSI attempts to support it, ... checks to see if lockoutTime has a value or not and assumes the account is ... For more information on unlock, ...
    (microsoft.public.windows.server.active_directory)
Loading