Welcome to ISAserver.org

web proxy - filtering

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Web Proxy] >> Web Proxy Client >> web proxy - filtering

Page: [1]

Message

<< Older Topic Newer Topic >>

web proxy - filtering - 21.Nov.2007 3:25:12 PM

samw

Posts: 4
Joined: 21.Nov.2007
Status: offline

We have a Celestix ISA 2006 Server with Websense.

If a browser is configured for direct connection then no filtering takes place. This is the case even when the Firewall Client is configured.

We have routed all internet traffic through the ISA at the router level so I know the traffic is hitting the ISA box.

Is there a way to make all web traffic going through the ISA server filtered regardless of the client settings?

Post #: 1

Featured Links*

RE: web proxy - filtering - 2.Dec.2007 8:55:09 PM

nwigmore

Posts: 16
Joined: 28.Nov.2007
Status: offline

Can you be more specific of what you are trying to achieve here? Which filters are we talking about?

(in reply to samw)

Post #: 2

RE: web proxy - filtering - 3.Dec.2007 1:02:59 AM

ferrix

Posts: 363
Joined: 16.Mar.2005
Status: offline

Did you accidentally remove the Web Proxy Filter from the http protocol properties? Sounds like it.

In the isa monitoring, what proto is listed for the traffic passing? If it's not http but something else, then maybe you have a custom :80 protocol and a rule matching it?

(in reply to nwigmore)

Post #: 3

RE: web proxy - filtering - 3.Dec.2007 2:37:30 PM

samw

Posts: 4
Joined: 21.Nov.2007
Status: offline

quote:

ORIGINAL: nwigmore

Can you be more specific of what you are trying to achieve here? Which filters are we talking about?

Websense is not logging or blocking any web useage if the web browser's proxy settings are not configured, even with the ISA client installed.

quote:

ORIGINAL: ferrix
Did you accidentally remove the Web Proxy Filter from the http protocol properties? Sounds like it.

In the isa monitoring, what proto is listed for the traffic passing? If it's not http but something else, then maybe you have a custom :80 protocol and a rule matching it?

Where do I go to verify this? I do not recall deleting any filters.
I see a Web Proxy filter listed in the Application Filters, and I see the Websense filter listed in the Web filters.

(in reply to ferrix)

Post #: 4

RE: web proxy - filtering - 3.Dec.2007 2:41:04 PM

ferrix

Posts: 363
Joined: 16.Mar.2005
Status: offline

In the right pane Toolbox you can edit the properties of protocols. For http make sure Web Proxy Filter is selected.

And as I mentioned, look in the real time logging to see what protocol is cited for your problem traffic. You want to make sure it's http and not some custom thing.

(in reply to samw)

Post #: 5

RE: web proxy - filtering - 3.Dec.2007 2:56:19 PM

samw

Posts: 4
Joined: 21.Nov.2007
Status: offline

Ok, I could see my traffic in the real time logging, but not in websense logging at the same time.

I saw mostly port 80 traffic, which is what I expected as I just went to a few news sites.

(in reply to ferrix)

Post #: 6

RE: web proxy - filtering - 3.Dec.2007 2:58:53 PM

ferrix

Posts: 363
Joined: 16.Mar.2005
Status: offline

All the stuff I said still applies. Port number is not the same thing as protocol.

(in reply to samw)

Post #: 7

RE: web proxy - filtering - 3.Dec.2007 5:02:54 PM

samw

Posts: 4
Joined: 21.Nov.2007
Status: offline

I see now what you were talking about. That seems to work it now blocks.
Unfortunatley I get this "The requested URL /cgi-bin/blockpage.cgi was not found on this server." instead of getting a Websense page.

It looks like I can only choose from applications filters and not web filters, but this is still better than nothing.

(in reply to ferrix)

Post #: 8

RE: web proxy - filtering - 3.Dec.2007 5:49:31 PM

ferrix

Posts: 363
Joined: 16.Mar.2005
Status: offline

No that's correct. The "web proxy filter" is an app filter, and it is the thing you have to have selected for the protocol. That is the thing that controls all the web filters and makes sure they run.

For your new error, Sounds like the block URL is wrong, or websense isn't listening at the right place maybe. Probably not too hard to track down the next step.

(in reply to samw)

Post #: 9

RE: web proxy - filtering - 5.Dec.2007 3:14:09 PM

abqtech

Posts: 216
Joined: 9.Mar.2004
Status: offline

In regards to the following message:
The requested URL /cgi-bin/blockpage.cgi was not found on this server

What server is the Websense Filtering service install on?

If it's installed on the same server as the ISA Server, you'll need to ensure a rule exists that allows clients to successfully connect to the Websense Filtering service, the default port that the Websense Filtering Service serves HTTP traffic from is TCP 15871 Outbound.

(in reply to ferrix)

Post #: 10

RE: web proxy - filtering - 5.Dec.2007 3:17:01 PM