A domain user account constantly getting locked out.

Each day, a particular user constantly get locked out of his computer. We always need to unlock his domain account to allow him to log in. I believe he has a session somewhere on another machine, where we need to log him out. This happened after he changed his domain password.

I use a lockout tool to trace the source:
2016-08-11_9-24-29.png
I then check the DC security log, and the client address (highlighted) points to an Exchange server. However, the user would not have access to log into our server. So, I am thinking that maybe he needs to set his new password on a mobile device (cell phone). However, the user mention that he does not use email on his cell. I know the lock out is occuring somewhere within email, but cannot trace exactly where. Anything I can try to resolve this issue?
2016-08-11_9-25-50.png
joukiejoukAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Schnell SolutionsSystems Infrastructure EngineerCommented:
No smartphone...

Does it also mean that he is not using a Tablet (Active Sync), an (Outlook) Client from a PC or MAC?

If it does not appear with information from the user, you will need to check the IIS logs on the Exchange server that corresponds to the connection (Outlook Anywhere, Active Sync, EWS, etc).
joukiejoukAuthor Commented:
I am not an Exchange guy. I know enough to get by. We use Office365. Anything I can check there? The user does not use any mobile device. I was inform he usually log into Office365 from home  (and never signed out), Would that cause the issue? If this is the case, how would I sign him out of Office365? Again. I am not solid in Exchange/Email administration. Our Exchange admin is out on vacation.
Schnell SolutionsSystems Infrastructure EngineerCommented:
The DC logs pointed the unsuccessful authentication from an Exchange server... was it a local server? do you have an hybrid environment with O365 and On-primases exchange servers?
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

joukiejoukAuthor Commented:
Yes, we have a hybrid environment (local Exchange server directing to O365).
Schnell SolutionsSystems Infrastructure EngineerCommented:
cool, so anyway, if the events are coming from the local server. We need to change the exchange connection logs (IIS Logs), and then check from where the connections are coming from.
joukiejoukAuthor Commented:
So I checked IIS logs on the local AD SYNC server, and here is what i see for the user (those in bold text has been changed to hide our info).

2016-08-11 11:48:57 10.10.xx.xxx POST /autodiscover/autodiscover.xml &CorrelationID=<empty>;&ClientId=SNATDBH9DEYYFVNXIAUSQ&cafeReqId=c013a4ea-d44b-461b-afcb-120b9f9814da; 443 abc@testcorp.com 173.51.116.242 WindowsMail/17.5.9600.20911 - 401 1 1909 15


2016-08-11 16:47:10 10.10.xx.xxx POST /Autodiscover/Autodiscover.xml &CorrelationID=<empty>;&ClientId=DINEXRFO0KLKVNBWFG&cafeReqId=ec349c60-8ad3-467c-9936-4d8a824fa52e; 443 XYZ\abc 10.10.xx.xxx Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6743;+Pro) - 200 0 64 15


The 10.10.xx.xxx is our subnet. Not so sure about the 173.51.116.242. Does this help? What should I check next?
Dirk MareSystems Engineer (Acting IT Manager)Commented:
On his workstation go to
Control Panel
User Accounts
on the left Manage your credentials

Remove or edit all credentials linked to outlook "MS.Outlook"

DirkMare
Schnell SolutionsSystems Infrastructure EngineerCommented:
That IP might corresponds to the public ip that is used from the client to unsuccessfully connect to your exchange.

It means that somewhere these logins are trying to complete. If it is a device of your user the password needs to be updated or the credential eliminated like 'Dirk mare' specified.

You also need to be aware, that if your mail services are published to the internet, and there is not a solution limiting these connections, it is possible that anyone knowing your web service URL and a user account of your domain can easily conduct a denial of service attack for that account... blocking it.
Senior IT System EngineerIT ProfessionalCommented:
You can use this freeware: https://www.netwrix.com/account_lockout_examiner.html 

To check the locked out account.
joukiejoukAuthor Commented:
Sorry, been out for a while (personal matter). The user is still experiencing the lock out. Last thing i tried was the below:

On his workstation go to
Control Panel
User Accounts
on the left Manage your credentials

Remove or edit all credentials linked to outlook "MS.Outlook"


I only edit his password to his newly changed domain password. He is still experiencing lock out issues. I think what I will try next is to remove credentials linked to outlook "MS.Outlook".
Dirk MareSystems Engineer (Acting IT Manager)Commented:
My original suggestion was to remove the stored credentials next time you open outlook remember to tick 'Remember password'

DirkMare
Senior IT System EngineerIT ProfessionalCommented:
Have you checked the other software which may cache the credentials like:

iTunes, iPhone and perhaps any other software which uses the AD authentication for Proxy connection ?
joukiejoukAuthor Commented:
This user continues to get locked out, and when checking DC logs, the source of the lock out still point to the Sync server for Exchange. We have a hybrid environment with 0365 and On-primases exchange servers.

I tried removing all stored credentials in Credential Manager, and even gone as far as recreating a new Windows profile for the user, but he continues to get locked out. This is annoying.
joukiejoukAuthor Commented:
Will recreating the AD account resolve the issue? Is there any other free tool that might help troubleshoot this? The only tool I've used so far is lockoutstatus.exe. Can I check anything in O365 EMC? Logs?
MaheshArchitectCommented:
Check on each domain controller for latest security event ID 4740 which can tell you the source compter from where attempt were happening with wrong password and account is getting locked.

Then check all those computers for presense of wrong password such as service, schedule tasks, any application and possible virus infections if any
AmitIT ArchitectCommented:
If you are unable to find source. Last option is to rename the SAM account name for this user. Don't need to create new account.

Open user properties in AD, click on account tab, append any new digit or letter at the end of the name. Like change it from User to User1. Ask user to log off and login back with User1 again. Rest will be same for user.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gheistCommented:
Windos 'run as service; stores clear password and makes guesses on password change.
joukiejoukAuthor Commented:
Mahesh,

I checked all DC for Event 4740, and it still trace back to our AD Sync server. The user does not have access to RDP or log into that server.

Amit,

I want to try your method, but if I change the SAM account name, what would be impacted? His email is still using the current SAM account name. Will this impact his email access?
AmitIT ArchitectCommented:
Renaming will not cause any profile issue. Only thing is change, user now need to login using User1.
Hypercat (Deb)Commented:
I didn't read this whole thread, but I've had experience with this issue at one of my clients.  The user was getting locked out and in her case she wasn't even using ActiveSync or any other mobile device.  I concluded that it was likely someone trying to use my client's email server to relay mail, possibly using a mobile device to connect, and was trying to use her user name to authenticate.  It was a little hazy and I had trouble tracking the activity. What I did to fix the issue was to change her login ID; IIRC I just added her middle initial (the original ID was first initial/last name).  I did NOT change her email address, and nothing else internally (roaming profile, folder redirection, etc., etc.) was affected.  This instantly fixed the issue. It seems that someone else earlier in the thread has suggested this, and I just wanted to chime in and say that it worked for me and I hope it does the same for you.
Guillermo FeijóoSystems administratorCommented:
i, ve suffered similar issues and I always
import exchange activesync log files to an excel sheet
order by username and find http status codes 4xx
use a mac vendor lookup web page to get the lockout source hardware vendor
punish the worker whom cell phone was "stolen" last year and his daughter is using today.

im sorry fory bad english
AmitIT ArchitectCommented:
Renaming user sam account name is the only option to resolve this issue.
Thomas Zucker-ScharffSolution GuideCommented:
Don't forget to check user's windows credentials manager.
joukiejoukAuthor Commented:
I had no choice but to rename the SAM account, which resolved the user's issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.