Event ID 4625 an account failed to logon (solution)

Today I wanted to logon to the SharedServicesProvider (SSP) of one of our SharePoint servers (Windows Server 2008 R2 with SharePoint 2007 CU June 2009) but was unable to do so. In the eventlog there was an event ID 4625 “An account failed to logon”. The text of the event ID is below.

An account failed to log on.

Subject:
Security ID:        NULL SID
Account Name:        -
Account Domain:        -
Logon ID:        0x0

Logon Type:            3

Account For Which Logon Failed:
Security ID:       NULL SID
Account Name:      <accountname>
Account Domain:    <domainname>

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

Process Information:
Caller Process ID:    0x0
Caller Process Name:  -

Network Information:
Workstation Name:        <Servername>
Source Network Address:  xxx.xxx.xxx.xxx
Source Port:             xxx

Detailed Authentication Information:
Logon Process:       
Authentication Package:  NTLM
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.

The solution for this logon failure can be found in this kb article. There are 2 methods mentioned in the article.

DisableLoopbackCheck was already enabled (because the server is 2008 R2). The second method is the solution for me. By creating the registry key BackConnectionHostNames and putting all the hostnames in it, including the SSP hostname, I was able to logon to my SSP.

Thanks to this article I was directed to the kb article.

Tags: error