RE: SSl on port 443 ?

found it!

it's definetely Websense.

Disabling it or mapping the url in the "Not filtered url" everything works.

The point is: why ISA2004 returns the error for unauthorized request for ssl
tunneling on a different port than 443???



--
Stef


"Stef" wrote:

thanks
:-(
still no luck also with your hint.

how about this?
http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/client_ssl.mspx

t
--
Stef


"Wilfred" wrote:

Hi,
I had a similar situation with an https site. If the users that cannot
access the site are containe in a firewall rule that allows them only
particular protocols like http or https (for example), then you might want to
create a computer set with the ip address of the https site you want to
reach. this is because even if you specify the whole site in a url set, the
rule only will apply to http traffic. Try creating the computer set by ip
address an apply to re firewall rule for the clients.

this is the ip address of the site 199.207.250.68

good luck
"Stef" wrote:

And again:

with isa2000 we do not have this issue: the site works for all users.


--
Stef


"Stef" wrote:

Hi everyone,

brief description of the environment: Win2003Std no sp1, ISA2004Ent sp2
single array, configured as single network adapter, Websense 5.52 integration.

when users try lo connect to this external link: https://kpmgvirtualihr.com
the following message is displayed:

Error Code: 502 Proxy Error. The specified Secure Sockets Layer (SSL) port
is not allowed. ISA Server is not configured to allow SSL requests from this
port. Most Web browsers use port 443 for SSL requests. (12204)


All seems related to the MS KB283284, but absolutely not. The web site
respond correctly on port 443 and that port is opened on ISA as for other
sites. Only me and a few users/clients (apparently isa2004 administrators
defined) are able to connect to this site

Thanks in advance.

Regards



--
Stef
.

Relevant Pages

  • Re: 502 Proxy Error msg
    ... Jim Harrison (ISA SE) ... People can get to banking sites and that's going to https ... port is not allowed. ... Most Web browsers uses port 443 for SSL requests. ...
    (microsoft.public.isa.configuration)
  • RE: SSl on port 443 ?
    ... still no luck also with your hint. ... I had a similar situation with an https site. ... The specified Secure Sockets Layer port ... Most Web browsers use port 443 for SSL requests. ...
    (microsoft.public.isa)
  • Re: trendmicro isa and https on port 4343
    ... I don't think the tunnel port range is required for internal https access, ... In proxy settings, bypass proxy for local addresses; ... Yes, there are a few more questions to answer, but the defaults are fine *except* you elect not to require https. ... Most Web browsers use port 443 for SSL requests. ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW with no https
    ... Speaking about MS IIS as a web server, in HTTP, one can run multiple ... "host headers" and run all sites on the default port 80. ... to workstations, runs on port 4125, which is dynamically opened by the SBS ... HTTP why cant you do the same with HTTPS? ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW with no https
    ... Change your ports for Kerio, using the instructions he provided, or get a different static IP for RWW ... Windows Small Business Server 2008 Unleashed ... running Https, I still have http open and free to use where ever. ... >> port but going to port 8080. ...
    (microsoft.public.windows.server.sbs)