Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

451 4.4.0 primary target ip address responded with 421 4.2.1 unable to connect

Posted on 2016-10-12
10
Medium Priority
?
1,033 Views
Last Modified: 2016-10-16
MS exchange q Viewer gives this below message
0
Comment
Question by:saul2paul
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +2
10 Comments
 
LVL 27

Expert Comment

by:MAS
ID: 41839917
Please mention the version of Exchange.
Please make sure your DNS working properly.
Please configure external for external lookup.
0
 
LVL 4

Accepted Solution

by:
Belal Khallad earned 2000 total points
ID: 41839926
The possible causes for the “451 4.4.0 Primary target ip address responded with: "421 4.2.1 Unable to connect." are:

 

1. Your hub transport server or edge server are unable to resolve the external domain names. It can be caused by the incorrect DNS sever settings.

2. Your firewall or ISP block the outbound traffics on port 25.

3. The IP address of your hub transport server or edge server are blocked by the target domain or other issues on the target domain.

The FQDN on the Receive Connector doesn't matter, that is inbound email only. It is only the FQDN on the send connector that is an issue. Ideally the FQDN on the send connector should match the PTR your ISP has set on your external IP address
0
 
LVL 3

Author Comment

by:saul2paul
ID: 41840018
@mas, exchange on Prem 2010 , we have O365 federation service
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 32

Expert Comment

by:Scott C
ID: 41840071
What SP / RU level are you at?  You can find this by running the following Exchange PS command.

Get-Command exsetup | foreach {$_.FileVersionInfo}

Assuming this was a working environment, what, if anything, has changed?  New ISP, new SmartHost, network equipment...etc..
0
 
LVL 16

Expert Comment

by:Todd Nelson
ID: 41841361
This may or may not be related but review the article and check the NIC settings on the Exchange server...

https://oddytee.wordpress.com/2016/08/16/exchange-server-message-queue-error-451-4-4-0-dns-query-failed/
0
 
LVL 3

Author Comment

by:saul2paul
ID: 41845627
the problem was with the SMTP port 25 on the firewall. Now its sorted
0
 
LVL 16

Expert Comment

by:Todd Nelson
ID: 41845637
Belal should be award the points.
0
 
LVL 27

Expert Comment

by:MAS
ID: 41845638
Agree with Todd,
Belal cleary explained about the port 25 block to check in post
0
 
LVL 3

Author Comment

by:saul2paul
ID: 41845641
sorry guys :) thanks for your feedback
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

New style of hardware planning for Microsoft Exchange server.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This video discusses moving either the default database or any database to a new volume.

609 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