Re: Tri homed network and accessing the corporate n etwork

From: "SNELL,BEN (HP-UnitedKingdom,ex1)" <ben_snell@xxxxxx>
To: "'[ISAserver.org Discussion List]'" <isalist@xxxxxxxxxxxxx>
Date: Tue, 28 May 2002 12:25:01 +0100

OK - so it's as simple as making sure that the SQL Server is a SNAT client
(default gateway = ISA Server's Corporate IP) and setting up the rules to
allow inbound and outbound access over port 1433. The web server can then be
published using Web Publishing.
 
One security implication is obviously there is a single point of failure.
Are there any others? I'd like to use a trusted connection if possible - can
this be done? 
 
Any answers would be very much appreciated.
 
Thanks
Ben
-----Original Message-----
From: Lloyd@xxxxxxxxxxx [mailto:Lloyd@xxxxxxxxxxx]
Sent: Tuesday, May 28, 2002 12:06 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: Tri homed network and accessing the corporate network


http://www.ISAserver.org 
I have done this exact thing in a lab setting but not in a production
environment. With the web server in the perimeter and the database server on
the private LAN you have to use ISA's publishing rules. Make sure you have a
protocol definition (ex: MS SQL TCP 1433 inbound) for your database server.
With ISA's publishing rules you can publish the database server just to your
Web server on the perimeter network. 
good luck! 
LA ------------------------------------------------------ You are currently
subscribed to this ISAserver.org Discussion List as: ben_snell@xxxxxx To
unsubscribe send a blank email to $subst('Email.Unsub')
<mailto:$subst('Email.Unsub')>

Re: Tri homed network and accessing the corporate n etwork

Other related posts: