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.