To ensure that all users who attempt to connect to the Internet through WinGate are authenticated you will need to do the following:

For NAT, WGIC, and Proxy clients:

1. Open GateKeeper on the WinGate server
2. Select the Users tab.
3. Open the System Policies icon.
4. Ensure the Rights option at the top is set to Users can Access these resources.
5. Click the Add button.
6. On the Properties of Recipient dialog that appears, click on the Recipient tab.
7. Select the Everyone radio button, and then the User must be authenticated radio button.
8. Click OK back through the dialogs.
9. Save changes in GateKeeper.

This will now mean that anyone who tries to connect through WinGate must be authenticated by one of the authentication methods described in the WinGate helpfile.

Please Note: This setting can be overridden on a Service by Service basis by configuring the service in question to explicitly ignore Default system policies as described in the WinGate helpfile. ]]> One of the three methods available to authenticate users in WinGate is to use a copy or mapped drive of GateKeeper.exe from the WinGate directory on the WinGate server, to each client machine.

Please Note: There are several things are required before attempting to use this form of authentication:

1. You will need to create a valid user and password in the WinGate user database (if using this for user accounts), a valid user account in NT/2000/XP if using the Operating System (Windows)Database option in WinGate.
2. In the Remote Control Service (found under the System tab in GateKeeper) you will need to make sure that Internal IP of the WinGate server is bound to allow the Gatekeeper.exe to be used for remote Authentication. (Please refer to the WinGate helpfile on how to do this)
3. Appropriate access rights have been configured for the user.

Once these things have been done on the WinGate Server, then authentication by this method can be achieved by doing the following:

1. Copy the GateKeeper.exe file from the WinGate folder on the machine acting as the WinGate Server or alternatively map a network drive to it.
2. Open the newly copied GateKeeper file on the client machine you which to log on from. (Simply double click on the GateKeeper.exe file).
3. Once the Online options Log on window is displayed, in the Username box, type the name of a user from the WinGate user database who is requiring (and has appropriate permissions to log on to WinGate etc) authentication.
4. In the password box enter the Users correct password.
5. In the Server box enter either the IP address or Server name of the WinGate server. (If this is greyed out uncheck the Log on to Local host check box).
6. Click OK and the User should now be authenticated. This is all the GateKeeper.exe is required for, and Users should now be able to access their allowed Internet activities (using their apps etc) through the WinGate server.

Please Note: The guest account in WinGate has a blank password by default, so this means that if the user Guest was entered in the User box in this scenario, there would be no need for a password to be entered for a successful log on.

This of course is not very secure so it is recommended that the Guest account on the WinGate server be given a password in this case. ]]> WinGate offers Java Authentication for clients who are using a java capable browser. The Java client is a java applet that connects to the Remote Control Service in WinGate to authenticate users. To use Java based Authentication, you must do the following:

On the WinGate Server.

1. You must be using the WinGate User Database. If you are using the Windows User Database, this option is not available, and there are other ways you can get your users to authenticate.
2. Open GateKeeper on the WinGate server.
3. On the System tab click on the Remote Control Service.
4. Select the bindings tab
5. At the bottom of the tab, there is a section called Binding Policies - This determines which interfaces will be able to access this service. If there is not a binding showing for the adapters your clients are connected to, then add a binding policy, choose "any internal adapter", then click OK, and OK.
6. Select WWW proxy server under the Services tab in GateKeeper.
7. On the General tab under authentication methods, check the tick box Java Authentication. You must be using the WinGate user database for this to be available.
8. Next, select the Policies tab in the WWW proxy server.
9. Underneath the window in the middle of the dialog make sure that the Default Rights (System Policies) are set to Are Ignored, then click on the Add button below. The new dialog Properties of new recipient will appear.
10. Select the everyone radio button.
11. Select User must be authenticated radio button below the window.
12. Click OK back through each dialog.
13. Save changes in GateKeeper.

On the Client machine

1. The web browser will need to be configured to use a Proxy server.
2. The address for the proxy server will be the Internal IP address of the WinGate server.

]]>