Re: Account lockout

From: Derick (anonymous_at_discussions.microsoft.com)
Date: 04/20/04 

Date: Tue, 20 Apr 2004 11:20:46 -0700

Thanks for the info but everything came back oki doki.
What is strange is the I get %1 and that wierd character.

I figured it would be not so clear cut of a problem. I
have not seen this paticular problem before. I have seen
locked out account problems before though.

Thanks

Derick

>-----Original Message-----
>This is usually related to an AD replication collision.
Run the replication
>diagnotsics tools from the Support Tools to see if
anything is amiss.
>
>If everything comes back okie dokey, then try some of
these suggestions:
>
>http://www.eventid.net/display.asp?
eventid=12294&eventno=875&source=SAM&phase=1
>
>--
>******************************
>Laura E. Hunter - MCSE, MCT, MVP
>Replies to newsgroup only
>
>
>"Derick" <anonymous@discussions.microsoft.com> wrote in
message
>news:186f01c426c3$7f93d710$a001280a@phx.gbl...
>>I recieve the following error:
>>
>> Severity: Error
>> Status: New
>> Source: SAM
>> Name: The SAM database was unable to lockout the
account
>> of %1 due to a resource error
>> Description: The SAM database was unable to lockout
the
>> account of &#1402; due to a resource error, such as a hard
disk
>> write failure (the specific error code is in the error
>> data) . Accounts are locked after a certain number of
bad
>> passwords are provided so please consider resetting the
>> password of the account mentioned above.
>>
>> I just can't seem to tackle this one. Any sugestions
are
>> welcome.
>
>
>.
>

Relevant Pages

  • Re: Account lockouts
    ... for reusable passwords and the AAA infrastructures that rely upon them? ... In that context, account lockout policy -- duration, threshold, lockout ... > cracking attacks. ...
    (microsoft.public.security)
  • Re: Account lockout
    ... This is usually related to an AD replication collision. ... diagnotsics tools from the Support Tools to see if anything is amiss. ... The SAM database was unable to lockout the account ...
    (microsoft.public.win2000.security)
  • Re: Deleting Admin Account
    ... administrative level account to change the Type of the Admin account ... created to a limited account (or create yourself a third account - non-admin ... The built-in administrator cannot be changed from the administrative level, ... You should password protect (with different passwords would be best) each ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Blank Passwords, Complex Requeirements and Problems...
    ... The account would then have: 544 = normal account with "Password Not Required" bit = on ... wellKnownObjects: B:32:6227F0AF1FC2410D8E3BB10615BB5B0F:CN=NTDS ... BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx ... As far as i know, the Win2003 AD never had a "free" Default Domain Policy to allow that, the DDP is the Default since the initial build of th AD. Ok, let's say that an Admin disabled temporarily th DDP for a few moments and allowed certain accouns to be created with blank passwords. ...
    (microsoft.public.win2000.active_directory)
  • RE: Single sign on
    ... How to authentificate an user via telephon? ... > Avatier has a product which would allow users to reset their own passwords ... >> for the person whose account is reset. ... >> would only be accessible by the person whose account is reset. ...
    (Security-Basics)