S
Sandra Bujang
Guest
Hello and Good Day,
Currently, Our server keep getting Failed Login Event ID 4625 as detailed below:
—————————————————————————————————————————————
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: HQSVR-KASP01$
Account Domain: GSCHQMY
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: HQSVR-KASP01
Source Network Address: 192.168.1.111
Source Port: 50346
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.
————————-–—————————————————————————————————————————————————————————————————
1. It keep been generated by event viewer everyday.
2. HQSVR-KASP01$ (Server B) is a windows server 2016, login only using domain admin. The password never been changed.
3. the event generated at another windows server 2016, Server A. So I assume it fail login from server B to server A.
4. Server A using local Admin access to login
Any suggestion or workaround on this is highly appreciated. Thanks.
Continue reading...
Currently, Our server keep getting Failed Login Event ID 4625 as detailed below:
—————————————————————————————————————————————
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: HQSVR-KASP01$
Account Domain: GSCHQMY
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: HQSVR-KASP01
Source Network Address: 192.168.1.111
Source Port: 50346
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.
————————-–—————————————————————————————————————————————————————————————————
1. It keep been generated by event viewer everyday.
2. HQSVR-KASP01$ (Server B) is a windows server 2016, login only using domain admin. The password never been changed.
3. the event generated at another windows server 2016, Server A. So I assume it fail login from server B to server A.
4. Server A using local Admin access to login
Any suggestion or workaround on this is highly appreciated. Thanks.
Continue reading...