Gatekeeper stopped working

[intell]

I upgraded Wingate to 7.1.0.3389, and since that, Gatekeeper doesn't work anymore.

Look on the screenshot attached.

Already tried to delete the reg key HKCU\Software\Qbik Software\Gatekeeper, no luck. Reinstall Wingate, no luck either.

It just hangs on that screen. If I click on any link below "Getting started on Wingate", like Install/Configure Services, nothing happens.

Please help.

[adrien]

Hi

that's what you see when you log into WinGate with an account that has no rights to see anything.

All you did was install the upgrade? Or did you alter any permissions or group membership? Did you change the account you log into WinGate with?

Regards

Adrien

[intell]

I just upgraded.

I use internal Wingate database account. I'm logging as user "Administrator", the same user I use since day 1.

Any thoughts? I'm not being able to administrate anything..

[adrien]

Hi

can we have a look at this system remotely? It would be great to know what caused this on an upgrade, and I think it would get you back up and running the quickest.

If so, we normally recommend Teamviewer, just send an email to support@wingate.com with teamviewer ID and password.

Regards

Adrien

[intell]

I just found the solution. After you said my account is behaving like a non-admin, I've decided to take a closer look on some regedit keys. Look what I have found.

That is the UID for Administrators group:
[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Users\WinGateProvider\Objects\{00488E68-210E-11DF-901D-00D0B70B08F7}\Members]

Now look on who was the member:

"S-1-4-219688881-500"=dword:00000001

That UID doesn't belong to Administrator account:

Administrator UID: S-1-4-219688882-500
Guest UID: S-1-4-219688881-500

Yeah, you are seeing right. After the upgrade, my only administrator was... the guest user! If that was caused by the upgrade, it's not only a bug but a potential security risk. Guest as admin? Yikes!

After I reverted to Administrator UID I was able to log in normally.

Thanks for your help adrien.

[adrien]

Hi

Thanks for that information.

did the computername change?

Which version did you upgrade from? I don't know why it would change the SID on Administrator...

Regards

Adrien

[intell]

Absolutely nothing was changed.

Upgrade -> Reboot -> Gatekeeper stopped working.

Previous version: WinGate7.0.8.3364-USE.exe

[adrien]

Ok thanks.

I wonder if it had some previously unmigrated user from a previous version (e.g. WG6)... had you run WG6 on that computer?

Otherwise everyone would be screaming about this.

I'll get the lab to look at it.

thanks!

Adrien

[intell]

I never installed Wingate 6 on that machine. I'm using version 7 since RC days.

Thanks.

[adrien]

Hi

did you copy / paste those SIDs into this forum? Just wondering if there was a typo.

the 3rd part of the SID is based on the computername, so for there to be 2 different ones implies either the computer name changed, or something happened in the calculation of the hash from it.

The final part is a well-known RID, used in AD and windows.

500 = Administrator
501 = Guest
544 = Administrators group (domain admins in AD)
545 = Users

Adrien

[adrien]

we couldn't repro in the end.

I think maybe it was some legacy issue from an old version of 7. we haven't had any other reports of it.

Adrien

[intell]

I copy / paste all the info above.

Computername wasn't changed.

[adrien]

ok

that only leaves either reg/disk corruption, or some WinGate crash that fried its brains and caused it to write that...

Adrien