Re: Event 12294 SAM error
- From: Speaker Ender <SpeakerEnder@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 7 Aug 2006 12:10:02 -0700
Thanks for the suggestion, I'll give Process Explorer a try.
The reason I'm also rather sure it isn't a virus is the virus they post on
that causes this behavior only effect Windows 2k (from all the articles
linked/searched).
Also haven't exactly tracked down all the users that generate the event. I
managed to duplicate the event when I try signing on with no password/wrong
password, hence leading me to think thats the problem (as the Webserver lets
internal/external users into our Intranet site).
"Adrian Grigorof" wrote:
Did the users actually try to login with the wrong password and generated.
this event? You also mentioned that the system was checked with Symantec
Antivirus, using the latest virus patterns. Please note that in itself, that
doesn't mean there is no virus - maybe the av did not detected. From my
experience, even with the latest updates, sometimes an antivirus may fail to
detect a virus. Try to run Process Explorer (from www.sysinternals.com) and
see if there is any strange process running on that machine.
--
Adrian Grigorof
www.eventid.net
"Speaker Ender" <SpeakerEnder@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B340BD1C-862D-4C23-97AD-9D941B6A8FD5@xxxxxxxxxxxxxxxx
Yeah the error code was not much help.
It is different usernames, and it took a while to track down that it was
coming from the webserver and not a specific workstation.
There is nothing else that appears related in any of the logs. No errors
in
the File Replication Service log, nothing in Directory Services or any of
the
other logs.
Looking in the log and analyzing it with NLParse and there are no accounts
with current password is not correct.
I checked the link, I've seen it before, and finally hunted down his part
III, the problem seems to be different though, as none of the services on
the
webserver use regular user accounts. I'm almost thinking it is something
with IIS and how its authenticating the users (i.e. when it fails the
third
time it should tell the DCs to lock the account, but doesn't).
"Adrian Grigorof" wrote:
Well, the error code means "DS (Directory Services) is busy" - not much
help
there. How about the user name - is it the same all the time? Is the
webserver a domain controller? Any other relevant events in the log?
Also,
take a look at this page:
http://www.eksternkompetanse.no/blog/PermaLink,guid,576846a0-ac14-47d4-8057-c117a9e2ec1c.aspx
--
Adrian Grigorof
www.eventid.net
- Follow-Ups:
- Re: Event 12294 SAM error
- From: Adrian Grigorof
- Re: Event 12294 SAM error
- References:
- Re: Event 12294 SAM error
- From: Adrian Grigorof
- Re: Event 12294 SAM error
- From: Adrian Grigorof
- Re: Event 12294 SAM error
- From: Adrian Grigorof
- Re: Event 12294 SAM error
- Prev by Date: removing problematic Win2k DC from 2003 forest
- Next by Date: Re: Group Policys
- Previous by thread: Re: Event 12294 SAM error
- Next by thread: Re: Event 12294 SAM error
- Index(es):
Relevant Pages
|