IIS issues and Audit Failures
A little weird one here - I'm troubleshooting some IIS issues across a few servers and sites. Essentially, I have a PBX system that uses Windows servers at each location. When I am on the management web page, and I drill down to a specific remote site server (to check it's status) we get a permissions error.
Now, how the PBX system works is fairly specific, and isn't necessarily the issue. So, looking into the http logs on the remote server, i see a bunch I get a large number of AppPool errors:
On the HQ server, I get numerous Audit failures in the audit log:
Note, I have scrubbed the domain and replaced with "domain"
Now, how the PBX system works is fairly specific, and isn't necessarily the issue. So, looking into the http logs on the remote server, i see a bunch I get a large number of AppPool errors:
2012-12-22 00:01:40 172.16.199.124 18381 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-22 01:37:21 172.20.100.167 55699 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-22 03:46:19 172.20.100.139 53334 192.168.81.30 5440 HTTP/1.1 GET /CSIS/CSISISAPI.dll/?request?7efba727-1d8a-4e45-972a-cd714a34c12c;CCSISSvrCONN%3A%3AwaitForEvent%3B3%3B300%3B3%3B120 - 1 Connection_Dropped CSISAppPool
2012-12-22 17:22:58 172.20.100.151 64949 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-23 15:13:53 172.20.100.146 61216 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-24 01:37:24 172.20.100.108 63548 192.168.81.30 5440 HTTP/1.1 GET /CSIS/CSISISAPI.dll/?request?6bd28e8c-9165-4aa1-8ea1-a982acd612d8;CCSISSvrCONN%3A%3AwaitForEvent%3B3%3B300%3B3%3B120 - 1 Connection_Dropped CSISAppPool
2012-12-24 03:34:49 172.20.100.108 63355 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-24 03:40:14 172.20.100.108 63484 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-24 03:44:29 172.20.100.108 63579 192.168.81.30 5440 - - - - - Timer_ConnectionIdle -
2012-12-24 03:44:29 172.20.100.108 63535 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-24 04:31:00 172.20.100.108 64255 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-24 04:32:55 172.20.100.108 64299 192.168.81.30 5440 HTTP/1.1 GET /CSIS/CSISISAPI.dll/?request?30ec233c-bc7d-40c4-8b81-5b2fd7646cec;CCSISSvrCONN%3A%3AwaitForEvent%3B3%3B300%3B3%3B120 - 1 Connection_Dropped CSISAppPool
2012-12-26 12:46:56 172.20.101.244 63348 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-26 14:24:37 172.20.101.253 63705 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-26 17:27:02 172.20.101.253 49425 192.168.81.30 5440 HTTP/1.1 GET /CSIS/CSISISAPI.dll/?request?51e2c3cb-7b8c-4dcb-9120-942d9fb33141;CCSISSvrCONN%3A%3AwaitForEvent%3B3%3B300%3B3%3B120 - 1 Connection_Dropped CSISAppPool
2012-12-27 00:54:03 10.11.3.15 50238 192.168.81.30 5440 HTTP/1.1 GET /CSIS/CSISISAPI.dll/?request?8a290b88-7f52-413a-abf5-87fe905a6cf0;CCSISSvrCONN%3A%3AwaitForEvent%3B3%3B300%3B3%3B120 - 1 Connection_Dropped CSISAppPool
2012-12-27 06:30:45 172.20.100.126 59148 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-27 06:33:55 172.20.100.126 59428 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-27 08:09:45 172.20.100.126 49245 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-27 09:45:46 172.20.100.126 49544 192.168.81.30 5440 - - - - - Timer_MinBytesPerSecond -
2012-12-27 17:34:05 172.20.100.217 49596 192.168.81.30 5440 HTTP/1.1 GET /CSIS/CSISISAPI.dll/?request?355bfa40-78da-4773-84e8-718570e90171;CCSISSvrCONN%3A%3AwaitForEvent%3B3%3B300%3B3%3B120 - 1 Connection_Dropped CSISAppPool
On the HQ server, I get numerous Audit failures in the audit log:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 12/27/2012 9:52:58 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: petntsps.domain.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: FRENTSPS$
Account Domain: domain
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: FRENTSPS
Source Network Address: 192.168.81.30
Source Port: 55676
Detailed Authentication Information:
Logon Process: NtLmSsp
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.
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="2012-12-27T17:52:58.176111900Z" />
<EventRecordID>4888159</EventRecordID>
<Correlation />
<Execution ProcessID="524" ThreadID="202484" />
<Channel>Security</Channel>
<Computer>petntsps.domain.local</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">FRENTSPS$</Data>
<Data Name="TargetDomainName">domain</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc000006a</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">FRENTSPS</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">192.168.81.30</Data>
<Data Name="IpPort">55676</Data>
</EventData>
</Event>
Note, I have scrubbed the domain and replaced with "domain"
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Probably some process that is wired up to use a domain account to log in. Either the account no longer exists, or the password was changed, and the process hasn't been updated to reflect that change.
In other words, "FRENTSPS$" may no longer exist, the password may have changed, or the account may be locked out/disabled.
In other words, "FRENTSPS$" may no longer exist, the password may have changed, or the account may be locked out/disabled.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial