Why does websense block everything

Your environment includes multiple Websense Filtering Service instances, and. You use the Quota or Confirm actions, password override, or account override. State Server tracks clients' quota, confirm, password override, and account override sessions to ensure that session time is allocated correctly across multiple Filtering Service instances see Policy Server, Filtering Service, and State Server.

After entering State Server connection details, click Check Status to verify the connection. Configure State Server connection information for each Policy Server instance in your deployment. Under Bandwidth Optimizer , enter the information needed to filter Internet usage based on available bandwidth.

For more information about enforcing bandwidth-based Internet access, see Using Bandwidth Optimizer to manage bandwidth. In Websense Web Security Gateway Anywhere environments, no bandwidth-based restrictions are enforced on requests passing through the hybrid service. To specify an Internet connection speed , do one of the following:. Enter the network speed in kilobits per second in the text field. Enter the default thresholds to use when bandwidth-based actions are enforced.

Note that when the thresholds are set, but no category or protocol filters include bandwidth-base actions, no bandwidth usage restriction occurs.

Network : When total network traffic reaches this percentage of total available bandwidth, start limiting access based on bandwidth, as configured in active filters. Protocol : When traffic for a specific protocol like HTTP or MSN Messenger reaches this percentage of total available bandwidth, start restricting access to that protocol, as configured in active filters. To enable this option, mark Include bandwidth data collected by Websense Content Gateway.

Leave these fields blank to use the default block message. If you have created custom block pages, and want to use those block pages for all protocols, you can also use the fields in this section blank see Customizing the block message. Custom block messages specified in the fields above are not applied to requests handled by the hybrid service. As a result, ACEInsight does not analyze password-protected content, and may return different results than Content Gateway.

The ACEInsight link does not appear on hybrid block pages. Filtering Service determines which setting is less restrictive at the filter level. In cases where a user might be assigned to multiple policies, one of which is enforcing a limited access filter, "less restrictive" may sometimes seem counterintuitive. When Use more restrictive blocking is OFF :. If the Block All category filter and a limited access filter could apply, the limited access filter is always considered less restrictive.

If any other category filter and a limited access filter could apply, the category filter is considered less restrictive. This means that even when the limited access filter permits the site and the category filter blocks the site, the site is blocked.

When Use more restrictive blocking is ON , a limited access filter is considered more restrictive than any category filter except Block All. The table below summarizes how the Use more restrictive blocking setting affects policy enforcement when multiple policies could apply:. Use more restrictive blocking OFF. Makes sense, although the AVC is a little beyond the scope in this particular project.

I would take a look at the iboss solution, it's more cost effective then websense and provides layer 7 visibility, application control, bandwidth shaping and SSL filtering without decryption.

PM me if you need more information. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.

Forcepoint 1, Followers Follow. Websense Web Security 4. BitTorrent Peer To Peer 0. Show all 5 tags.