Description
In our new ASP.NET Wep Application, we are using Windows Authentication to validate user credential with Active Directory. This mechanism was worked well for the past few days. But today, we have hosted our ASP .NET Web Application in IIS Web Server with host header. Now, after we have added host header to access Web Application, Windows Credential dialog seems not authenticate user’s credential properly. but it was worked well before without host header
Now I am getting an error message even though I provide the valid credentials
After I have analyzed some time, noticed the logon failure event ‘4625 An account failed to log on‘ in Security event log
Event ID 4625 Source
Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 27/12/2013 2:07:33 PM Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: myServer.myDomain.local Description: 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: Administrator Account Domain: myDomain 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: myServer Source Network Address: 292.168.1.139 Source Port: 44721 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.
Solution:Event id 4625 An account failed to log on
After I have some time, found this issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
Check this Microsoft’s KB article for further analyze: http://support.microsoft.com/kb/896861