Solved

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

Posted on 2013-06-24
1
470 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

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

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

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
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…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

809 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