A robust email, calendaring, and collaboration platform developed by Microsoft, designed for enterprise-level communication and data management.Miscellaneous topics that do not fit into specific categories.
Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.
Based on what you shared, the behavior you are experiencing appears to be related to port 25. I would suggest starting with the checks below to help narrow down.
First, please confirm whether your Exchange server is listening on port 25 by running:
Test-NetConnection -ComputerName localhost -Port 25
If the result is True, then the service is listening correctly. In that case, the next step would be to review your Firewall or Router configuration to ensure everything is open and consistent:
- Inbound TCP port 25 is allowed from any source IP
- No recent rule changes that may impact connectivity
If the result is False, then it would be helpful to check the following areas on the server side:
Transport services status:
Get-Service MSExchangeTransport, MSExchangeFrontEndTransport
Receive connector status:
Get-ReceiveConnector | Select Name, Enabled, Bindings
Windows Firewall rules related to port 25:
Get-NetFirewallRule | Where-Object {$_.LocalPort -eq "25"} | Select DisplayName, Enabled, Direction, Action
I hope this gives you a clear direction on where to look next. If you have any updates or findings, please feel free to share them here
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.