Valid scenario for ISA 2004 Site to Site Deployment?

Hello,

I need help identifying whether or not the following is a valid ISA 2004
site to site
deployment scenario before I installing ISA on my hosted server and make it
completly unavailable for remote login over RDP or VPN. Can someone provide
some guidance?

This should be the simplest of solution but it still eludes me after days of
configuration. I have a W2K3 corpnet domain and recently setup a W2K3
server with a
hosting provider where there is only one NIC which has the public ip
assigned
to it.

All I want to do is keep a VPN or IPSec (whatever it takes, even ISA 2004 if
need be) connection between our domain network and that hosted server alive
so that we can manage that server in the hosted environment using the same
GPO's and AD accounts. I have already added the hosted server to the
corpnet domain. It would be great if it would only dial on demand when a
request was made for that netbios or fqdn of the hosted server from the corp
net but I'd be content with an "always on" connection too if that's what it
takes.

On our corpnet we are using RRAS (for inbound VPN clients) and ISA 2004 on
the same box which has a NIC going to the DMZ and an internal NIC to our
corpnet.

Should I use ISA in this scenario or does the single public IP addressed NIC
rule out ISA 2004 in this case? Couldn't I add the MS Loopback adapter to
simulate a second NIC in this machine?

Thx,
Gaylen


.

Loading