Improve company productivity with a Business Account.Sign Up

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

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
0
pomah1
Asked:
pomah1
1 Solution
 
IvanSystem EngineerCommented:
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
 
Md. MojahidCommented:
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
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
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
 
pomah1Author Commented:
Yes that was actually IP address restriction on the connector itself.

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

Thanks
Henry
0
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.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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