Exchange Server Forums

Configuration Help

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Installation >> Configuration Help

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Configuration Help - 17.Sep.2008 12:32:44 PM

airwin_ca

Posts: 4
Joined: 17.Sep.2008
Status: offline

We have two internet connections a primary and a secondary. I would like to move all outbound email to the secondary connection. Both connections reside on the same network but will act as different gateways. Our primary is Firewall1 at 10.10.10.1, Our secondary is Firewall2 at 10.10.10.2. Is this possible and how hard is it to setup. We have a single Exchange Server 2003 standard edition.

Thanks

Andrew

Post #: 1

Featured Links*

RE: Configuration Help - 17.Sep.2008 12:47:22 PM

mark@mvps.org

Posts: 3785
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline

nothing to do with Exchange.
One solution is to change the default gateway of your Exchange server from .1 to .2

_____________________________

Mark Arnold (Exchange MVP)
List Moderator

(in reply to airwin_ca)

Post #: 2

RE: Configuration Help - 17.Sep.2008 1:10:10 PM

airwin_ca

Posts: 4
Joined: 17.Sep.2008
Status: offline

would that effect inbound email? Sorry I'm new to managing a exchange server.

Andrew

(in reply to mark@mvps.org)

Post #: 3

RE: Configuration Help - 17.Sep.2008 1:15:05 PM

mark@mvps.org

Posts: 3785
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline

The problem here is that you're intertwining Exchange and networking. Frankly you need to get someone who knows networking involved in this so he can sort your routing/firewall infrastructure out properly.
Ideally you won't have multiple gateways, you'll have one gateway and the devices will control outbound traffic.
If I were you I wouldn't be changing anything on Exchange but I would be configuring my routers to do the right thing.

_____________________________

Mark Arnold (Exchange MVP)
List Moderator

(in reply to airwin_ca)

Post #: 4

RE: Configuration Help - 17.Sep.2008 1:23:40 PM

airwin_ca

Posts: 4
Joined: 17.Sep.2008
Status: offline

Thanks for the info.

(in reply to mark@mvps.org)

Post #: 5

RE: Configuration Help - 19.Sep.2008 3:04:02 PM

StuntmanMike

Posts: 2
Joined: 19.Sep.2008
Status: offline

quote:

ORIGINAL: airwin_ca

would that effect inbound email? Sorry I'm new to managing a exchange server.

Andrew

No, as a matter of fact the setup is very simple.

SM

(in reply to airwin_ca)

Post #: 6

RE: Configuration Help - 22.Sep.2008 10:43:47 AM

airwin_ca

Posts: 4
Joined: 17.Sep.2008
Status: offline

Care to share the how to with me please

(in reply to StuntmanMike)

Post #: 7

RE: Configuration Help - 22.Sep.2008 12:01:10 PM

uemurad

Posts: 5485
Joined: 7.Jan.2004
From: California, USA
Status: offline

As Mark said, what you have brought up is not an Exchange routing issue, but is instead a network routing issue. You can either have Exchange perform the DNS search and therefore attempt to send out the message to the outside world, or you can have Exchange send all the messages to another SMTP system that will forward the messages, or you can configure it to selective do either or both. Exchange does not choose the networking route, but instead follows the implied and static routes defined in your environment. Those routes can be defined in Windows, on network switches (OSI layer-3 and above), on routers, or on firewalls.

You can control the messages to a certain extent with the use of SMTP connectors, but that really isn't ideal. You are talking about network redundancy, and therefore should be looking to implement it at the network-layer of your environment. Don't bury the details in Exchange, because it will be difficult to troubleshoot when messages start traveling over an unexpected path.

So, can you do it? Yes, but I don't recommend doing it that way.

quote:

Will it affect inbound mail?

It could, but not as far as Exchange is concerned. Once a message reaches any Exchange server in an Organization, it's configured routing will take over. Before a message gets to the Exchange Org, it's all up to your network routing. Again, that means routers, firewalls, and possibly switches. In more complex environments that could include VPN tunnels and their associated routers, firewalls, and switches.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to airwin_ca)

Post #: 8