Failed Logon Events [Event ID 4625; Logon Type 8; Procss Name: w3wp; Process: Advapi]


Joined
Nov 21, 2010
Messages
3
Reaction score
0
We are getting dozens of these Alerts generated at our Exchange Server. What is causing it and more importantly, what procedural steps do we take to prevent the alerts from generating.

------------------------------------------------------------------------------------------------------------------------------
Details:

Windows Event Alert was recorded

Time: Date Time
Windows Event Time: Date Time
Windows Event Log: Security
Windows Event Source: Microsoft-Windows-Security-Auditing
Windows Event ID: 4625
Windows Event Severity: Failure Audit
Windows Event Message: An account failed to log on.

Subject:
Security ID: S-1-5-18
Account Name: [[EXCHANGE_SERVER$]]
Account Domain: [[DOMAIN]]
Logon ID: 0x3e7

Logon Type: 8

Account For Which Logon Failed:
Security ID: S-1-0-0
Account Name: [[Username]]
Account Domain: [[DOMAIN]]

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a

Process Information:
Caller Process ID: 0xd5c
Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe

Network Information:
Workstation Name: [[EXCHANGE_SERVER]]
Source Network Address: [[IP_ADDRESS]]
Source Port: 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.
------------------------------------------------------------------------------------------------------------------------------

Any help would be much appreciated.
 

Silverhazesurfer

Master of Logic
Joined
Oct 3, 2008
Messages
1,068
Reaction score
42
Account For Which Logon Failed:
Security ID: S-1-0-0
Account Name: [[Username]]
Account Domain: [[DOMAIN]]

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a

Process Information:
Caller Process ID: 0xd5c
Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe

Network Information:
Workstation Name: [[EXCHANGE_SERVER]]
Source Network Address: [[IP_ADDRESS]]
Source Port: Port
I would start there. Where is the source of the attempt? Inside or outside? If inside, it should be easy to determine who the source is (assuming that this is an internal server). If outside, you may have someone trying to hack an account.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top