Client Setup

[kamikazicamel]

We are currently evaluating Wingate for our company. We have everything set up and working properly. Our main concern is the client. I have 2 problems:

A.) We need to be able to distribute the client this quickly and silently as we have around 100 computers. We can set up the remote installation and distribute it without a problem, but any time we install it, remotely or locally, the client does not work until we manually open the client toolbox disable, reenable and close. Is there any way to get it to activate itself?

B.) Is there any way to prevent a user from disabling thier own client? We need the client to control which users have access, however we have salesmen bring laptops in which cannot have the client and need internet access, so the access cannot be severed any other way...

[genie]

You can avoid installing the client by using NAT support - all clients should have Wingate machine as a default gateway and the traffic can be then controlled by ENS/NAT-related set of policies.

[kamikazicamel]

We tried setting up NAT first but all users showed as guest in Wingate. We need to be able to restrict WHO can access the internet based on system login but still have unlimited acces for people who are not part of the domain.

[genie]

You can setup a policy that requires authentication - it means then that whatever your clients do they have to get authenticaetd first using proxy authentication, gatekeeper authentication of QbikAuth authentication.

[kamikazicamel]

What about the users that are not going to be able to authenticate, such as salesman and outside contractors that will not have accounts?

[genie]

You can simply request from them to go to any web site - then Wingate would request authentication (through its Java client, for example).

[MattP]

Hi,

I don't want to confuse the issue but the WGIC (WinGate Internet Client) could be a good solution for you. The WGIC would allow you to intercept all connections from the client machines and authenticate them seamlessly if you're using the Active Directory user database. Then the laptop/external users can receive a generic username/password, or use their own if they're a member of the domain. They won't need the WGIC installed to access the Internet if you create your Internet access policy in the WWW proxy. They will be prompted to authenticate when they open a browser page.

The problem with the WGIC could be due to internal firewalls. The WGIC relies on a broadcast that it sends to the network to discover any listening WinGate servers, perhaps this is being blocked before it gets to the WinGate server?

If you are using NT based OSes on the clients and the users are not members of the Administrators group then they should not be able to disable the WGIC.

I hope this helps,

Matt

[kamikazicamel]

We are set up using WGIC with Active Directory. WGIC is finding the server and configuring fine, but it will not intercept traffic until we manually access the client, make some form of change, and apply/ok.

All of our computers are running Windows 2000 Pro or Windows XP Pro yet on the computer we are testing on (Win XP) when I log in as a user without Admin rights it still allows me to disable the client.