Sep 22 06 4:12 am
Sep 22 06 1:58 pm
Sep 23 06 4:17 am
adrien wrote:Hi Max
You'll find that the users are making NAT connections. If you want to block this to force your users to make proxy connections, there are several options.
1. disable NAT in WinGate - this can be turned off in the General tab of the Extended Networking Properties.
adrien wrote:2. Intercept HTTP connections through to the WWW proxy. This will only work when the proxy is running though - I don't know how you're planning to use the proxy to control surfing (i.e. do you want to be able to turn surfing on and off by disabling/enabling the www proxy or something). This at least will mean the policies of the WWW proxy will apply even if users don't configure their browser to use a proxy. To do this, enter the port numbers you want to intercept on the sessions tab of the WWW proxy.
Adrien
Sep 23 06 9:49 am
Sep 25 06 11:25 pm
deftech wrote:You check the NAT setting or do you think it's disabled by faith alone :).
NAT was always enabled by default for me, check it if you haven't.
If they can surf without the "enable proxy settings" in IE then they have to be getting out through NAT.
If you do ipconfig, what are their settings?
Sep 27 06 3:26 am
Sep 27 06 3:38 am
Sep 27 06 9:07 pm
adrien wrote:Hi
what shows up in GateKeeper's activity pane when the users are surfing?
adrien
Sep 27 06 9:43 pm
Sep 29 06 2:59 am
adrien wrote:Hi
It is possible that WinGate is acting as a router instead of NAT between your internet device (is it a DSL/NAT device) and your internal LAN.
Try disabling routing in WinGate - on the General tab of the Extended Networking properties.
Routed traffic doesn't show up in GateKeeper, only NAT traffic and proxy sessions.
Adrien
Oct 02 06 5:36 pm