Exchange 2013 Connector

Hello Experts!

I created additional receive connector on port 587 on my Exchange 2013 SP1.
Trying to test it using telnet and this is what I'm having:

421 4.3.2 Service not available

Connection to host lost.  

I restarted Transports service but the situation remains the same.

Any ideas will be highly appreciated.

Thank you
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

IvanSystem EngineerCommented:

you are testing this internally or via internet? If via internet, have you reconfigured router to NAT this new port to Exchange and FW on it as well?
Md. MojahidCommented:
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Henry DawsonCommented:
Hi pomah1.....

 If the SMTP Receive protocol log on the Hub Transport server shows exactly the exact message:

>421 4.3.2 Service not available, closing transmission channel

>Connection to host lost.
That's good. At least it shows that the 421 status originated from
that HT role.
Is it safe to assume that the receive connector isn't configured to be
used as an anonymous SMTP relay? Or is it usable for that purpose?
Do you have multiple addresses in the remote-ip ranges on the
connector? What about authentication methods? Permissions?
get-receiveconnector <connectrorname>|fl
The fact that a simple telnet to port 25 from within the local site
works but a try from outside the AD site fails sure sounds like an IP
range restriction problem (assuming the two sites are in different

 Hope this will work.

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pomah1Author Commented:
Yes that was actually IP address restriction on the connector itself.

Thank you
Henry DawsonCommented:
You Welcome pomah1...
If you have any query in future, let me know....

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.