timothy.m.curry

Windows Audit Log failures when using url_response probe with authentication

Discussion created by timothy.m.curry on Mar 1, 2013

has anyone seen this and have a solution for the windows 2008r2 audit log entries shown below when using url_response probe (multiple versions) that has authentication set.

 event ID 4776:

The computer attempted to validate the credentials for an account.

Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0

Logon Account: <username>

Source Workstation: <server name with url_responseprobe>

Error Code: 0xc0000064

 

and

event ID 4626:

An account failed to log on.

Subject:

Security ID: SYSTEM

Account Name: <server name with url_response probe$>

Account Domain: <domain>

Logon ID: 0x3e7

Logon Type: 2

Account For Which Logon Failed:

Security ID: NULL SID

Account Name: <account name>

Account Domain: <server name with url_response Probe>

Failure Information:

Failure Reason: Unknown user name or bad password.

Status: 0xc000006d

Sub Status: 0xc0000064

Process Information:

Caller Process ID: 0xf70

Caller Process Name: Program Files (x86)\Nimsoft\probes\application\url_response\url_response.exe

Network Information:

Workstation Name:

Source Network Address: -

Source Port: -

Detailed Authentication Information:

Logon Process: Advapi

Authentication Package: Negotiate

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.

 

I have been trying to track this down for a while with no results.

Thanks in advanced.

Outcomes