I set a wingate server for authentication only (the machine has only one nick) however the proxy HTTP service often denials pages downloading at random:
The server listen on port 8080, the users name are assumed correctly as seen in Gatekeeper message logs but the page is blocked with authentication failed. The failure appears at randomly for more than one machine (the username used is the same for more than one client).
Is it possible that a session for the same user that uses more than one PC may be confused by the server?
I use Intercept on the HTTP service.
The users are authenticate by AD groups. The wingate server is a member server, not a domain controller.
The policy is accepted only if users are authenticated. Default policy must also granted.
This is a big problem for me because a page that seems to browse correctly it may be not shown if reloaded.
Another question:
Why is not possible to use nested groups for authentication in wingate?
I noticed if a user belongs to a AD global group named FIRST wich is nested to another global group named SECOND and the SECOND group is assigned in an authentication policy in wingate, the users is not authenticated.
Thanks.
Davide Cottignoli.
Istituto Geometri "C.Morigia" Ravenna Italy