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?
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 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.
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.
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 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.