We help IT Professionals succeed at work.

Multiple accounts Lockout

96 Views
Last Modified: 2020-10-18
Hello,
We having random accounts lockout and a few account persistently among the lockouts. Using Netwrix account lockout examiner, it indicates the PDC from where the account is locked and the workstation as our exchange front end (2010). The details for event id 4625 on the exchange server does not have any information as to where the lockout is coming from so Source Network Address is blank. Anyone encountered this before? Attached are some of the details.
Comment
Watch Question

Dr. KlahnPrincipal Software Engineer
CERTIFIED EXPERT

Commented:
(The attachment didn't come through; please try again.)
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
When the source of the auth requests is exchange, this means users have email clients, on Hines, etc. that use outdated passwords.
You have to scan the exchange security log for logi. Events it will have the info on the source.
Rodney BarnhardtServer Administrator
CERTIFIED EXPERT

Commented:
When we have this happen it is usually due to a mobile device with an old password. We use Varonis for our monitoring and any time we have a similar issue, the user has changed their password, but failed to change it on their mobile device.
AmitIT Architect
CERTIFIED EXPERT
Distinguished Expert 2017

Commented:
What type of users getting account lockout. Normally, i see lockout issue with IT admin users, who uses their account to configure various task and forget to update the password. If it is related to normal user, 99% it might be related to mobile device. You need to review IIS logs to find out the cause.
Jason ZondagSenior Managed Services Specialist

Commented:
Check Exchange transport logs as well.
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Nice catch, possible issue not updating the outgoing password, though the issue will be apparent to the user while the checks for emails might not ......and run in a schedule.

Author

Commented:
Focusing on 3 users (not admins), one has no mail on any mobile device setup for him, his account still lockout with no source in the event viewer ID 4625 (on the front end exchange server).  IIS logs shows access to his mailbox by an ip address which is the internal ip of our company firewall. Another has only one setup on only one phone and with "Get-ActiveSyncDeviceStatistics" for his mailbox shows the LastSuccessSync being a minute ago but account still keeps locking out randomly. Enabled protocol logging level to Verbose but logs not updating. Netwrix showed a disabled account and also lockout. Need to find the source or services behind  the locking of the accounts from the exchange server's end. Below is one of the event details.




An account failed to log on.

Subject:
      Security ID:            NETWORK SERVICE
      Account Name:            XXXX$
      Account Domain:            ZZZZ
      Logon ID:            0x3e4

Logon Type:                  8

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

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

Process Information:
      Caller Process ID:      0xb10
      Caller Process Name:      C:\Program Files\Microsoft\Exchange Server\V14\Bin\EdgeTransport.exe

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

Detailed Authentication Information:
      Logon Process:            Advapi  
      Authentication Package:      MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
      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.
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION

Author

Commented:
@Arnold, yes but the security log in Exchange failed login details show "Source Network Address" as BLANK, no computer name or ip address to trace to.
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
The event you pose is a network access related event.
Check exchange log/queue for emails to these users to see what might be going on.
Check user server based rules.
Does yyyyy correspond to the user account being locked?

The iis imap/pop
If they do not have mobile, do they have access to work email from outside.

Have each check their hone wan ip, then as an experiment, block those ip from being able to enter your network.
See if those accounts continue to lock.
Is there a pattern to the lockout?
Do you have an RDS in the environment where these three have disconnected session within which they have an email client running with a login prior their recent password change?

Author

Commented:
Yes yyyy denote the user account being lock. One account without mobile phone setup only does works from both office and out of office with his corporate computer (with outlook already setup on it). No home wan setup for all the account locking out. They all use mobile data services. We don't have an RDS in our environment. More than 6 accounts keeps locking most of the time( sometimes they lockout immediately they are unlocked) and some are just randomly locking once in a while. Exchange log show some "Inbound AUTH LOGIN failed because of LogonDenied" from some external IP addresses (Germany, Russia, Panama etc) on most of the lockout accounts.
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Shaun VermaakSenior Consultant
CERTIFIED EXPERT
Awarded 2017
Distinguished Expert 2019
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Seth SimmonsLead Systems Administrator
CERTIFIED EXPERT

Commented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Split:
-- 'arnold' (https:#a42963153)
-- 'arnold' (https:#a42963893)
-- 'Shaun Vermaak' (https:#a42968210)


If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer