SQL Server - Audit failures

JamesonJendreas used Ask the Experts™
I've been monitoring the security log on my Server 2008\SQL Enterprise 2008 server.  I tend to get eh following error every few minutes or so - NOTE: Servername$ is the local DB server name plus a $

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          8/8/2011 12:15:01 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      servername.foxshox.com
An account failed to log on.

      Security ID:            SYSTEM
      Account Name:            SERVERNAME$
      Account Domain:            DOMAIN
      Logon ID:            0x3e7

Logon Type:                  3

Account For Which Logon Failed:
      Security ID:            NULL SID
      Account Name:            
      Account Domain:            

Failure Information:
      Failure Reason:            An Error occured during Logon.
      Status:                  0xc000018b
      Sub Status:            0x0

Process Information:
      Caller Process ID:      0x8b0
      Caller Process Name:      C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe

Network Information:
      Workstation Name:      BLUEWHALE
      Source Network Address:      -
      Source Port:            -

Detailed Authentication Information:
      Logon Process:            Authz  
      Authentication Package:      Kerberos
      Transited Services:      -
      Package Name (NTLM only):      -
      Key Length:            0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
      - Transited services indicate which intermediate services have participated in this logon request.
      - Package name indicates which sub-protocol was used among the NTLM protocols.
      - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Are these from different workstation names or the same events with the same event details every time?  Without knowing much about your environment. Two possibilities come to mind, it could be a brute force attempt if you have the connection ports open to the public and someone is trying to guess the password to it, or you have a workstation that is configured to connect to it but doesn't have the correct credentials, every time it tries to restart the connection it will cause a failure.  

if that doesn't help maybe attach a larger portion of the log files, you can use word to find and replace the ip addresses if they are external.


All the exact same - and seem to be coming from the database server itself - the username is that of the DB server and these errors show on the DB servers event viewer.  Looks like it actually happens every 30 minutes or so.  There is NO source IP, and  if there was I'd expect to see it as the local IP, as this is a local (to the server) logon failure (or so it looks)
Try pulling up Sql Server Manager and looking at what accounts you are running the services as.  Perhaps you don't have the correct password setup there.  Are any of the applications broken, do any of the applications use specific credentials or to you manage it via IIS's app pools?  

First step would be narrowing down where it's stemming from.  As you are checking SQL server logs or windows event viewer logs should help out some.  

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial