I'd do as suggested, have the email dns pointing to the ISA server external, have a rule pushing all smtp to an internal smtp server which would then route it to the two different subnets and have the smtp server software sort out what goes where. We use Trend MSS to do this here and it allows us to put in AV and content rule filtering for all. The exchange boxes remain unchanged, the ISA server remains unchanged, the smtp server is separate from the whole solution so you can stop the flow at any time, if the subnets go down the mail is queued in the smtp server. It runs on a bag of spanners pc so no real money outlay there, and if you're dealing with a very small subnet rather than a enterprise lan then it doesn't cost much either. I dare say there are open source versions that do this just as well. -----Original Message----- From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] Sent: Saturday, November 05, 2005 1:29 AM To: [ISAserver.org Discussion List] Subject: [isalist] Two Internal Networks http://www.ISAserver.org In one of my previous posts I asked about running two internal networks through ISA 2004 Server. Now I have question. If both companyA and compayB have their own Exchange servers, how do I go about configuring ISA 2004 to push all mail incoming in on port 25 from mail.companyA.com to companyA, and all mail.companyB.com to companyB? Thanks Andrew ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: pnoble@xxxxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx