I used a tool called ExMon to determine what network address the connection was coming from and determined these were originating from outside the company via a mobile device.In a nutshell, I found that my account was locking out via failed authentication attempts to our Exchange server.This article is going to give an in-depth explanation of how to resolve issues like this, but first, here’s the short version: Fortunately I’ve come across this issue before, so I didn’t waste time resetting my password since that’s a red herring here.

In this case the password was correct, but the account was locked. Microsoft isn’t always great about telling you exactly why something isn’t working. Everything seemed fine for a day or so, then when I logged into the VPN from home and tried to connect to my work PC via Remote Desktop I got this error: It all started after a routine password change of my Active Directory account. The issue and how I resolved it is worthy of commentary since it illustrates the complexity of troubleshooting and how to proceed in a sane and orderly fashion.

Both were based upon real-world events or ideas from day-to-day operations.īad events often seem to occur in threes, so as it turned out I faced a more complicated issue along the same theme. I wrote recently about how to reduce account lockouts and password resets and how to troubleshoot account lockouts via Group Policy. Developing ways to reduce and resolve Active Directory account lockouts has been one of my quests lately.

How to verify exchange account on mac