Avatar of JUGGER97139
JUGGER97139
 asked on

EXCHANGE PROBLEM 451 4.4.0 Primary Target IP address responded 421 4.2.1 unable to connect

Hi,

I have a Exchange Server 2010 on a Windows Server 2008 X64.
Everything was good but since once week i have message not delivery ton my client.
In the exchange manager console i can see this error:

451 4.4.0 Primary Target IP address responded 421 4.2.1 unable to connect. Attempted failover to the alternate host but That did not succeed. Either, there are ni alternate hosts, or delivery failed to all alternate hosts

I have an other send connector and i have the differents domains with trouble inside.
I used the smtp-msa.orange.fr

With some domains, i have no problem.

Could you help me?

NB: Sorry for my English I'm not so good --> (French Speaking)
Exchange

Avatar of undefined
Last Comment
neilpage99

8/22/2022 - Mon
neilpage99

I had that problem before.
For me it turned out to be poor DNS resolution. Make sure yoru Exchange server can successfully resolve the MX records (and they are the correct MX records) for your destination email server.

From the Exchange Server:
1. Open a command window.
2. type:
nslookup

Open in new window

...and press <ENTER>

3. Type:
set q=mx

Open in new window


4. Type:
recipientdomain.com

Open in new window

...but use the real domain name of the recipient that you're trying to send to.

5. Verify that your query returns valid results - compare them to what you find when using http://www.dnsstuff.com/
JUGGER97139

ASKER
No problem with those commands

the return is valid
neilpage99

Did you use the link I provided, and enter the recipient domain in the MX and DNS tools to verify resolution is correct?

Can you send a test email to the SAME RECIPIENT from a different, external test email account like GMail or Yahoo?

Try this link:
https://www.testexchangeconnectivity.com/ 
And enter information about BOTH your sending email server, and the recipient email server.

Also, are you using any third party resources, like a smart host, or forwarder, or special send connector?
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
neilpage99

If that doesn't help, consider the possibility that you need to for SMTP "HELO" commands instead of the native EHLO.
http://www.networkadminsecrets.com/2010/04/421-and-451-exchange-2007-errors.html
JUGGER97139

ASKER
Yes i did

I can send a test email to the same recipient from external account

I used a send connector like a smart host  (smtp-msa.orange.fr)

The resolution is correct but i have a dns request timed out
ASKER CERTIFIED SOLUTION
neilpage99

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
neilpage99

The error you received is often a result of SPAM filter on the recipient side. They are denying your sending SMTP connection because it is registered on a RBL or some other spam-related list. I know you said you're using a smarthost connector, but confirm email is being sent using that connector, and that the provider on the other end of that connector is no having spam related issues.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.