Wingate System Policies and NAT

[owzw]

Hi.

Running Wingate 4.5.2 on Windows NT 4.0 SP6. I am not using NT User authentication or the wingate client on each workstation. I have the Extended Network Driver enabled and General Purpose Interenet Sharing enabled.

Each user workstation behind Wingate has their web browser to Automatically Detect Settings, which causes them to use NAT rather than the www proxy service.

I have a ban list of banned urls set up for everyone. However, the list seems to be ignored when users are using NAT instead of the www proxy. This is under system policies. If I set up a ban list in the policy for Extended Networking, this is ignored also.

Can anybody help with this?

Thank you
Scott Schaffer

[tim]

Hi.
Running Wingate 4.5.2 on Windows NT 4.0 SP6. I am not using NT User authentication or the wingate client on each workstation. I have the Extended Network Driver enabled and General Purpose Interenet Sharing enabled.
Each user workstation behind Wingate has their web browser to Automatically Detect Settings, which causes them to use NAT rather than the www proxy service.
I have a ban list of banned urls set up for everyone. However, the list seems to be ignored when users are using NAT instead of the www proxy. This is under system policies. If I set up a ban list in the policy for Extended Networking, this is ignored also.

Hi, Either disable the General Internet Sharing, or turn on Transparant Redirection in the WWW proxy. This will pipe NAT level requests up to the proxy, so it will use your rules.

Tim

[owzw]

OK, I have checked off that option. So far, I have been unable to get the ban list working. Users are still able to access addresses on the banned list.

Is my understanding correct that selecting this option causes a browser on a workstation, that is not configured to use the proxy service, to be redirected thru the www proxy service? The help states that for this to work you must use a standard port for the proxy. What is standard? Currently, it uses port 8080.

Also where do I set the restrictions up, in system policies, under www proxy policies or under ENS policies?

Last, what should I set the default system rights for the www proxy and ENS services to: are ignored, may be used or must be granted?

Thanks for your help
Scott Schaffer

[adrien]

Standard port is 80. Transparent redirection currently only works on the same port as the proxy, so if the proxy is on port 8080, then only web connections that went to port 8080 (about 0.0005%) would be intercepted.

You will need to run the web proxy on port 80 for this to be effective.

Did you already have a web server running on port 80 - is that why the proxy was set to the different port?

Adrien

[owzw]

Yes, I do have a web server running on port 80. Anything I can do to get around this?

Scott

[johnlow]

I have a question which relates to this point on transparent redirection and the standard port.

You replied "Transparent redirection currently only works on the same port as the proxy......"

I have my clients and the WWW Proxy set to use the a non-standard port 1180 . Clients mostly use WGIC. I have enabled transparent re-direction as I wish to set up policies only in the WWW proxy. Is my thinking correct and is TR working for all clients?

Would you advise me to change the proxy to port 80?

Thanks