by logan » Oct 09 07 9:02 am
This is a simple logic error that is causing your problem.
Think of the WWW Proxy Policies as a room and each policy in the Proxy as a door that leads to the world outside. In your case, there would be two doors. Group1, and Group 2.
When the user tries to open a door, the policy of that door will be checked to see if the user is allowed out or not. The user can try any number of doors that he/she needs to to get out of the room. If the user fails to open the first door, then he/she will move to the next until the user either gets out, or finds that no door will open.
So in your example, when your user goes to Site1, the user tries door 1 (group 1) first and will find that the door won't open because of the ban list. Your user will then find that door 2 (group 2) doesn't have the site banned, so your user is able to get to site 1 via door 2.
The same goes for site 2. When your user navigates to site 2, they will try door 1 and find that they are allowed to get out through door 1, even though door 2 doesn't let them.
To solve this logic error, you simply need to change the way you think about group policies when you make them. For example, just making an extra policy will give you your desired result.
Policy1 - restrict user from ICQ
Policy2 - restrict user from sex.com
Policy3 - restrict user from ICQ "AND" sex.com
Also, make sure that the default rights for the WWW Proxy is set to "are ignored" to stop the user from using the System Policy doors if the user can't get out the policy specific doors.
The policy framework in WinGate 2007 has been completely overhauled to give you absolute control over the policy logic in addition to more advanced and more efficient policy decisions. This sort of logic error will be a thing of the past and how you make the policy decisions is how they will be carried out.