Authentication issues when adding restrictions

[rfreeman↑↓]

Just installed wingate on one of our windows 2000 AD servers. Version is 6.0.3. I have setup the www proxy to listen on port 80. NTLM auth is on and set the transparent proxy setting to port 80. In policies, I have set so that default policies are ignored and added 1 user from my domain. With no BAN settings or advanced setting, everything looks fine as wingate is logging my domain username and allowing me to sites. When I try to add anything to the BAN list or the advanced tab, all the logging comes through as guest. Any way around this? I have read some other posts in the forums, but I did not see a solution.

[erwin↑↓]

Hi there

What you are seeing has to do with the way that WinGate receives and processes WWW requests.

The reason why you are seeing the failure as Guest when a banned site is accessed is because when the client makes a WWW request, WinGate checks the request against its policies before anything else to see if the site is banned even before the authentication challenge (to identify the user takes place), which is why it fails immediately and logs the failure against “guest”, as it doesn’t even continue with auth challenge if the policy has been breached.

You would find if the user was try and access an allowed site, before accessing a banned site, WinGate will have had a successful chance to establish who the user is and so all subsequent requests for banned sites from that user while their connection is active with WinGate, will result in the username being logged against the failure.

I retested this here in the lab this morning in the AD scenario and confirmed this is the case.

Hope this helps

Regards
Erwin