Forcing Proxy in WinGate 6

[ahkow]

Hi, I am using WinGate 6.6.4 Plus in Windows Server 2008 R2.
In WinGate 7, you can force proxy and let user see a custom page when they are not using proxy.

In WinGate 6, I am trying to simulate the effect.
- Extended Networking -> Port Security -> LAN connections to Internet -> Default action = Deny.
- Extended Networking -> Port Security -> LAN connections to WinGate PC -> Default action = Allow.
- In WWW Proxy, port 80 is intercepted.

But how to display a page like in WinGate 7 when user does not use proxy?
I see that there is a 'Web Server' which has a default 'Reject' action. But I never see any 'Reject' page when user is not using proxy.
Is this a restriction of my WinGate Plus license?

[adrien]

One of the limitations of WinGate 6 policy was that it was a grant only system.

If not granted, then a request is denied, and therefore there is only ever 1 reason why a request is denied.

therefore you can't do different actions based on different reasons why a request is denied, since there is only ever 1 reason - the rules didn't grant it.

You'll need WinGate 7 for this sort of feature.

Adrien

[ahkow]

Thanks, but I think you misunderstood me.
What I want is a reject page shown in user's browser if she did not use a proxy to access internet.

[adrien]

exactly.

But WinGate doesn't know why it is rejecting. So you can only define 1 reject page for all cases - even that is a registry hack.

[ahkow]

I think I understand the grant only style in WinGate 6.
But how do I show the "Proxy required" page when user is not using proxy, just like in WinGate 7?
Maybe I should not use the 'reject' word in previous posts, what I meant was showing the user a 'Proxy required' page, thus rejecting users from accessing internet through NAT without WinGate proxy.

[adrien]

Hi

check out http://forum.wingate.com/viewtopic.php?f=12&t=40952

that allows you to specify some content when a page is blocked. That's it for WG6 though, so if you block for any other reason, it will still be this same page.

that's why we added divert etc to WinGate 7.

Adrien

[ahkow]

Thanks. I end up with setting a policy in WWW Proxy server, the criterion is Is non-proxy request is FALSE. Then intercept port 80. This seems to reject user when they are not using proxy to access internet (through port 80).

Then I customize the page by adding a AccessNoRightsDescription key in HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\ErrorStrings\HTTP. The value is something like <META HTTP-EQUIV="Refresh" CONTENT="0;URL=http://local.company.com/denied-or-need-proxy.html">