Active Directory Account Lockouts Every Second of the Day

Ornaldo 41 Reputation points
2020-11-03T13:32:31.327+00:00

Hello everyone,

Since last week ago I’m struggling with my Active Directory Account Lockouts

I have read all the possible answers on MWG Forums, Tech Support, Sys Admin and Microsoft Forms also.

Till now I find myself in the middle of nowhere. So I decided to post here once again the question if anyone has experienced this before and how it has been solved

Note: In all the previous questions marked as solutions I could not find anything useful

So below I will describe my situations:

Last week ago I changed my windows AD credentials due to expiry date
Since that moment I keep getting locked every second !
If I want to be unlocked the sys admin should be on the phone with me. They need to click on OK and unlock my user and me at the same time I should click OK in order to login !

Without this synchronization it is not possible since my user is getting locked two frequently

I have changed the password four time but no result
From the logs of AD, on event 4740 I can see only that the caller computer name is MWG ( which is our proxy web gateway server )
Our Proxy ( MWG ) is joined into domain ( using NTLM2 method )
I have tried to enable on MWG the bad password logs but nothing useful can be found from there
I keep getting the popup from proxy (MWG)
I keep getting locked
I have logged on every possible server with rdp and sign out from there from my user
I have check all the possible logs from AD but the only thing that I keep looking is: Caller computer name MWG

%NICWIN-4-Security_4776_Microsoft-Windows-Security-Auditing: Security,rn=506628954 cid=9316 eid=728,Mon Nov 02 12:28:46 2020,4776,Microsoft-Windows-Security-Auditing,,Audit Failure,Credential Validation,The computer attempted to validate the credentials for an account. Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 Logon Account: UserName Source Workstation: McAfeeNew Error Code: 0xC0000234

Tech Support of MWG is saying that is not MWG which is looking my AD credentials but another computer
I believe the opposite:  maybe on another workstations where the pop up of MWG has appeared I may have inputed my AD credentials
I have checked on all servers and my workstation for Windows Credentials ( like everyone) is suggesting but nothing is shown there.
I have used Netwrix_Account_Lockout_Examiner on our Domain Controller but I could find nothing

I found some task scheduler on my PC with my UserName wich I have disabled but it is not working

Since Netwrix_Account_Lockout_Examiner is using event viewer logs I find it useless

Please could you help me ?

Has anyone faced this before ? Maybe it is better to close my UserName but I find it not a good solution

Thank Youuuu

Windows for business Windows Client for IT Pros Directory services Active Directory
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2020-11-04T08:34:17.753+00:00

    Hello,

    Thank you so much for your feedback.

    So sorry that we are not professional with Powershell. We have the dedicated powershell forum. For any question, we could ask a question and select the powershell tag.

    https://learn.microsoft.com/en-us/answers/topics/windows-server-powershell.html

    More logs such as events logs, Netlogon debug logs, Process monitor, Network monitor and NTLM etl trace will be needed to further troubleshoot this issue. According to provided information, the Source workstation on event ID 4776 is McAfeeNew.

    According to our experience, is there any policy on the McAfee server to make the clients to access any shared path via \IP address\shared path (For example)?When accessing the shared path, the old credentials were used. Not sure whether it helps. We could kindly have a check about this.

    For any question, please feel free to contact us.

    Best regards,
    Hannah Xiong

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


2 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-11-04T05:55:59.583+00:00

    Hello,

    Thank you so much for posting here.

    This event 4776 generates every time that a credential validation occurs using NTLM authentication. It shows successful and unsuccessful credential validation attempts. The error code 0xC0000234 means "Account logon with account locked."

    Through the 4776 event log, we can obtain the address of the Source workstation (McAfeeNew), log in to the computer and refer to the following steps to check:

    • Check the credential management to see if there are cached user’s old credentials
    • Check whether there is a wrong password to mount the network disk
    • Check whether the user has used the wrong password to start services, run scheduled tasks, etc.
    • Are there other third-party programs that cache the user's wrong password

    For any question, please feel free to contact us.

    Best regards,
    Hannah Xiong

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Ornaldo 41 Reputation points
    2020-11-11T08:05:39.52+00:00

    Hello, yes I found it finally :) :) :)
    It was inserted on one of our system in order to authenticate against the proxy server

    I found it by accident :)


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.