The default front end receive connector does not require authentication by default.
Are you sure its related to the lockouts?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
To All,
Please help or suggestion me to resolve this issue!!
I have an user account which locks out almost everyday in AD & Security logs from Domain Controller indicates the caller computer name is the exchange server. When I look into the exchange server Security Logs I can see there are multiple failed logins but it gives me no specific info about from where is this originating from.
I've checked the IIS logs as well but can't find anything related to this particular user account.
Please see the Exchange Server Log:
Event ID (4625) as picture below,
Thank you in advance,
Tanisorn
The default front end receive connector does not require authentication by default.
Are you sure its related to the lockouts?
Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query
If you are experiencing account lockouts that originate from the Exchange Server, there are several possible causes. These can include incorrect credentials being used to access the server, a malware infection on the server, or a user account being left logged in on the server. To troubleshoot this issue, you can start by running a malware scan on the server to check for any malicious software. If the scan comes up clean, you can then check the user accounts to see if any are left logged in. Additionally, you can set up an audit policy to track logon events to help identify any suspicious activity. Finally, you can configure a lockout policy to prevent users from being locked out due to incorrect credentials.
If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.
The source is the transport service, meaning SMTP auth is failing.
enable SMTP protocol logging on the front end client receive connector (s) and match up the log entries with the lockouts in the event logs by date and time and hopefully you can find the IP