We help IT Professionals succeed at work.

Exchange 2010 will not send messages

198 Views
Last Modified: 2014-09-15
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?
Comment
Watch Question

Commented:
Sounds like an issue with the send connector.

Start by performing a test at  https://testconnectivity.microsoft.com/ and share results please.

Author

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.

Commented:
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?

Author

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.

Author

Commented:
dexIT

Other domains and servers available. I don't have access to them.

Author

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.

Author

Commented:
I am seeing this as well:

'A matching connector cannot be found to route the external recipient'

Commented:
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
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Got it thanks. I think I got it figured out but it'll be Tuesday until I can confirm.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.