none
Audit Failure event ID 4625 RRS feed

  • Question

  • Windows 2008 R2 server has over 3000 audit failures in the last hour with the following description. Any help would be appreciated.

    An account failed to log on.


    Subject:
    Security ID:  SYSTEM
    Account Name:  PHS-AERO$
    Account Domain: PUSD
    Logon ID:  0x3e7


    Logon Type: 8


    Account For Which Logon Failed:
    Security ID:  NULL SID
    Account Name:  Administrator
    Account Domain: PUSD.local


    Failure Information:
    Failure Reason: Unknown user name or bad password.
    Status:  0xc000006d
    Sub Status:  0xc000006a


    Process Information:
    Caller Process ID: 0x4b4
    Caller Process Name: C:\Windows\System32\svchost.exe


    Network Information:
    Workstation Name: PHS-AERO
    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.

    Monday, February 13, 2012 6:15 PM

Answers

  • looks like you have either deleted the computer account for machine PHS-AERO.

    or the machine has corrupted its "secure-channel" with the DC - meaning the machine's password that the computer is trying to use against the DC is diffrent from the password (hash) that is stored on the DC in question. This can happen either by some corruption of the local computer registry on the PHS-AERO machine, or maybe AD restore. Or the most probable reason is that the machine PHS-AERO has just changed its computer password (happens every 30 days) on a different DC and the change has not yet replicated to the DC with the errors.

    You can check the machine's PHS-AERO health by using:

    NLTEST /SC_VERIFY:domain-name

    and if the result is SUCCESS, you can also try NLTEST /SC_RESET:domain-name several times to see what happens. The SC_RESET command forces the machine to select a new DC to authneticate against and you should see a random switching between your DCs. This should go smoothly when you reset several times. If the problem was only temporary due to the replication latency, you should not see any further errors on the machine nor on any DC.

    ondrej.

    • Marked as answer by Bruce-Liu Wednesday, February 29, 2012 2:46 AM
    Tuesday, February 14, 2012 8:45 AM

All replies

  • looks like you have either deleted the computer account for machine PHS-AERO.

    or the machine has corrupted its "secure-channel" with the DC - meaning the machine's password that the computer is trying to use against the DC is diffrent from the password (hash) that is stored on the DC in question. This can happen either by some corruption of the local computer registry on the PHS-AERO machine, or maybe AD restore. Or the most probable reason is that the machine PHS-AERO has just changed its computer password (happens every 30 days) on a different DC and the change has not yet replicated to the DC with the errors.

    You can check the machine's PHS-AERO health by using:

    NLTEST /SC_VERIFY:domain-name

    and if the result is SUCCESS, you can also try NLTEST /SC_RESET:domain-name several times to see what happens. The SC_RESET command forces the machine to select a new DC to authneticate against and you should see a random switching between your DCs. This should go smoothly when you reset several times. If the problem was only temporary due to the replication latency, you should not see any further errors on the machine nor on any DC.

    ondrej.

    • Marked as answer by Bruce-Liu Wednesday, February 29, 2012 2:46 AM
    Tuesday, February 14, 2012 8:45 AM
  • I am not completely sure I understand what you are saying (sorry, pretty new at this). Error went away yesterday afternoon. This morning I successfully ran NLTEST like you suggested with no errors. SC_RESET was also succesful. I think you might have been right about the DC being the problem since we had just barely had it go down and had to reset a bunch of settings to get it back up.

    I thought the problem was gone but have now noticed the error returned except for one difference, the Account Name has changed from "administrator" to "aloha". Everything else is identical to what I quoted above. NLTEST is still succesful.

    Thanks

    Tuesday, February 14, 2012 7:03 PM
  • Hello

    I know this thread is two years old but I have started to experience something similar, this is a new installation of SBS2011 and it's been up about a week. We have only just finished configuring it and installing it to match are needs.

    Anyway I have started to get quite a lot of audit failures, what is puzzling me is that all the usernames are no existent on our box, below is an example. We do not have an account called receptionist, other audit failures seem to be using other name like john, jan, etc.. non of which exsist.

    An account failed to log on.
    Subject:
     Security ID:  NULL SID
     Account Name:  -
     Account Domain:  -
     Logon ID:  0x0
    Logon Type:   3
    Account For Which Logon Failed:
     Security ID:  NULL SID
     Account Name:  RECEPTIONIST
     Account Domain:  
    Failure Information:
     Failure Reason:  Unknown user name or bad password.
     Status:   0xc000006d
     Sub Status:  0xc0000064
    Process Information:
     Caller Process ID: 0x0
     Caller Process Name: -
    Network Information:
     Workstation Name: 
     Source Network Address: -
     Source Port:  -
    Detailed Authentication Information:
     Logon Process:  NtLmSsp
     Authentication Package: NTLM
     Transited Services: -
     Package Name (NTLM only): -
     Key Length:  0

    Any help will be appreciated, thank you in advance.

    Thursday, November 10, 2016 6:51 PM
  • Hi

    Did you get a response to your query posted Nov 10 2016? We are seeing something similar and an Audit failure is logged 15-20 seconds. The account name varies. Any assistance appreciated. Thank you.

    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          10/02/2017 06:34:58
    Event ID:      4625
    Task Category: Logon
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      REMOVED FOR SECURITY PURPOSES
    Description:
    An account failed to log on.

    Subject:
    Security ID: NULL SID
    Account Name: -
    Account Domain: -
    Logon ID: 0x0

    Logon Type: 3

    Account For Which Logon Failed:
    Security ID: NULL SID
    Account Name: GENE
    Account Domain:

    Failure Information:
    Failure Reason: Unknown user name or bad password.
    Status: 0xc000006d
    Sub Status: 0xc0000064

    Process Information:
    Caller Process ID: 0x0
    Caller Process Name: -

    Network Information:
    Workstation Name:
    Source Network Address: -
    Source Port: -

    Detailed Authentication Information:
    Logon Process: NtLmSsp 
    Authentication Package: NTLM
    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, February 14, 2017 8:19 PM
  • We're running into the same issue here. Haven't figured it out yet.

    Simon Ferguson

    Friday, May 12, 2017 8:07 PM
  • I specified all DCs manually and this fixed the issue:

    NLTEST /SC_RESET:domain\dc1
    NLTEST /SC_RESET:domain\dc2
    ...
    PS: Did nothing on DCs.
    Friday, April 13, 2018 4:31 PM