Knowledgebase: WinGate
Using a Domain Controller User Database - Pre-version 6
Posted by Adrien de Croy (Import) on 30 January 2004 05:34 PM
As per the WinGate helpfile it is possible, when using the NT user database option in WinGate, to synchronise the NT User database on a Domain Controller in a Windows NT4/Active Directory Domain environment.

Please Note:
To do this requires editing the registry settings, you should only attempt this if you fully understand the consequences of editing the registry, and have taken the appropriate steps to backup the WinGate registry.

Obviously the WinGate server needs to be part of the NT Domain to authenticate properly.

To make WinGate synchronise with a Domain Controller on NT Domain :
  1. From the Run command on the Start Menu type Regedit.
  2. Expand to the key called HKEY_LOCAL_MACHINE\\Software\\QbikSoftware\\WinGate\\UserDatabase.
  3. Create a string value called DomainServer
  4. Set the value in the form of a \\\\Servername , where Servername is the Computer name of the Primary Domain controller.
Please Note: For Active Directory Domain Controllers
When using an Active Directory Domain Controller for a database there is one futher step required for this work correctly:
  1. Open the Computer Management MMC (found in Administrative tools in Windows) and open the Services and Applications configuration that lists all Services.
  2. Select the Qbik WinGate Engine service.
  3. Right click on this service and select Properties.
  4. Select the Log On tab.
  5. Where it says Log on as, select the This Account option and browse the Active directory for a suitable account with Domain Adminstration equivilent privilages. (It is recommended that administrators create a special account in Active Directory Users and Computers for this purpose.)
  6. Stop and then Restart the WinGate engine for the changes to affect.
  7. Re-synchronise the database from the User database configuration found under the Users tab in GateKeeper.

    If the setup is not followed exactly as outlined above then it will cause the inability for the administrator to log in to Gatekeeper, which may require uninstalling and reinstalling WinGate if necessary.
(1170 vote(s))
Helpful
Not helpful

Comments (0)