Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2818
  • Last Modified:

Anyone know why I'm getting these security errors?

This client has an SBS 2003 box (not yet SP-1'd I just noticed). I was asked to identify the cause of all of the errors in the security event log. I've never seen these so I'm wondering if anyone can piont me in the right direction for a solution so I don't re-create the discovery wheel from scratch. Thanks for any help.

Here are 3 examples of what I'm seeing. There appear to several different security errors and there are about seceral dozen being logged per day:


Source: Security
Category: Account Logon
Event ID: 673
Description: Failure Code: 0x25


Source: Security
Category: Logon/Logoff
Event ID: 537
Description: An error occured during logon.
Status code: 0xC000006D
Substatus code: 0xC0000133


Source: Security
Category: Logon/Logoff
Event ID: 537
Description: An error occured during logon.
Status code: 0x000006D
Substatus code: 0xC0000133
0
WineGeek
Asked:
WineGeek
  • 3
  • 3
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Event 537 errors usually are caused by incorrectly configured time synchronization.  Because Kerberos security relies on system clocks being synchronized (within 5 minutes of eachother) if the workstations are not getting their time settings from the server, then this can be a problem.  If these just happened last night, then it could be due to the change from daylight savings time.

To configure an authoritative time server, please see: http://support.microsoft.com/kb/816042

FYI, for any EVENT that you are unaware of, you should always check www.eventid.net

Jeff
TechSoEasy

0
 
WineGeekAuthor Commented:
Thanks Jeff. Yeah, eventid.net is and was my first stop and they had nothing on the one I looked up. No, these have been happening for some time I've been told. I'll check out your link now.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, next time, you might want to read a bit slower... (or search a busy page for the actual Status Code)

http://www.eventid.net/display.asp?eventid=537&eventno=194&source=Security&phase=1  has the following info:

The "Connecting to" line gives you fully qualified domain name and IP address of the SBS server that is providing time synchronization. It also provides the port (123) that the Windows Time Service is utilizing. You can find more information by reading M314054".

This problem might also be caused by a “loopback check” security feature that is designed to help prevent reflection attacks on your computer. This feature was introduced in Windows XP SP2 and Windows Server 2003 SP1. Read M896861 for information on resolving this problem.

See MSW2KDB for additional information on this event.

(although I you didn't post the "connecting to" details of your event messages... so I can't be sure if you skipped these due to them not matching exactly).

Jeff
TechSoEasy
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
WineGeekAuthor Commented:
I'm looking through several of these logged events and I'm not seeing anywhere in any of them any reference to "Connecting to." Where should I see this "Connecting to" you referred to?
0
 
WineGeekAuthor Commented:
Also, I read that article about setting a time server, and it was already set in the registry when I checked on that. So I'm guessing this is not a time-related issue.... maybe....
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Sorry, that was my error in reading the EventId.net article too quickly... (although you could have clicked the link above to see the complete article to understand the context of "connecting to").  But essentially it's possible it's the second part of what I clipped from there anyhow... which is the loopback check, and the reference to http://support.microsoft.com/kb/896861

Jeff
TechSoEasy

0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now