We help IT Professionals succeed at work.

Redundant mail path for Exchange 2003

dekkar
dekkar asked
on
Medium Priority
487 Views
Last Modified: 2015-01-05
Hi, we have 2 x offices connected via WAN. Each office has its own internet connection (separate to our WAN connection), but all email comes into office 1. The exchange server here then passes emails to the server in office 2.


The internet in office 1 was down all of yesterday, which made me think, is there a way we can redirect our email (ingoing / outgoing) through our office 2 server?

My understanding of it is we can add another SMTP connector to both servers with a higher cost, so exchange will fall back to the secondary connection if it needs to.

We only have 1 server per site, so I'm not sure about this front end / back end / bridgehead arrangement. But I am also curious to know if mail starts coming in through exchange server 2, will it know to automatically send mail up to exchange server 1? (as it has never had to do this before, usually its the other way around)


My thinking may be way out here, hope someone can help out!
Comment
Watch Question

Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Dave HoweSoftware and Hardware Engineer
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Expert of the Quarter 2009
Expert of the Year 2009
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Dave HoweSoftware and Hardware Engineer

Commented:
Mestha: yep, my point exactly. however, you can run a scheduled job to ping a remote IP, and shut down or start up the service as appropriate.
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
Start what service?
There is no way to control the routing in Exchange depending on whether something is down or not. You cannot stop SMTP because that will affect inter-server traffic as well.

If there are multiple sites then another way round it is to use a smart host that is under your control. That is what I do with a number of clients. Doesn't matter where the email originates from, it all leaves via a single host on the internet (actually a cluster of machines, but it is a single "host" name).

Simon.
Dave HoweSoftware and Hardware Engineer

Commented:
Mestha: on the script I use, it uses Set-SendConnector with the -enabled parameter to shut down the bridgehead unless it can successfully ping the upstream router at the ISP.
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
This is a question about Exchange 2003. So Powershell doesn't apply.

Simon.
Dave HoweSoftware and Hardware Engineer

Commented:
hmm. I didn't think exchange 2003 used smtp for links between servers, I thought it used rpc?
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
Inter-server traffic goes over SMTP. That has been the case since Exchange 2000. That is why you will see in all the migration questions the first thing that is asked is about SMTP connectivity.
Stop SMTP and no traffic will flow between them. Try it and see.

Simon.

Author

Commented:
Hi... Thanks for the replies... It does shed some light on inbound, which is pretty straight forward. Outbound however seems to be impossible to have redundancy?

Does Exch 2007 provide this? As it could be the excuse I'm looking for to upgrade!


Thanks,
Dekkar
Expert of the Quarter 2009
Expert of the Year 2009

Commented:
The behaviour hasn't changed. All it does is load balance, nothing else.

Simon.

Author

Commented:
working.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.