Solved

Three Exchange servers on the same network, diff domains, can't send mail

Posted on 2013-06-24
1
471 Views
Last Modified: 2013-07-07
We run a small IT shop.  In the building, we have our own exchange server, a hosted mail server for customer mail and a test mail server.

On the WAN side of the router, we have Comcast inbound with 15 static IPs and ATT inbound with 10 static IPs.  On the router, the Comcast is the primary with ATT as secondary.

Exchange1 has mail coming in from public IP xx.xx.xx.138 (Comcast)
Exchange2 has mail coming in from public IP xx.xx.xx.105 (ATT)
Exchange3 has mail coming in from public IP xx.xx.xx.109 (ATT)

Our problem was that mail coming in on 109 (ATT) was going out on 138 (Comcast) and that was giving us some grief for obvious reasons.  So, we wrote some policy rules in our firewall that forced traffic coming in on a public IP to go out on the same public IP.  However, when that rule is in place, Exchange3 cannot send mail to Exchange1.

Remove the rule and Exchange3 can send mail to Exchange1, but it goes out on the wrong public IP.  With the rule in place, everything is good, except Exchange3 cannot send mail to Exchange1.  We need to rule to make sure traffic leaves on the same IP it entered on.

Remember, all three Exchange servers are on the same 10.50.0.x network and we suspect that has something to do with it, but we are striking out homing in on the specific problem.

Ideas?

Thanks

Cliff
0
Comment
Question by:crp0499
1 Comment
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39274122
You should have the servers send email between themselves directly, rather than trying to use public records and going out and back in again through the same firewall.

There are two ways to do this.

1. Split DNS for the MX record.
This is where you use an additional entry in the local DNS server of each server for the MX record for the other two servers.
For example, if the MX record mail.example.com, then you create a zone for mail.example.com then create a blank entry with the local IP address in it.

2. Send/SMTP Connector for each domain.
This bypasses the MX record lookup. You create a Send Connector for the other two servers. Set them to use a smart host, entering it in the format of [192.168.1.1]. On the Address space, enter the domain the remote server is responsible for.

Of the two, option 2 is probably the easiest and keeps everything in Exchange.

Simon.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

Suggested Solutions

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this video we show how to create a mailbox database 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 Servers >> Data…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

830 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