We are receiving Event 4625 almost 3,000 times per hour...it appears to be related to an old consultant account that helped configure LF almost two years ago. Here is the full message:
06/23/2017 10:51:19 AM LogName=Security SourceName=Microsoft Windows security auditing. EventCode=4625 EventType=0 Type=Information ComputerName=***lfweb.****.net TaskCategory=Logon OpCode=Info RecordNumber=59956708 Keywords=Audit Failure Message=An account failed to log on. Subject: Security ID: ****\LF_Service Account Name: lf_service Account Domain: **** Logon ID: 0x1DA89 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: consultant Account Domain: **** Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC0000064 Process Information: Caller Process ID: 0x5cc Caller Process Name: C:\Program Files\Laserfiche\Directory Server\LFDS.exe Network Information: Workstation Name: ORAULFWEB Source Network Address: - Source 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.
We have tried to re-register the SPN to no avail. Since the consultant's account no longer exists, I'm thinking that is the root cause. However, I have verified that all LF services are indeed using our "lf_service" account...and not the consultant account.
So I guess my question at this point is whether there's any place inside LF itself to configure service accounts...config files, admin GUI, etc.? Just running out of ideas at this point.
Regards,
Matthew