User Database - Domain Controller/Active directory Issues.

[SeanLeR]

Hi,

I have tried this a few times now
Whenever I set up wingate to use usernames from the Active directory it works perfectly for between 12 to 24 hours then suddenly it considers everyone to be assumed users.

Nobody can get onto the web after this as it asks clients for passwords and does not accept there active directory username and password (if you use domain\username or just the username).

Once this happens The only working solution I have found to get wingate to use active directory again is to uninstall wingate server, remove all the registry entries for wingate, reboot the server, reload wingate then restore all settings from a registry backup.

Once this is done I usually have another 12 to 24 hours before I have to repeat the process.

Please help me rectify this issue.

I have been using wingate for around 5 years now but this is a serious issue. I will be giving wingate 1 last good effort and several more hours of my time before I bin it and go for something open source.

[SeanLeR]

I do not want to post my entire registry backup into the forum as I believe some of the info may be sensitive but if anyone wants to know anything, wants screenshots or anything else please shout.

Wingate running on Windows XP x86 (completely up to date).
Our main server that the active directory runs on is SBS2008 X64.

[adrien]

HI Sean

that must be driving you nuts!

I presume it's not sufficient just to reboot the WinGate server? Reinstalling WinGate is fairly serious. I'm struggling to see what WinGate could be storing in the reg that poisons it for next time around once it gets into a state.

Is this something that's just started recently? We've seen a few issues here with accessing the AD through ADSI since running windows updates a couple weeks ago.

Regards

Adrien

[SeanLeR]

Hi Adrien,

It happens whenever I try to use AD for authentication.

It used to happen with our last server as well (windows SBS 2003 X86) but at that time I did not need as much control so I left the guest account open and parsed the logs via proxyinspector.

Currently we have a Windows SBS 2008 X64 based server.

[SeanLeR]

Thank you for the solution supplied via email.

Working perfectly so far and wow, great work!

I am very impressed :)

[adrien]

Thanks Sean

let me know if you have any issues. We're still working on documentation, and there are a few features that were in 6 that haven't yet been re-implemented in WinGate 7.

Regards

Adrien