I've been seeing this logon event failure in the Security log of our Echange 2010 for the past week. I'm trying to figure out what account is attempting to log on and from where. Any help is greatly appreciated. Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 12/19/2010 10:49:57 PM Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: sabexchange2.sab.local Description: An account failed to log on. Subject: Security ID: SYSTEM Account Name: SABEXCHANGE2$ Account Domain: SAB Logon ID: 0x3e7 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: Account Domain: Failure Information: Failure Reason: The specified user account has expired. Status: 0xc0000193 Sub Status: 0xc0000193 Process Information: Caller Process ID: 0x15ec Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe Network Information: Workstation Name: SABEXCHANGE2 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. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>4625</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2010-12-20T03:49:57.105760700Z" /> <EventRecordID>12387629</EventRecordID> <Correlation /> <Execution ProcessID="544" ThreadID="600" /> <Channel>Security</Channel> <Computer>sabexchange2.sab.local</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-5-18</Data> <Data Name="SubjectUserName">SABEXCHANGE2$</Data> <Data Name="SubjectDomainName">SAB</Data> <Data Name="SubjectLogonId">0x3e7</Data> <Data Name="TargetUserSid">S-1-0-0</Data> <Data Name="TargetUserName"> </Data> <Data Name="TargetDomainName"> </Data> <Data Name="Status">0xc0000193</Data> <Data Name="FailureReason">%%2305</Data> <Data Name="SubStatus">0xc0000193</Data> <Data Name="LogonType">3</Data> <Data Name="LogonProcessName">Authz </Data> <Data Name="AuthenticationPackageName">Kerberos</Data> <Data Name="WorkstationName">SABEXCHANGE2</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x15ec</Data> <Data Name="ProcessName">C:\Windows\System32\inetsrv\w3wp.exe</Data> <Data Name="IpAddress">-</Data> <Data Name="IpPort">-</Data> </EventData> </Event>

w3wp.exe is IIS worker process (app pool). so this is happening because of something is being processed in IIS. consult IIS log files to find after what request this event log happens. ondrej.