Security Log: Event ID 537 issue

I support a SBS2003 Standard network at my wife's office and it has been
operational since Thanksgiving 2004. With the support of this group I have
managed to learn quite a bit about SBS and we are excited about the product.
All was well until the last couple of days, when the morning status report
started speaking of numerous Security Violations. I went into the office
and prowled through the Event Logs, here is a summary of the error which is
repeated over and over the past few days:

Source: Security
Category: Logon/Logoff
Type: Failure Aud
Event ID: 537
Reason: An error occurred during logon
Logon Type: 3
Logon Process: Kerberos
Status Code: 0x000006D

Background: When I checked the IP Address listed in the Event Properties it
comes back to a Tablet PC that was just fired up last Thursday after not
being used for five months. These Tablets connect wirelessly and were
successful members of the Domain for months. Now that a software issue has
been addressed the doctors wish to bring them back online. I fired them up
and let them run for a couple of days, actually to test their updating with
Trend Micro CSM which is another issue I am working on! Ever since they (2
of them) were turned on these errors starting appearing in the Event Logs
under the Security section. Just over the weekend this error appeared more
than fifty (50) times for these 2 Tablets.

Can anybody point me in the right direction? Many thanks for this and all
of the help offered by this wonderful group of folks. :>)

Mike Stem
Cinti, OH
SBS2003 Newbie



.

Relevant Pages

  • RE: Account Lockout (Event ID: 539) Alert message
    ... >Subject: Account Lockout Alert message ... >SBS box with a subject just like the subject of this post. ... > For more information about this event, see the event logs on the server ... >Logon Failure: ...
    (microsoft.public.windows.server.sbs)
  • Active Directory DC Hangs when lmcompatibility is set 4
    ... DIRECTORY SERVICE EVENT LOGS: ... see Help and Support Center at ... The DNS server was unable to open the Active Directory. ... Nothing in the security event logs to indicate any authentication issues. ...
    (microsoft.public.windows.server.active_directory)
  • Security Audits.
    ... I sent the following letter to our Anti-Virus support team; ... Windows security event logs becoming clogged and full of Failure audits of ... Event Source: Security ... the constantly filling event logs make for more frequent than ...
    (microsoft.public.windowsmedia)
  • Re: Standard / Default SBS 2003 R2 Service Settings
    ... Here are the last four unscheduled restart event logs. ... see Help and Support Center at ... Symantec Groupware Antivirus, Quarantine Agent, Symantec LiveUpdate and ... Symantec Reporting Agent. ...
    (microsoft.public.windows.server.sbs)
  • Re: Last gasp......
    ... I deleted all event logs and restarted my PC. ... see Help and Support Center at ... You can access Event Viewer by selecting Start, Control Panel, ... Properties window and must be Xed out of or ended with Task Manager. ...
    (microsoft.public.windowsxp.general)