Exchange 2013 Connector

Posted on 2015-01-29
Last Modified: 2015-01-30
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
Question by:pomah1
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
LVL 17

Expert Comment

ID: 40578646

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?
LVL 12

Expert Comment

by:Md. Mojahid
ID: 40578993
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.


Accepted Solution

Henry Dawson earned 500 total points
ID: 40579550
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.

Author Comment

ID: 40580258
Yes that was actually IP address restriction on the connector itself.

Thank you

Expert Comment

by:Henry Dawson
ID: 40581146
You Welcome pomah1...
If you have any query in future, let me know....


Featured Post

[Webinar] How Hackers Steal Your Credentials

Do You Know How Hackers Steal Your Credentials? Join us and Skyport Systems to learn how hackers steal your credentials and why Active Directory must be secure to stop them. Thursday, July 13, 2017 10:00 A.M. PDT

Question has a verified solution.

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

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…

734 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