Hello,
We are currently having trouble tracing back the source of multiple failed login attempts, please help. It seems that we have a device trying to brute force its way into our network. When I check our DC Security Logs, I see multiple (1000+) Failed audits,
EventID 4776 with limited information. Below is an example of Windows Security Logs and Debug Netlogon logs. I've replace any and all site specific information.
When I check the security logs on 'Server1', they don't show any failed login attempts or anything suspicious. I ran a packet capture on 'Server1' while the failed logins generated to see if I could find the source. I was unable to find any of the failed
audit account names, 'administrator' in this case, in the capture results.
Can someone please assist me in finding out what might be attacking 'Server1'? Could I use 'Netsh Trace' or WireShark to determine the source of the attack and what port is being leveraged? Are there any additional logs I can enable or view to see what might
be trying to authenticate against 'Server1'? The issue is still happening today and I can provide updated logs if need be.
Information Replaced
Domain Controller: ADServer (server 2012R2)
Domain Name: Domain.local
Server Name: Server1 (server 2008 R2)
Event ID from ADServer
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 12/21/2018 8:00:04 PM
Event ID: 4776
Task Category: Credential Validation
Level: Information
Keywords: Audit Failure
User: N/A
Computer: ADServer.domain.local
Description:
The computer attempted to validate the credentials for an account.
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account: Administrator
Source Workstation: MSTSC
Error Code: 0xC0000234
Verbose security logs
12/21 20:00:04 [LOGON] [2328] DOMAIN: SamLogon: Transitive Network logon of Domain\Administrator from MSTSC (via Server1)
Entered
12/21 20:00:04 [LOGON] [2328] DOMAIN: SamLogon: Transitive Network logon of Domain\Administrator from MSTSC (via Server1)
Returns 0xC0000234
Ps. As per best practice our 'administrator' account is disabled