Re: SSL Bridging & Tunnelling
- From: Rob <Rob@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 18 Apr 2008 01:43:00 -0700
Hi Jim,
Thanks for the reply.
q1 - This is now it was setup when I started here. I believe it was done
this way as originally just one site was using ssl and server publishing was
the easiest way to tunnel the ssl as opposed to bridging. To be honest I
don't know and it puzzled me.
q2 - the inbound web listener is configured individually per IP address (we
only have one address tho) and it *does* include the external IP address that
is used by the server publishing rule. I also noticed that 'Enable SSL
listeners' is *not* checked and no certificate is installed in the listener.
Should I then add the two imported certificates to the listener and confiure
to use SSL? This seems to be the right thing to do as per
http://www.microsoft.com/technet/archive/isa/2000/isafp1/piw.mspx?mfr=true
If so, thanks for pointing me in the direction of the listener
Rob
"Jim Harrison (ISA SE)" wrote:
Q1 - why are you using server publishing?
Q2 - have you checked that the inbound web listener does *not* include the
external IP used by the server publishing rule?
--
Jim Harrison (ISA SE)
.
- Follow-Ups:
- Re: SSL Bridging & Tunnelling
- From: Jim Harrison \(ISA SE\)
- Re: SSL Bridging & Tunnelling
- References:
- SSL Bridging & Tunnelling
- From: Rob
- Re: SSL Bridging & Tunnelling
- From: Jim Harrison \(ISA SE\)
- SSL Bridging & Tunnelling
- Prev by Date: How Do You Monitor a Published Server
- Next by Date: ISA Server and two internet connections
- Previous by thread: Re: SSL Bridging & Tunnelling
- Next by thread: Re: SSL Bridging & Tunnelling
- Index(es):
Relevant Pages
|