Paul,
We did the exact same thing and it works.
We also use ESPG but with build 100 and not 101, not that I think this would
be the cause of the problem.
We use an additional URI TCP service port for a web site of 4080, so the
definition of that would be the same as your 8080, and then the rule is :
Who Any http-4080->Http-AntiVirus Accept
And it works.
What happens if you allow your rule without the ESPG scanner ? Do you still
get the error message ?
Mike
> -----Original Message-----
> From: Paul Daley [SMTP:[EMAIL PROTECTED]]
> Sent: � ������ 20 2000 12:15
> To: 'FW-1 Mailing List'
> Subject: [FW1] Scanning HTTP traffic to non-standard ports
>
>
> Hi,
>
> We're using Esafe Protect Gateway (ESPG) v2.1 build 101 as a CVP server
> hanging of FW-1 v4.0 SP6. ESPG scans all http traffic to port 80 on web
> servers, but I can't get it to scan traffic for non standard web server
> ports e.g. 8080.
>
> I create the new network service (TCP, type URI, port 8080), and place it
> in
> a rule with the ESPG resource, but when I try to connect I just get a
> 'connection refused' message straight back.
>
> Has anybody had this problem? Is it possible to scan http traffic to other
> ports?!?
>
> Thanks in advance,
>
> Paul.
>
>
> ==========================================================================
> ======
> 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
================================================================================
