Solved

4.2.1 Unable to connect. "Attempted failover to alternate host ....

Posted on 2013-11-08
4
3,549 Views
Last Modified: 2013-11-14
Here is one for those who like a challenge.


I have had a very interesting issue come up today.
I can find no reason for this what so ever.

I have seen a number of posts about this and most all of them are around port 25 for an ISP - this is not the case. ***

My servers have been up and running for about 3 years
their serevers have been up and runnig for about 2 years.
email has in the past been sent AND received with no trouble.
reciently my email will not leave the queue for thier domain.
My Users can send / receive email from any domain / user
their users can send / recive form any domain / user
***
The ONLY thing that is not working on both domains is the ability for us to send them emails.

I know I have not changed anything on my end.  My fellow minions claim to be guilt free.  And the receiveing end says no changes on his end.

- error message -
541 4.4.0 Primary target IP address responded with: "421 4.2.1 Unable to connect." Attempted failover to alternate host, but that did not succeed.  Either there are no alternate hosts, or delivery failed to all alternate hosts.


 - checked MX / DNS records with MxToolBox.com -
Mine cam back clean his has an issue with  
"Warning - reverse DNS does not match SMTP Banner" &
"Warning - Does not support TLS"
 
I can telnet to his server on port 25 and receive the proper responses from the exchange server ehlo command.

there are no 3rd party relay services.
0
Comment
Question by:MPonto
  • 2
  • 2
4 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39634558
Can you actually do a full NSLOOKUP of the MX records from the Exchange server and get the correct results? Are you on the same ISP by any chance?

Simon.
0
 

Author Comment

by:MPonto
ID: 39634775
Yes I get a full look up on both servers via nslookup
and
Yes we are both on the same ISP.
I have the isp looking into routing as well
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39637253
Being on the same ISP would tend to suggest that either the ISP is doing something, or the other side ahs their restrictions or network setup incorrect. I have seen some odd things happen where the subnet was configured incorrect on the router and local (ie same ISP) traffic was failing.

Simon.
0
 

Author Comment

by:MPonto
ID: 39649515
It was in the DNS servers.  I was using a public server for forwarding requests (4.2.2.4) and when I changed it to the DNS or our ISP it works fine.
0

Featured Post

Free book by J.Peter Bruzzese, Microsoft MVP

Are you using Office 365? Trying to set up email signatures but you’re struggling with transport rules and connectors? Let renowned Microsoft MVP J.Peter Bruzzese show you how in this exclusive e-book on Office 365 email signatures. Better yet, it’s free!

Join & Write a Comment

Resolve DNS query failed errors for Exchange
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now