Solved

Exchange 2013 Connector

Posted on 2015-01-29
6
255 Views
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
0
Comment
Question by:pomah1
6 Comments
 
LVL 16

Expert Comment

by:Ivan
ID: 40578646
Hi,

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

Expert Comment

by:Md. Mojahid
ID: 40578993
0
 
LVL 18

Expert Comment

by:suriyaehnop
ID: 40579057
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 
LVL 3

Accepted Solution

by:
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
RemoteIPRanges,AuthMechanism,PermissionGroups
 
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
networks).

 Hope this will work.
Thanks.
Henry
0
 
LVL 1

Author Comment

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

Thank you
0
 
LVL 3

Expert Comment

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

Thanks
Henry
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

895 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now