Re: Security event id 537
- From: SteveC <scashman@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 5 Sep 2008 06:44:01 -0700 (PDT)
On Sep 5, 5:26 am, IanB <I...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have this exact same issue, and it could be since upgrading Trend CSM to
the WF version.
Could there be a link?
IanB
"SteveC" wrote:
On Sep 4, 12:09 pm, "Cliff Galiher" <cgali...@xxxxxxxxx> wrote:
Is everything else *really* blank? Or did you 'edit' it for security?
Specifically domain, username, workstation, and source IP?
If you did edit the output, do all of the fields contain the same values
every time?
-Cliff
<scash...@xxxxxxxxxxxxxxxxxx> wrote in message
news:b7e8ef1b-5647-41f3-8fd2-dfe8fee236ac@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We're running SBS 2003 R2. We have about 7,000 of these failure audits
in our Security Log. Any ideas?
Logon Failure:
Reason: An error occurred during logon
User Name:
Domain:
Logon Type: 3
Logon Process: Èù¿ Wd
Authentication Package: NTLM
Workstation Name:
Status code: 0x80090308
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -
Each one of them is the same, but the Logon Process changes.
Thanks for any help you can offer.- Hide quoted text -
- Show quoted text -
Cliff,
Yes, everything else is blank. That is a direct copy of the event log.
Everything stays the same for each event (7000 right now), but the
"Logon Process" changes to something similar, but unreadable (at least
to me).
Steve- Hide quoted text -
- Show quoted text -
IanB,
We have Trend Micro Worry Free Security running. We didn't upgrade,
but installed WF from scratch. I searched Trend Micro's site and
didn't see anything. I saw a thread about making sure that Proxy
Server was selected and user names/passwords were entered in WF and I
did that. I haven't seen a change, but I don't know if it would
require a reboot. I can't restart the server until this weekend.
Steve
.
- Follow-Ups:
- Re: Security event id 537
- From: Miles Li [MSFT]
- Re: Security event id 537
- References:
- Security event id 537
- From: scashman
- Re: Security event id 537
- From: Cliff Galiher
- Re: Security event id 537
- From: SteveC
- Re: Security event id 537
- From: IanB
- Security event id 537
- Prev by Date: SBS 2003 Exchange Setup
- Next by Date: Re: WSUS from R2 Technologies wont re-install
- Previous by thread: Re: Security event id 537
- Next by thread: Re: Security event id 537
- Index(es):
Relevant Pages
|
Loading