Software

Ask something
Discussion Locked

Exchange Routing

0 helpful
5 replies

by garrett1226

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an Exchange 5.5 server running 3 NICs: 2 internal, one with a hard connection to the Internet. I recently attempted to pull the Exchange server behind our ISA firewall and found that I was able to hit the OWA but my Exchange server was no longer forwarding mail to external recipients.

I changed the external address on the Exchange Server to a valid internal address and set the gateway to the ISA server. I also added the gateway to the other 2 NICs, effectively creating 3 internal cards. I am confident that the problem has to do with some Exchange setup, but, am unable to find info on the subject.

5 replies

by acattr

You can only have one default gateway on a server, otherwise it will get confuses as to which card to send thru.

If you have gateways to other networks add static routes for those networks.

by sfertic

I use a batch file called addroute.bat and run it on my Exchange Server any time I boot up and sometimes when IMS has 'lost its way'. It is basically a series of routes to my internet host and uses NT route statements, such as
route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1
(dest.) (mask) (gateway)

you can use command route PRINT to check your route, etc.

This discussion is closed to new replies.