RE: Dual homed Exchange 2003
- From: "Art Henning" <AHenning@xxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Thu, 12 Aug 2004 13:46:37 -0500
Greeting Mr Smith, Thank you for your prompt response. I assume you a
referring to modifying the routing table on the Server. What a simple
solution. Don't know why that did not occur to me. Guess trying to make
a mountain of a molehill.
Best regards,
Art Henning
-----Original Message-----
From: Michael B. Smith [mailto:michael@xxxxxxxxxx]
Sent: Thursday, August 12, 2004 1:43 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Dual homed Exchange 2003
http://www.MSExchange.org/
You add manual routes for the private subnets.
It's exactly what I do on all my mail servers.
-----Original Message-----
From: Art Henning [mailto:ahenning@xxxxxxxxxxx]
Sent: Thursday, August 12, 2004 3:34 PM
To: [ExchangeList]
Subject: [exchangelist] Dual homed Exchange 2003
http://www.MSExchange.org/
Exchange 2003 Enterprise installed on Server 2003. Latest SP's etc. Dual
homed. One nic (Nic1) on a DMZ ip mapped to the DNS MX record for our
public domain. The other nic (Nic2) on the private LAN (several subnets)
servicing our Windows 2000 Active Directory and providing our Exchange
Server services. Default SMTP Virtual Server configured for Nic2 ip and
Internet SMTP Virtual Server configure for Nic1 ip. Can properly service
incoming SMTP, POP3, OWA, IMAP requests thru the MX record ip. The
default gateway for the Exchange Server is the gateway for Nic2. This
allows other private subnets to connect to the Exchange Server services.
The Exchange Server sends all email from the default gateway nic (Nic2)
which is delivered thru the firewall ip address (not the MX record ip
address). The problem is some receiving email servers cannot resolve the
DNS entry for our Exchange Server because it is identified coming from
our firewall ip and not the MX record. The result is that some outgoing
email is rejected as either spam or relayed email. If I set the default
gateway to the Nic1 (the DMZ nic), all email is sent out with the MX
record ip address and the problem is no longer. But this introduces the
problem of not being able to route our Exchange Server services to the
other private subnets. Would like suggestions on how to crack this
catch-22 issue. Many thanks!
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading
Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
michael@xxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading
Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
ahenning@xxxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
Other related posts:
