[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 183
  • Last Modified:

Exchange 2010 will not send messages

Exchange 2010

I can receive fine from all over the world, send messages internally but no luck sending externally to other domains.
I’m getting the 451 4.4.0 Primary target IP address responded with 421 4.2… unable to connect. For messages hanging in the queue.

On NSLOOKUP resolve distant domains fine, Server has a firewall rule allowing port 25, running Exchange diagnostics I do get ‘Remote server failed the mail acceptance test when trying to open the remote socket’, ‘remote socket not available’.

Install went fine with no issues, restarted Transport services several times, cleared the queue several times and resent messages only to see them hang.

Use MX record is checked, use ‘external dns’ is checked, etc.

So where do I look at next?
0
xmouser
Asked:
xmouser
  • 6
  • 4
1 Solution
 
dexITCommented:
Sounds like an issue with the send connector.

Start by performing a test at  https://testconnectivity.microsoft.com/ and share results please.
0
 
xmouserAuthor Commented:
I can't get to this as the business model does not allow access to the internet. I have many 'internal' domains available just not the internet.
0
 
dexITCommented:
You might have just answered part of the question then. Exchange requires HTTP/HTTPS, Port 25/587 to pass through. If you are unable, by policy, to do this, this could partially be why you're sustaining problems. Do you have any other exchange servers/domains?
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
xmouserAuthor Commented:
Under server configuration > Hub transport > send connector:

General:
Specify the FQDN this ... > Exchange server listed

Address Space:
'*'
Network:
Use DNS is checked. I also have Use external DNS lookup checked

Source Server:
The exchange server is listed.
0
 
xmouserAuthor Commented:
dexIT

Other domains and servers available. I don't have access to them.
0
 
xmouserAuthor Commented:
Yes, port 25 was a thought but I do have a server firewall rule for that. I've sent a message to networking about port 25 to see if it's blocked.
0
 
xmouserAuthor Commented:
I am seeing this as well:

'A matching connector cannot be found to route the external recipient'
0
 
dexITCommented:
Definitely an issue with the send connector.

Either it's been modified, where you'll have to delete and re-create  using * in the address space.

Follow these steps:
http://technet.microsoft.com/en-us/library/aa997285.aspx
0
 
dexITCommented:
I just realized I provided the wrong link above and fixed it. You will need to create/re-create the send connector and use the above link as a reference to properly configure it.
0
 
xmouserAuthor Commented:
Got it thanks. I think I got it figured out but it'll be Tuesday until I can confirm.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now