Choose from several options for complete web, email and data security.
Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Come work for the global leader in unified information security.
Websense apply default policy on user's , please find below for better understanding issue:-
For user identification we have applied manual authentication secondly everthing would be fine for next with in min websense unable to filter the Website and categorized all sites in "Network error" , then we restart the Filering service then everything is working fine.
Second issue:- Websense applied default policy on all users and some tiime it prompt for user credentials but Websense not accept that and shows "Session timeout" then we restarted the User service and issue got resolved , then we analyze the Application events logs and found application warning error " error says Websense unable to get the group or user detail from DC.
We have continiously facing these issues , please suggest
Which version of Websense are you using? Please check the Fatal Error messages in Websense.log file.
BTW, just kindly remind you, this is Suggest a Feature forum. Next time, please post the issues with Websense products to: http://community.websense.com/forums/
This is the Web Security forum: http://community.websense.com/forums/default.aspx?GroupID=6
More customers will see your posts in there :-)
I am experincing the same problem on websense 7.6. i've created policies and applied them to the OU's, but for some reason only the default policy is applied to all the users. how do i enforce the newly created policies to work?
I know this post is old but there's no answer and I'm encountering the same issue - the Default policy is being applied to everyone. I've tried to troubleshoot DC Agent yet that doesn't seem to be the problem. Any suggestions while I wait for support contact me?
Good ol' testlogserver should be able to shed some light on it for you. Normally when users are all getting the default policy either a) Users aren't being properly identified or b) Misconfiguration of policies is causing everyone to get the default policy
Thanks Glitch. The reason I posted is because I've gone through all that so simply stating check the obvious first doesn't really help me. I've gone through the DC Agent troubleshooting documentation and everything appears to be in order. As for policies - probably the issue but where to look? For example, users are being identified correctly but the incorrect policy is being applied - testlogserver shows this. When I look at the policy config - default is assigned to 0 clients, the basic policy we use is assigned to Domain Users. If I compare testlogserver results to a check via triton it is the same. So, how can I check the policies then as that is where I suspect the issue is.
We limit our server subnets to particular whitelisted sites. I created a policy called Server Allowed Destinations and then created the subnets in Clients. Those subnets have the Server Allowed Destinations policy applied to them.
When a person in the AD group that is allowed full Internet access via a different policy tries to access the Internet from a server, they seem to get the default policy because the block page says "all access is blocked" or something similar.
Any chance something similar is happening to you?
Oh yeah, the Real Time Monitor properly identifies them via AD but shows all sites as Blocked when this happens.