Rick,
TR or Ethernet has absolutely no base definition which states that just
because I'm TR or Eth, I will or will not allow SSL through.
The issue is more likely something else either inside your Network, or in
the FW rulebase itself.
Do you use an internal proxy server ? Are your clients set to use proxy ? If
so, see if you get a difference if you set a proxy on the security proxy
option as well.
Try setting the clients to not use HTTP 1.1.
Check if you have a rule on the FW which allows HTTPS to go out from inside.
HTH,
Mike
> -----Original Message-----
> From: Rick Francis [SMTP:[EMAIL PROTECTED]]
> Sent: u ea?e 24 2000 2:26
> To: [EMAIL PROTECTED]
> Subject: [FW1] token ring, ethernet firewall
>
>
> os=solaris 2.5.1
> model=ultra2
> platform=firewall
> interior interface=token ring
> exterior interface=ethernet
>
> problem: https urls that use the secure type 'ssl' protocol cannot connect
> to a browser (whatever kind) from inside the token-ring network. on the
> other side of the firewall, they work fine (all the pages serve up, and
> the
> application (javascript) connect and work).
>
> solution:??
>
> your ideas are appreciated, rf.
>
>
>
> ==========================================================================
> ======
> To unsubscribe from this mailing list, please see the instructions at
> http://www.checkpoint.com/services/mailing.html
> ==========================================================================
> ======
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
