isa2004 blocking tunnelled ssl

Not sure, but this might help:
(From ISAServer.org)
You can download the .NET application, ISATpre.zip file at http://www.isatools.org/ISAtrpe.zip (written by Steven Soekrasno) from the www.isatools.org site and install the application on the ISA firewall. This application provides an easy to use graphical interface that allows you to extend the SSL tunnel port range. Just enter the first port and last port you want to include in the SSL tunnel port range in the LowPort and HighPort text boxes and click the Add Tunnel Range button. Then click the Refresh button to see the new SSL tunnel port range in the list.
Note that if you have unbound the Web Proxy filter from the HTTP protocol, then Firewall and SecureNAT client connections made through the ISA firewall will not be redirected to the Web Proxy Filter. In this case, you can create a Protocol Definition for the alternate SSL port and then create an Access Rule allowing outbound access to that protocol.

does it use 443 port for ssl is it another port?

can you get the session state.

isa console logs and reporting, logging tab.

what does it say if you capture the relevant traffic?

thanks for the input. currently the isa server is configured as an enterprise, so adding a secure web publsing i have not been able to do. i have not been able to find the spot that allows you to check the box that addresses web presentation.  what i see when monitoring the firewall, is that the application uses http80 to start the connect, then attempts to do tunnelled ssl, and is at that point the isa server shows the ssl tunnel connection failed. i am hesistent to download a 3rd party program to configure the isa server. i do appreciate the suggestion however

how is the application published as server publishing or web publishing rule?

the application is a washington state online testing app. while monitoring isa traffic filtered on the ip# of the test pc, i see a connection to the external ip#, port 443 protocol=ssl-tunnel; action= failed connection attempt; rule = enterprise name-http; so. it appears that ssl tunnel protocol is not enabled on the entrprise http rule; i have been thru all the tabs on the properties of the enterprise http rule; action=allow; protocol=all outbound; from= local;allnetworks;private iprange; to=external;local;all networks;private iprange; condtion=all users

Are you hosting or accessing this application?

From what I understand you are accessing it?

The app is a client piece that accesses servers on the net. It has a test tab which goes out and verifies connectivity that is how I can trace traffic on ISA server

Are you using a proxy server on the ISA?

Pcs connect to a content filter the content filter connects to ISA. My testing has been pc to ISA. Currently the testing app is working there was a setting that affected ssl that I was able to adjust. I am still interested in understanding why ssl tunnel protocol shows failed connection. Thanks for your time

There are several possibilities why it wouldn't work, maybe rule order. But the rule that denied it had "all protocols defined", so that is a dead end.

If you are using a web proxy, the client did not have secure proxy defined?

What did you change in SSL, maybe that is why it didn't work?

thanks again for working wtih me on this...the app had a setting that says, use secure channel, unchecked that, the app stopped attemtping to tunnel ssl in the http 80 traffic and passed all it's tests. on the pc itself, we do not proxy ssl at all, nothing is entered in the connections settings option; this standalone app, picks up it's settings from ie; however you can manually override them; with the use secure option checked, this app will not function thru isa; isa denies with the ssl tunnel error..we did have the dc that hosted the isa enterprise config info, so we had to rebuild it from ground up, from memory; there is a good possiblity that we missed something...however as you pointed out...we are not blocking any protocols...we have only 1 rule in place; why does it not allow ssl tunnelling? everything have read talks about publsihsing a secure web app and enabling ssl tunneling, which is not what i think i need to do.  thanks again..

Will do Tuesday and let you know. Thanks again

simonlimon thanks for the help.  the test of the google site showed a blocked ssl tunnel on the isa server.  I appreciate all your help.  i will be building a new isa server with a newer version.  I found a work around to make the app work. thanks again.