Endpoint Protection

Hi there

We have been using Web sense 6.3 and Symantec AV 10 very nicely now for a couple of years.

We are aware of the End of Life of Symantec AV 10, and are now looking at Symantec End Point 11.

We deployed the client to a server running the Web sense 6.3, and although it did work to an extent, some of the policies that Web sense uses did not work correctly.

So some  'allowed' sites such as social networking which are allowed for a specific user on a staff room computer, which although they were allowed on the policy, they were subsequently blocked when the Proxy server that was running Web sense was upgraded from AV 10 to SEP 11.

We have since removed version 11 and reverted back to 10, and all is well.

Before we build a separate server and start from scratch, we wondered if anyone else had any similar problems?

cheers folks.

Kevin

What SEP features are you running on your server? You might try removing one feature at a time and test. Report back here once you have the results.

You might try posting this issue on the Websence forum as well.

http://community.websense.com/forums/

As of now only one instance of web sense has been discussed.  Here is the link.

http://www.symantec.com/connect/forums/auto-protect-malfunction

And as rightly suggested by Cycletech check the features of endpoint installed. Out of the 3 features AV/AS is supported on all OS. The PTP feature is not supported on Server OS. The NTP feature is similar to that of a Firewall which can block both incoming and outgoing traffic, therefore it should be tested on a test environment first.

Thank you very much for the reply mate
I will try both and see how I get on

thank you

Kev

We have made some progress. It appears that the Windows User Account that had the problem yesterday still had the problem today and on further investigation the account had had its policy changed within Websense, which explains why it was unable to get to the web sites that it should.

We do not know when this was changed or how, as there are only 4 of us in Tech Support who can do that, but it appears it was all okay Friday but not yesterday, and we put 2 and 2 together, but that was not the case.

So we have resolved that problem, and we are going to do a re install today, but definately yesterday there were not stats being collected which suggests some sort of DB connctivity, but at least the policy looks like it was a very bad coincidence !

Will keep you posted

We have resolved this issue now.

Instead of doing a managed install, we did a client stand alone intsall instead, and chose only the AV, Anti Spam and the Tru Scan options. The firewall stuff weleft off and now it seems to be working okay, which gets us round this problem of deplyment for now.

The dashboard which obviously connects to the database is working a treat, and it must have been the firewall part of the AV package that was blocking the stats and real time analysis from being connected.

So were all happy here !

thanks to all who replied, I think it gave us the direction we needed.

Kevin