HCD01
asked on
Exchange 2007 email not received by external domains - internally it works
This problem started today without system configuration changes. User are not able to receive emails from any external domain. There are not error messages rec’d by the sender. User can successfully send emails to all external addresses without error. Emails are not received on Outlook client or owa.
I’m not sure if this is related to the pressure back issue or not.
I would appreciate any assistance on this matter since it’s been down all day. (Note: I’m new to Exchange and not very familiar with any version beyond setup users)
Problem:
No external email is being received. External senders are not receiving any delivery errors. Internal mail works and we can send externally.
Troubleshooting steps:
1. Rebooted the exchange server – no resolve.
2. Ran the Exchange Toolkit
• Received error - Mail submission failed. Error message: Service not available, closing transmission channel. The server response was: 4.3.2 Service not available, closing transmission channel.
• Sender ID accepts failed messages: Sender ID filtering is set to accept messages that fail the Sender ID validation test
• I received the test mail from the troubleshooting assistant: ExMFA-MailAcceptTest@Fabri
3. I attempted to telnet but received the same server response error: 421 4.3.2 Service not available, closing transmission channel.
4. I ran the Microsoft Connectivity Analyzer and received a message (only warning included): Connectivity Successful with Warnings.
Analyzing SMTP Capabilities for server housecalldoctorstexas.com.
The test passed with some warnings encountered. Please expand the additional details.
Additional Details
Unabled to determine SMTP capabilities. Reason: Authentication failed to the SMTP server.
Elapsed Time: 97 ms.
Analyzing SMTP Capabilities for server housecalldoctorstexas.com.
The test passed with some warnings encountered. Please expand the additional details.
Additional Details
Unabled to determine SMTP capabilities. Reason: Authentication failed to the SMTP server.
Elapsed Time: 85 ms.
I’m not sure if this is related to the pressure back issue or not.
I would appreciate any assistance on this matter since it’s been down all day. (Note: I’m new to Exchange and not very familiar with any version beyond setup users)
Problem:
No external email is being received. External senders are not receiving any delivery errors. Internal mail works and we can send externally.
Troubleshooting steps:
1. Rebooted the exchange server – no resolve.
2. Ran the Exchange Toolkit
• Received error - Mail submission failed. Error message: Service not available, closing transmission channel. The server response was: 4.3.2 Service not available, closing transmission channel.
• Sender ID accepts failed messages: Sender ID filtering is set to accept messages that fail the Sender ID validation test
• I received the test mail from the troubleshooting assistant: ExMFA-MailAcceptTest@Fabri
3. I attempted to telnet but received the same server response error: 421 4.3.2 Service not available, closing transmission channel.
4. I ran the Microsoft Connectivity Analyzer and received a message (only warning included): Connectivity Successful with Warnings.
Analyzing SMTP Capabilities for server housecalldoctorstexas.com.
The test passed with some warnings encountered. Please expand the additional details.
Additional Details
Unabled to determine SMTP capabilities. Reason: Authentication failed to the SMTP server.
Elapsed Time: 97 ms.
Analyzing SMTP Capabilities for server housecalldoctorstexas.com.
The test passed with some warnings encountered. Please expand the additional details.
Additional Details
Unabled to determine SMTP capabilities. Reason: Authentication failed to the SMTP server.
Elapsed Time: 85 ms.
R_Edwards
Do a Netstat -a. Does it show port 25 as listening
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was able to resolve the issue by redirecting our mail traffic on our firewall
Awesome! glad you found a fix!