• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

Receive connector issue

I've read here and other places that it is important to use the FrontendTransport role when creating an Exchange 2013 Receive Connector for devices that will use the Exchange server for relay.  If you don't use a FrontendTransport connector you will regularly have to stop and restart the Transport service.  

My problem is when I create Receive Connector using the FrontendTransport role using port 25 (or any other port) I can't establish a connection to the server using that port.  I'm using "telnet server 25" from another machine on the inside network for my testing.

Even my Internet Receive connector was created with the Hub Transport rule.

What must I do to get a FrontendTransport Receive connector to actually listen on port 25?


1 Solution
Muralidharan RAssociate ConsultantCommented:
Whether the application installed server ip/device ip has been provided in the receive connector?

Receive connector only listen connections from the mentioned ip's in receive connector.

If receive connector needs to receive emails from all the ip's, then you could select  All available IPV4 while creating.
labdunnAuthor Commented:
I didn't set it to all IP's but I did select the output address of the spam filter and all the relay devices on the network.  This seems to be working.  Thanks.

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

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

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