Question about WinGate 6.0

[controlair]

I have couple pre-sales questions about how the latest version of WinGate interact with ADUC account of Win2K domain. As far as I know, in version 5, it only lets you "import" all accounts from ADUC and it is a stand alone user database after that.

1.
Does version 6 provide the ability to really "integrate" with ADUC, which means when there is addition / deletion / modification on domain users, the user database on GateKeeper will also be updated / synchronized?

2.
Does version 6 provide the ability to authenticate clients, by looking at which user account is currently used to log on to their workstation, and grant them appropriate access? Or I still have to use "Assumed IP", or have our users do another logon when they try to access to the Internet?

3.
Does it have any problem in passing traffic for Windows Update? I've heard from current user of version 5 that there is a problem in that (Windows XP only).

Thanks for replying.

[controlair]

Could I get some feedback from any experienced WinGate 6.x user? I need to make a decision pretty soon upon the answers of questions I listed above.

[MattP]

Hi,

WinGate 6 works well when using the AD user database, we've simplified the process of using a remote database now, there is a GUI for it, rather than a registry change required. You can choose your synchronisation options and there is also a synchronise now button which allows you to update the User database manually.

You can authenticate users against the OS database by using NTLM authentication. WinGate receives the authentication request and checks it against the OS database.

You may need to create a caching policy to not cache Windows Update pages, otherwise updates work fine.

I hope this answers your questions.

Regards,

Matt