Puresight not blocking

[pgr]

Hi,

we have Puresight 2.0 installed on Wingate 6.1.0. Both have valid licenses.

I noticed users can access content that should be blocked. There are URLs that I try in Puresight's "Test URL" feature, and it says they should be blocked, however users can still access them.

Puresight is enabled in "WWW Proxy Server Properties / Plug-ins".

Is there anything I'm missing?

Thank you.

[Pascal]

Are your users going through the WWW proxy? (Either direct proxy or by turning on intercepts)

Also check that the users are enabled in the plugin. (You can en/disable users that are to be scanned)

[pgr]

Thanks for your help.

I checked the users and they are enabled in the plugin.

About "Are your users going through the WWW proxy? (Either direct proxy or by turning on intercepts)" I'm not sure what you mean, I have to ask you to be more specific as to where I should check... I don't know Wingate very well, not even network administration in general...

On the clients, they are configured for "direct access" to the Internet - I don't know if that's relevant.

Thanks.

[Pascal]

Either your clients need to have their browsers configured to use the WWW Proxy Service (Find it on the Services tab in GateKeeper)

OR

your clients need to be configured for direct access, but their web surfing should be intercepted (Again in the WWW Proxy Service, check the "Sessions" tab of that Service that Intercepts are turned on)

Then, also in the WWW Proxy Service, check that the plugin is turned on. The fastest way to confirm that your users are indeed going through the WWW Proxy Service is to check what their session types are by looking at the activity pane. If it shows up as a little web-page loading icon it is WWW Proxy, that is correct. If it is two arrows curling around one-another (Pink/Purple) then they are using NAT.

[pgr]

I'm making progress... I turned on intercepts and Puresight filtering is working fine for all computers EXCEPT the server. I would like the server to have filtering also, is this possible? How?

IE on the server is configured for direct access, and I notice filtering starts to function if I set it to go through a proxy (127.0.0.1). Shouldn't it be working on direct access also?

Thanks again

[Pascal]

No, not on direct access. You need to push it through the proxy for it to actually be filtered.