Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


MSExchange SMTP Receive Connectors

Posted on 2009-07-02
Medium Priority
Last Modified: 2012-05-07
We are running SBS 2008 (Exchange 2007) we have 2 SMTP Receive connectors one hosting our mail eg (not our real domain name) and a second receive connector which is a relay connection eg  When we restart our server for whatever reason, we intermittently have the second relay connection start as our primary smtp receive connector.  In order to get things working as expected we restart all exchange services and the correct one starts as the primary connector.  

While this is very intermittant - probably because it is a 50/50 chance of the wrong connector starting first - we previously had 2 other connectors - the Windows SBS Fax Sharepoint Receive and the Windows SBS Internet Receive and we are looking at re-instating at least 1 of these two which would increase the chance of the incorrect connector starting up.  

Question by:trimblenet
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
  • 3
  • 2
LVL 37

Expert Comment

by:Jamie McKillop
ID: 24787911

I'm not sure you have your receive connectors configured. There is no such thing as a "primary connector". Each connector needs to be running on a different port or IP. You can't have two connectors listening on the same port on the same IP. Are you using multiple IPs? If so, you probably have both connectors set to use "All available IP addresses". Change this so that the IP associated with the connector is specified.


Author Comment

ID: 24790599
we are using the same ip for our external connectors - one connector is using port 3325 the other port 25, the other connector is the internal connector servername.domainname.local

so we have port 25 port 3325
server.domain.local port 25 (i believe)

last night for example after we rebooted the server when telnetting to on port 25 we would always be welcomed with the header server.domain.local and emails would bounce back with a relay denied message as the mail was expecting to reach and was receiving a response from server.domain.local

hope this helps
LVL 37

Accepted Solution

Jamie McKillop earned 1500 total points
ID: 24790649
That's your problem. You have two connectors on the same port and same IP. You either need another IP or you need to change the port used by server.domain.local. Since this is SBS, I assume it is your only Exchange server, so changing the port won't create any problems.


Author Comment

ID: 24791762
Hi JJ, Thanks for the response.  I have never seen this issue on othersites.  So your suggesting we shouldn't have any problems by changing the port for the internal connector to say 4425?

LVL 37

Expert Comment

by:Jamie McKillop
ID: 24793351
You can change the port to any port than isn't currently used by the server.


Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
New style of hardware planning for Microsoft Exchange server.
To show how to create a transport rule 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 Mail Flow >> Rules tab.:  To cr…
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

715 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