Error: Tunnel or SSL Forbidden, not an allowed port

Factual Questions
1

With some web pages I get the following error

(where XXX is a number) For example this link does it for me. I have been unable to find anything on the Net or Microsoft which explains what is the cause and the remedy. It looks like it is related to SSL but I have no problem generally with secure web pages. Any ideas?

2

I tried playing with my SSL and TSL settings, but nothing duplicated that error. If SSL was turned off completely, I got a page unavailable. What browser and OS are you using?

3

Sorry for not providing: WIN98SE, IE6

Where can I check SSL and TSL settings?

If I am interpreting the message correctly, SSL is trying to use a port which it is not allowed to use.

4

No one? It turns out I cannot access any secure sites. Cannot access my bank accounts or hotmail. I really need to resolve this. Where can I go for help?

5

Just a shot in the dark here, are you using a firewall or router that may be blocking some ports?

6

Sailor,

Have you looked into tools -> internet options advanced tab of IE. The scroll down to the bottom. There are a bunch of check boxes about versions of SSL and how to handle certificates. If I turn off the SSL stuff I cannot get to my banking sites.

7

sailor, my first guess would be that you are running a firewall (or connecting through an ISP or local network that is running a firewall) that has been configured to be a bit too aggressive.
Most firewalls are configured to block unexpected connections on incoming ports. Many can also be configured to limit connections on outgoing ports as well. For example, some companies use this technique to block their employees from surfing the web on company time or from sending email outside the company.

If you can reach http pages (port 80) but consistently fail on https (port 443), it may be due to a firewall that was configured to allow only http, email, and a few other services.

8

I am using ZoneAlarm but I was using it before and have not changed any settings. After much fumbling and tinkering I finally figured out the cause of the problem. A few days ago I was experimenting and set the connection to use a proxy server and later forgot to set it back. Now I have done it and everything is fine again.