New HP workstations connected to Windows server 2016 essentials giving login failure error4625

Question

Hello,

I have noticed that when I connect Brand new workstations to Windows server 2016 essentials, I am getting login failure 4625 in the security of event viewer. When I turn them off the errors stop. This happens on different brand new HP workstation and the server is HP Proliant server Gen 9. Here is the error. I have researched the error and I thought it was the server, but it is the workstation. and it is New HP Workstation Windows 11 pro, connected to the domain controller. i do not get any IP or additional information such as user name. But some kind of issues with the new HP workstation services or apps that is causing this issue. I appreciate your help.

An account failed to log on.

Subject:

Security ID:		SYSTEM

Account Name:		SCHORBRSVR$

Account Domain:		SCHBT12

Logon ID:		0x3E7

Logon Type: 3

Account For Which Logon Failed:

Security ID:		NULL SID

Account Name:		

Account Domain:		

Failure Information:

Failure Reason:		Unknown user name or bad password.

Status:			0xC000006D

Sub Status:		0xC0000064

Process Information:

Caller Process ID:	0x37c

Caller Process Name:	C:\Windows\System32\lsass.exe

Network Information:

Workstation Name:	SCHORBRSVR

Source Network Address:	-

Source Port:		-

Detailed Authentication Information:

Logon Process:		Schannel

Authentication Package:	Kerberos

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.

Answer 1

Hello,

Thank you for posting question on Microsoft Windows forum!

Based on your query of encountering Event ID 4625 (failed logon attempt) on Windows Server 2016 . The key point is that it stops when you turn off the new Windows 11 HP workstations. This strongly points to an issue originating from the workstations, even though the error appears on the server. You can try the following potential troubleshooting steps.

1.Isolate the Workstation:

• As You have already observed that turning them off stops the errors. This confirms the workstation as the source.
• When the workstation is ON, try to identify which one is generating the errors. You might need to check the exact timestamps of the errors on the server and try to correlate them with activity on individual workstations.

2.Test with a Different User Account:

• If possible, try logging in with a different domain account to determine if the issue is account-specific.

3.Check Domain Trust Relationships:

• Ensure the workstation is properly joined to the domain and that trust relationships between the domain controller and the workstation are intact.

4.Verify Secure Channel Integrity:

• To confirm the workstation’s secure channel with the domain by running this command

nltest /sc_verify:<domain name>

• Or using the Powershell command. Test-ComputerSecureChannel -Verbose

5.Verify Domain Controller Connectivity:

• To confirm the workstation is communicating with the correct domain controller by running the command. nltest /dsgetdc:<domain name>

6.Time Synchronization:

• Verify that the time on the Windows 11 workstations is synchronized with your domain controller.
• Running the command w32tm /query /status in an elevated command prompt on the workstation will show you the time source.
• Running the command w32tm /resync to force a resync. In case time significant differences between workstation and DC can cause Kerberos issues.

You can refer to the following articles for further reference regarding the issue of Event ID 4625.

• https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/auditing/event-4625
• https://windowsreport.com/event-id-4625/

Hope the above information is helpful!