Mulit-homing MS_EXCHANGE

[Sanguine]

I need to put our Exchange Server on two LANs so that when one service provider goes down eg BT Opneworld, the Exchange should still be able to take mail from the second ISP, in our case ZEN. So, our first MX record points to one of our public IP addresses and the second record to another - each respective LAN firewall points port 25 to the same internal server system.
Multi-homing an ordinary NT4 box is no problem but Exchange 5.5/NT4 doesn't seem to allow me to appoint which NIC to look at and even so, only looks at one of the two NICs.
What do I need to do, BIND order or something to make this alternate route work?

 

[Frankenherder]

Why do you want to use multihomed?

if you are using NAT just have each firewall's External IP (wich should be the same as the MX record) route SMTP to you internal IP of your mail server. That way if one firewall or ISP goes down the other will continue to work.

Matt

 

[Sanguine]

Hi Frank! As you may see from my original question, each firewall uses a different external IP address and I have pointed each firewall port 25 at the Exchange server already.
The problem remains that I am using two NICs because each firewall is on a physically separate LAN - and Exchange doesn't seem to know which LAN to listen to. Perhaps there is some way of binding the two NICs for Exchange to listen to both LANs.

 

[garyoh]

Sanguine:
I have a similar situation. Have you gotten this resolved? I want to setup a second nic to keep email flowing when I switch ISP's. Basically, I want a week of dual ISP connections so I don't lose any emails once the DNS records are changed. You scenario is exactly what I wanted to do but have not begun yet. What did you do to resolve? Anything? If I find a solution, I'll surely send it to you.

 

[pctekk]

garyoh

did u find a solution yet ??

 

[Sanguine]

garyoh...
I've been all quiet because I went away! Now I'm back, I'm still facing the same problem... did you have any luck?
...sanguine