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

Configuring Exchange for Fortigate 40c firewall with dual internet connections

Hello Experts!

We have a fortigate 40c firewall connected to Charter Business (WAN1) and TDS (WAN2) ISP's. While we purchased the TDS for a backup connection, it seems silly to pay for it and have it sit idle... I was hoping to configure it for load balanced Internet connection.

I set up the balancing in the firewall based on fortigate documentation and our email stopped sending. I assumed it would use the policies created for WAN1 and use that path for sending emails, but it looks like I assumed incorrectly.

Do any of you know how I can keep both connections weighted equally and either give mail both routing options or force mail to only use WAN1 for it's path?

Thank you for your help!!!

Nance
0
NanceS
Asked:
NanceS
  • 4
  • 2
1 Solution
 
jerseysamCommented:
Could be that you need to change your MX records to include the external IP of the other WAN?
0
 
NanceSAuthor Commented:
So, would I copy the MX info in our DNS server as the same name but the new ip address? Would that work for SMTP? We could receive mail with both internet connections enabled, but sending was backlogged. This surprised me because I figured the policy in the firewall would give it the correct path.

Thanks!

Nance
0
 
jerseysamCommented:
I may be barking up the wrong tree.

Just thinking that I used to use a dray trek dual wan router and our mx records only listed 1 IP. I pushed all mail through this 1 WAN. If that wan failed or I needed to use the secondary line then I would need to change my MX records to the other IP.

This may not be the case with you but just a thought. Maybe mail out is not going as the IP it is coming from is not recognised as correct. This is presuming of course that all ports etc are opened accordingly etc

Some mx records allow you to enter multiple IP info as secondary.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
NanceSAuthor Commented:
I may not be sharing enough either...

Here's the whole scenario.

I had both internet connects enabled. When distance was 10 on Wan1 and 20 on Wan2 all worked well, but Wan2 sat idle... so I thought I'd try to load balance the internet connect. I set both distances to 10  and gave them a spill over measure... which worked amazingly for internet and phones... but not so much for sending mail. All outbound mail backed up in the queue until I set the back up as secondary (unused) I did call TDS that morning and had reverse dns set up to avoid being blacklisted and they assured me it was for failover only.. I called back and had them cancel it... to no change, still couldn't send mail. It wasn't until we set TDS to backup only that mail started sending again and cleared the queue.

Nance
0
 
Craig BeckCommented:
Don't touch your MX records for this.  MX records only dictate incoming mail routing.

In the Fortigate config you should be able to use source-based load-balancing.  This will allow you to determine which link the mail server sends on.  This will be determined via NAT rules.
0
 
NanceSAuthor Commented:
Thanks... I'll take a look at source based load balancing... I had all but given up on it working...
0
 
NanceSAuthor Commented:
After much research - our fortigate is a 40c and doesn't support the routing that is needed to force our exchange traffic to only flow on WAN1... due to this we are unable to load balance our two internet connections and have the smaller pipe designated solely as a backup.

Thank you for all the efforts!

Nance
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

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