RE: re : re RE: SSL High Port Publishing Issue
- From: "Thomas W Shinder" <tshinder@xxxxxxxxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 17 Sep 2003 18:33:12 -0500
Hi Steve,
In the future, if you want to allow non-standard SSL port connections
via the Web Proxy service for the Web Proxy client, then configure
additional tunnel port ranges. Jim has a script that will do the heavy
lifting for you.
HTH,
Tom
Thomas W Shinder
www.isaserver.org/shinder
ISA Server and Beyond: http://tinyurl.com/1jq1
Configuring ISA Server: http://tinyurl.com/1llp
-----Original Message-----
From: Craft, Steve [mailto:SCraft@xxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, September 17, 2003 8:56 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: re : re RE: SSL High Port Publishing
Issue
http://www.ISAserver.org
I solved the problem. It turns out that my *client* was behind
an ISA server, and it was set as the web proxy for the client, and it
was munging the IP/port. Not using the web proxy in IE (or using
Netscrape) to go direct to the HTTPS high-port site works fine.
Other related posts:
