Microsoft-Windows-Security-Auditing 4625 Expand / Collapse
Author
Message
Posted 12/26/2016 8:55:38 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 12/26/2016 8:39:19 AM
Posts: 2, Visits: 0
An account failed to log on.
Subject: Security ID: S-1-0-0
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: S-1-0-0
Account Name: xyzuser
Account Domain: srkt
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: Compname
Source Network Address: ipv4
Source Port: Randomhignumberport
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.

A user name separated from our company and deleted from AD. He's trying to reach the File Server. It gets this error and it is trying again. There are more than 10000 logs in a weekly period. Every time it's tried from random ports.I found nothing for the solution on the internet. How can i fix this
Post #7296
Posted 12/26/2016 4:06:03 PM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 11/14/2013 3:17:47 PM
Posts: 237, Visits: 0
I have seen similar issues occur when virtual workstations were still running after the user was deleted or if there is a script still running somewhere using those creds. I would start with the source workstation and try to determine why that username is being used to to login from the source workstation to this particular host.
Post #7302
Posted 12/27/2016 3:58:46 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 12/26/2016 8:39:19 AM
Posts: 2, Visits: 0
Thanks for reply Derek. what is your suggestion? where/how should i look? i cant reach workstation anytime, somebody use machine. ı cant research for long time
Post #7303
Posted 1/23/2017 6:42:50 PM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 11/14/2013 3:17:47 PM
Posts: 237, Visits: 0
You will have to look into the logs on that workstation. Look into remotely viewing those logs if you can't get to the workstation.
Post #7309
Posted 7/14/2017 3:59:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 10/10/2017 10:00:15 PM
Posts: 2, Visits: 5
I am encountering the same issue but with the user account enabled and in use. What puzzles me is that the user doesn't get locked out due to the logon failure (our GPO policy is configured to lock out account after 5 failed attempt). Any ideas what's happening?
Post #7386
Posted 8/14/2017 4:49:30 PM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 11/14/2013 3:17:47 PM
Posts: 237, Visits: 0
What is the error code that you are receiving?
Post #7398
Posted 9/10/2017 10:28:34 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 10/10/2017 10:00:15 PM
Posts: 2, Visits: 5
Below is the log that I received. This has been bugging me for awhile now. I tried to simulate a logon failure with a wrong password and the lockout works just fine.

LogName=Security
SourceName=Microsoft Windows security auditing.
EventCode=4625
EventType=0
Type=Information
ComputerName=XXXXX
TaskCategory=Logon
OpCode=Info
RecordNumber=41303656
Keywords=Audit Failure
Message=An account failed to log on.

Subject:
Security ID: NT AUTHORITY\SYSTEM
Account Name: XXXXX$
Account Domain: XXXXX
Logon ID: 0x3E7

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: XXXXX
Account Domain: XXXXX

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC000006A

Process Information:
Caller Process ID: 0x264
Caller Process Name: C:\Windows\System32\lsass.exe

Network Information:
Workstation Name: XXXXX
Source Network Address: XXXXX
Source Port: 60232

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
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.
Post #7408
Posted 9/24/2017 1:57:52 PM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 11/14/2013 3:17:47 PM
Posts: 237, Visits: 0
Do you observe authentication success events in between failures which would prevent the account from getting locked out?
Post #7413
« Prev Topic | Next Topic »


Permissions Expand / Collapse

All times are GMT -5:00, Time now is 8:29am