locked
Fully Patched windows server 2012 R2 Failed audits every seconds RRS feed

  • Question

  • I need some help here, i am still unable to resolve this issue, after a few days of crawling the internet and trying countless resolutions that have failed

    Have tried: 

    - Checking the SMTP logs, nothing

    - Checking server for stale credentials, nothing 

    - Checking Credential manager, Nothing

    - Checking network services, All automatic are running and manual run when started 
    - Re synching DB users
    - Viewing backups, running successfully
    - Turned off DNS event logging to see if the events stopped, nothing 
    - Testing to see if this is NTFS permission problem, nothing

    Here is a paste of the log!: 

    An account failed to log on.

    Subject:

    Security ID: SYSTEM

    Account Name: PWM-SE12$

    Account Domain: POMBOWEALTHMGT

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

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

    Network Information:

    Workstation Name: PWM-SE12

    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.

    Tuesday, July 12, 2016 12:47 PM

All replies

  • Hi,

    >windows server 2012 R2 Failed audits every seconds.
    I want to confirm with you if it indicates that the event log – “An account failed to log on” is recorded in event log every seconds, and there is a lot of this event.

    If so, using anti-virus software to have a full disk scanning. Undo the change(such as new installation, changed configuration and etc. ) which has been made before this problem happened. 

    Beside, either service or process may also cause this failed log on. Reference the methods mentioned in below link for further narrow down this problem:
    https://social.technet.microsoft.com/Forums/office/en-US/39f4b300-1521-4f1c-bb3d-b3836d7ff760/lots-of-failure-auditan-account-failed-to-log-on?forum=winservergen

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, July 13, 2016 8:56 AM
  • Yes, I can confirm that the events are every second.. Attaching a screenshot 

    Also, Iv taken a look at the services, i can confirm the issue is not with them.

    Wednesday, July 13, 2016 1:00 PM
  • Yes, I can confirm that the events are every second.. Attaching a screenshot?

    Also, Iv taken a look at the services, i can confirm the issue is not with them?

    Friday, July 15, 2016 1:09 PM