Confused about User Database Options!

[HUEYDOK]

Hello. I am confused with the HELP instructions on how to configure the User Database Options. I want to authenticate all users against an Active Directory security group ONLY. The instructions and screens state I basically have three options:

1) Authenticate against a local WinGate proprietary user database (I do not want this)
2) Authenticate against the local Windows Server OS users and groups (I do not want this)
3) Authenticate against a remote user database such as Active Directory ( This is what I want).

The problem is that the instructions state to place a checkmark in EITHER the "Use the Operating System (Windows) user database", OR "Use Remote User Database (Domain Controller / Active Directory)". The key words here are "either" and "or", and since I do not want to authenticate against the local OS database, I did not place a checkmark in that box. However, if I do not check that box, then I cannot place a checkmark in the second option since it is greyed out! In addition, if I leave both checkmarks in (so I can get option #2 to work), and then go back and uncheck option #1, it reverts back to WinGate-only proprietary authentication!

So - it would seem that I do not have the option of authenticating ONLY against a remote Active Directory, since I must also enable authentication against the local OS in order for either option to work. This is not what I expected and not what the instructions state, which should give me a choice of either/or. I am experiencing other authentication issues that I think are related to this (see my other post under Hueydok). Any thoughts or ideas? I am running version 6.5.2 (build 1217).

[logan]

WinGate goes through the local operating system when talking to remote user databases, however when you select both options (Use the OS user database and Use remote user database) you are authenticating against the remote user database and not the local one.

If you are having problems syncing with and authentication against the remote AD, make sure that WinGate is logging on as a domain admin and not the local system account. This needs to be done so that WinGate actually has permission to access the remote AD.