[isalist] Re: Configuration Advice for Multiple IP's
- From: "Andy Haigh" <ahaigh@xxxxxxxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Tue, 6 Feb 2007 02:18:43 +1100
I thought there was a problem with using forms based authentication for
OWA and then trying to use basic for Activesync and RPC over HTTP.
Are you using the procedure set out here?
http://www.isaserver.org/tutorials/2004pubowamobile.html
As the warning states it's not been stressed tested I didn't want to use
it in this case.
Thanks
Andy
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Steve Moffat
Sent: Monday, 5 February 2007 9:29 PM
To: ISA Mailing List
Subject: [isalist] Re: Configuration Advice for Multiple IP's
What's the issue? I build many ISA servers with only 1 IP address and
publish those services successfully on ISA 2004/ 2006.
S
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Andy Haigh
Sent: Monday, February 05, 2007 3:28 AM
To: ISA Mailing List
Subject: [isalist] Configuration Advice for Multiple IP's
Hi,
I am after some advice on the best way to configure ISA Server for what
I am trying to do. The scenario is:
Current
Windows 2003 SP1 (fully patched)
ISA Server 2004 SP2
Netgear ADSL Router with Packet Filter rules setup and port forwarding.
ADSL 1.5Mb/256kb service with Single Static IP Address, this is
basically a residential service.
Problems caused here is with allowing Forms based OWA, Activesync, RPC
over HTTP, VPN all through the single IP address. I know there was a
workaround published for this but I doubt it would be supported by MS.
The client is having a business grade SHDSL service installed with a /29
subnet with a Cisco 878 router as the interface.
We are aiming to use both services by adding a 3rd network card and
connect the new SHDSL service to it, so that web browsing traffic can
use the current ADSL link and the other services can use the SHDSL link.
Thereby we can create multiple listeners for the different access
requirements via the SHDSL link, though I have read that ISA2006 gets
round this problem.
I am also going to upgrade to ISA Server 2006, which I will do prior to
connecting up the new service. Allow that change to bed in prior to
implementing another!
Any advice or direction would be appreciated.
Thanks
Andy
Other related posts:
