getting logon failure on Windows server 2016 error 4625

Question

within the last week I am getting error 4625 on my Windows Security event viewer log. This is a on premise server not a VM, 4 workstations joined to the Domain. Here is the information from the event viewer. please let me know what else do you need to give me resolution.

Thanks,

Jamshid

An account failed to log on.

Subject:

Security ID:		SYSTEM

Account Name:		MLFSERVER$

Account Domain:		ABCDMLF

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:	0x38c

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

Network Information:

Workstation Name:	MLFSERVER

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

Hi Daisy, yes. they are all part of the domain. I looked at the services. I only see some that in the login they have empty field for the account. What does that mean if in the services login the field for the account? Could they be the cause? Can I delete them and add them. I am not sure about how to set up the additional audits and do not want to mess anything up.

Answer 2

Answer 3

Hi Daisy,

Thank you for assisting me with this. It is a domain controller Windows server 2016 essential.

i did not find any locked account.