MrWizard   0 pts.  |   Jan 4 2005  8:16PM GMT

First, to answer your question…yes you’ll have to open those ports on your firewall.

FYI,
Be very careful. Very few legitimate websites use ports that are abnormal (standard ports: http-80, https-443).

dantebrown   0 pts.  |   Jan 5 2005  5:23PM GMT

Adam,

I’m going to make two assumptions:
1. It’s a single server solution.
2. You are viewing the website from the internal network.(http://servername)

Since http works, the problem seems to deal with SSL or the HTTPS port.

A few things to check:

1. The web publishing rule for the site and the certificate installed on the server. Check the certificate (validation, site name, etc.)

2. Make sure the port is correctly configured in IIS.

One thing i’ve seen with ISA and websites, is that I would have to include them in my proxy exclusion list in IE. (both HTTP and HTTPS).

If viewing the site from external network:
1. Still check the cert and the IIS settings.
2. Check web publishing rule for the site. Make sure the cert installed on IIS, and ISA is configured correctly on the server. (name, validatino etc.) Check the port the publishing rule is configured for.
3. Check the configuraion of the the web listner for the website.
4. Check your resolution method (DNS).

Let me know if that helps.

Dante

mraslan   0 pts.  |   Jan 6 2005  12:32AM GMT

I believe that the web server is on the internet not on your network, correct me if i’m wrong.

If the above is true, does your ISA server allows certain protocols to users? or does it allow all traffic from internal users to the internet?

from what you said, i beleive that your ISA server is allowing some protocols to users. If so then you will have to add a new protocol definition with the new port 8443, and then add a new protocol rule that allows your users to use this protocol to access external web servers. I’m assuming that you are using ISA 2000, if you are using ISA 2004, the process is similar but from different places.

If its not like that please describe more your network setup, you don’t have to say the exact setup or IP’s, and also it will be good if you describe the error returned to the client.

dcashman   0 pts.  |   Jan 6 2005  9:33AM GMT

check out <a href="http://isaserver.org" title="http://isaserver. " target="_blank">isaserver.org</a> and <a href="http://www.isatools.org" title="http://www.isatools. " target="_blank">www.isatools.org</a>. I was having the same problem and found a fix from Jim Harrison. Save this code as vbs and run.

set isa=CreateObject(”FPC.Root”)
set tprange=isa.Arrays.GetContainingArray.ArrayPolicy.WebProxy.TunnelPortRanges
set tmp=tprange.AddRange(”SSL 8443″, 8443, 8443)
tprange.Save

habiru   0 pts.  |   Jan 7 2005  1:47PM GMT

All good advice. But if this does not fix it, try this. Contact your provider to make sure that the server is not caching. Had this very same problem last year from a client. ISP had started using the caching option on the server and in doing so, he could not log on to authenticate with his RSA keygen.

mraslan   0 pts.  |   Jan 7 2005  11:36PM GMT

Just want to add that the post by dcashman is right, this is a known issue with ISA if you are using HTTPS.

The solution i posted earlier will not be complete in your case, if the solution posted by dcashman didn’t work for any reason, then just tell me is your clients browser are configured to use ISA as a proxy or not, and tell me how is the HTTP Redirectory Filter is configured, you will find it on the ISA Server, ISA Management Console, Externsions, Applicaiton Filters, HTTP Redirector, By default it should be “Redirect to the local web proxy service”. I need to know how this and the browser is configured in order to give you the correct solution.

Humboldt421   10 pts.  |   Nov 2 2009  9:18PM GMT

The port in question is likely a typo, the port was changed from 80 to 443 but someone forgot to press enough backspaces. I would contact that systems admin and explain your situation and ask if that was done with purpose or accidental.