Proxy Service Policies do not work (after upgrade6.0.1.)

[mv1234]

Hello,
Wingate runs on Windows 200 server. When I upgraded to 6.0.1. users can not connect to internet. Access is denied is diplayed to them.

The users are assumed by their IP address. All the user have access everywhere. There is also the user "everyone" which has access to specific addresses. If a user tries to connect to these addresses there is no problem. All the other addresses display "access is denied".

On the activity monitor I can see that Wingate correctly assumes users (it diplays their names, so it reads correct their ip address).

I have to mention that there was no problem before the upgrade.

Please help me.
Thanks in advance.

[erwin]

Hi there

On the front screen of the policy config in WWW proxy what is the
"Default rights (System Policies)" setting set to. Are ignored?

If I understand your post correctly, you have set "everyone" to only access a specific list of sites as a policy in the WWW proxy?.

If this is the case and the Default rights setting is set to "Are ignored" then the policy will be applied to everyone.(regardless of group or user)

Check to see if this is the case.
You could try changing the Defaults right setting to "May also be used". Then whatever System policies you have set or the service policy may be used. (Since when comparing access policies WinGate will choose the least restrictive.)

Regards
Erwin

[mv1234]

Hi there
>> Thanks for replying

On the front screen of the policy config in WWW proxy what is the
"Default rights (System Policies)" setting set to. Are ignored?
>> It is set to "may be used instead"

If I understand your post correctly, you have set "everyone" to only access a specific list of sites as a policy in the WWW proxy?.
>> yes

If this is the case and the Default rights setting is set to "Are ignored" then the policy will be applied to everyone.(regardless of group or user)

Check to see if this is the case.
>> Unfortunately it is not. However I noticed that if I enter the user >>proporties and change "user may be assumed" to "user may be >>unkonown" it works. Is this what I have to do ? (the previous version >>was ok with the choice "user may be assumed")
>>Thanks




You could try changing the Defaults right setting to "May also be used". Then whatever System policies you have set or the service policy may be used. (Since when comparing access policies WinGate will choose the least restrictive.)

Regards
Erwin

[Dr_Cancel]

Hi all!
I have the same problem. But I find the reason, I think.

I have two services

1. FTP Proxy Server
2. WWW Proxy Server

In both services properties are the same.

Default rights (System Policies)"are Ignored"
Policies in FTP Proxy
2 groups
FTP_Proxy_Server & Administrators

Policies in WWW Proxy
2 groups
WWW_Proxy_Server & Administrators

And now the most interesting!!!
FTP Proxy work perfectly! all users can go to internet as before upgrade.
WWW proxy not work... Users receive error 403...
so...
I for a long time searched and searched in what a problem, have damned Wingate...
and...
I have decided to exclude group Administrators from access to WWW Proxy.... ooooo.... f....k... Users now can go to internet...
I have not believed the eyes and have added group back...
and users can't go to internet...
I have checked up this guess on FTP Proxy... But with FTP this problem has not proved to be true...
so... mv1234 maybe it will help you...


Now words for Qbik...

[mv1234]

Unfortunately, this is not the solution to my case.
Thanks for the reply.