Gatekeeper Will Not Start

[Gina]

We are running Wingate 5.2.2 and ADSL, and the wingate server is using Windows NT Server 4sp6.

Since a few days ago, every time i try to start Gatekeeper i get the following error message after entering the password:
Connection with Wingate server terminated.

If you say OK to that, it just goes back to the Username/Password window; and Gatekeeper will not open.

Fortunately!!! the Wingate Service is still running, and it's business as usual with email and web browsing throughout the network.

I've tried the following to troubleshoot:

1) shut down and reboot the machine
2) shut down and reboot the machine and turn off ADSL modem and restart everything
3) run the setup/installation file for wingate 5.2.2 again - without uninstalling the existing installation

i would appreciate any help - please
i need to get into Gatekeeper, hopefully without uninstalling everything!

thanks
gina

[n0ticer]

r u running any third party firewall? e.g. zonealarm or outpost

[Gina]

no, we rely on the Wingate firewall (part of ENS)

gina

[labull]

Gina,

Try the instructions at the bottom of this post.

Larry

[Gina]

Larry,

i so hoped that deleting the History files would work - but it didn't. :(

do you have any other suggestions?

anyone?

gina

[Nev]

Larry,

i so hoped that deleting the History files would work - but it didn't. :(

do you have any other suggestions?

anyone?

gina

Hi Gina,

Virus scan?

Maybe that could help?

Good luck,
Nev.

[argi73]

Hi,
I have today the same problem. Wingate 5.2.2 on a Win NT server sp6a. I upgrade to 5.2.3, nothing, delete histor,y nothing.

I connect ot gatekeep but I cannot see the control panel and the other tabs.

The good is that the internet access still working.

I am thinking to unistall the Wingate and re-installed it. You think that will work?

Any Ideas?

[MattP]

Hi,

It sounds like you're not logged in with Administrator rights, can you verify that you're logging in as administrator?

You can check that your login has admin rights in the registry, find the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\UserDatabase\Administrators\Members
your username should be listed here, if it is not you can add your user by creating a new DWORD called Administrator, leave the value set to 0.

As always all warnings apply to editing the registry.

Regards,

Matt

[Gina]

hi Matt
thank you for the suggestion,
but it didn't work for me.
gina

[Pascal]

Few questions. Did anything change prior to this ? Such as usernames or passwords, etc. ? It seems as if you are being denied access - but that should show a message. Some of these instructions will include editing / modifying the registry - so be sure you have an appropriate BACKUP of the registry before you begin making modifications.

The first thing I want you to try is have a look in the Remote Control Service log file. This should be in <WinGate>\Logs\Remote Control Service. See if there is anything there that gives you an indication of why it might have happened.

If nothing seems obvious (Or if there are very little log entries) try enabling full debug logging. Do this by editing the registry. Now, all the applicable warnings for editing the registry apply here. Open RegEdit and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Services\Remote Control Service

Change the value of LogOptions to 3ff hex or 1023 decimal. That enables all logging. Also make sure that LoggingEnabled is set to 1. Now you'll need to restart the WinGate Engine for this setting to take effect.

Then, try the GateKeeper login again, and check the logs again. If nothing jumps out there, check your IP blackhole list. You can't get into GateKeeper, so you will have to use the registry again.

Scroll to:

HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Components\WinGate Network Driver\IP Ban Table.

There will be a series of subkeys beneath this, 0, 1, 2, etc. Check the IP value in each of these to ensure that 127.0.0.1 OR your local IP has not been accidentally blackholed. I don't think you CAN do this in WinGate, but as it's 5.2.2 I'm not 100% sure.

If all of those things are still true / the same, then the problem is with a configured policy (Which only allows access for a specific time / ip / user / etc.) or with your actual user account.

Are you using the OS (NT, 2K, XP) or WinGate user database ? If you are using the WinGate user database, try deleting your users entry from the registry. (ONLY YOUR LOGIN USER entry). This will normally be under

HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\UserDatabase

If you are logging in as user "BOB" your entry will be

HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\UserDatabase\Bob

If you're still not having any joy, we might have to cleanup the remote control service and system policies, but let's first see if you can get it sorted from this.

[argi73]

Hi Pascal

I try all your sugestion but no luck :-( . I send you few lines from the Remote service log:
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Created:
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve System Info
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve System Info
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Get local IP Information
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login:
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Get all licences
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve list of components
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve user database
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve user database
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve user database
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve user database
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve service configurations
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve service configurations
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve Assumptions
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve system policies
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve cache settings
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Get scheduler settings
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve activity information
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Get history database settings
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve dialer settings
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve WinGate Enhanced Network Support Driver Configuration
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Failed authorisation:
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Failed authorisation:
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve WinGate Enhanced Network Support Driver Configuration
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve WinGate Enhanced Network Support Driver Configuration
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Retrieve WinGate Enhanced Network Support Driver Configuration
07/20/04 08:47:14 127.0.0.1 administrator 0000000001 Requested: WinGate Login: Register for everything
07/20/04 08:49:12 127.0.0.1 administrator 0000000001 Error: Client has not responded to KeepAlive - terminating
07/20/04 08:49:12 127.0.0.1 administrator 0000000001 Traffic 25884 340 0 0 118s
07/20/04 08:49:12 127.0.0.1 administrator 0000000001 Terminated exit code 4


Nothing was change to our system the last days, also we are using the wingate user database.

I notice that If i try to connect with a user not in administrators group then I can see only the history tab. Also the connection is not terminated (exit code 4)

Thank you for your support

[Gina]

Hi Pascal
thank you for stepping in to help.

this is what i've done:
1) enabled full debug logging - see short extract of log file below
2) checked the IP ban table - that was fine
3) removed my login user name (Administrator) from the UserDatabase - but that didn't help the problem either

here's what the remote control service log file said after i enable full logging (dates and times removed):

Service started on interface 127.0.0.1:808
Service started successfully
127.0.0.1 administrator 0000000001 Failed authorisation: WinGate Remote Control Login
127.0.0.1 administrator 0000000001 Traffic 21 77 0 0 0s
127.0.0.1 administrator 0000000001 Terminated exit code 1

there's a few other things i noticed at the end of the log file from the day before the problems started, which may be a clue (although i can't remember making any changes then):

127.0.0.1 Administrator 0000546633 Requested: WinGate Login: Modify Assumptions
127.0.0.1 Administrator 0000546633 Requested: WinGate Login: Modify system policies

i definitely didn't make any changes to usernames and passwords before the problem. and nothing else jumped out at me from the RCS log.

one last thing that's happened which may also be a clue is that web browsing from this wingate server machine doesn't work any more. it can ping, telnet etc internet IPs but can't reach a webpage using IE.

thanks
gina

[Pascal]

Hi Gina,

This one is interesting. From the information you've just provided, it looks like one of the policies could be affecting this. The easiest way to solve this is for you to send your registry key to me (HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate) then I will run it in a debugger to see where the problem lies.

When I get back to the office, I canl check through that. Alternatively, I'll send you information on where to check the policies and system policies, but that will have to wait until I'm at my desk again.

One thing you can try in the meantime is to backup the Remote Control Service registry key (Where you made the logging modifications). Then delete that key. If you then stop and start the WinGate Engine, that recreates the service. If the problem is with the Remote Control Service policies, then you should be alright again. If it's in the system policies, tomorrow, I'm afraid.

[Pascal]

Alright, what I think you want to have a look at is this:

HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access

If you can backup and send me that key, I can check that. Otherwise, check what the TimeFilters and BanFilters are that have been specified.

[Gina]

Pascal,
i have sent you the registry export files.
in the meantime, i will recreate the Remote Control Service as you suggested.
thanks
gina

[Gina]

Pascal,
i recreated the Remote Control Service, but no luck.
gina

[Pascal]

The problem is with the Default Access Rights you have configured. It looks as if someone has gone and changed that.

More specifically, the Request Filter that was applied to your Default Access Rights. The fix is easy, though. Again, open RegEdit.

Go into HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access\Recipient0.

Find the value "SpecifyRequest" and change the 1 to a 0. Then you should be able to login again, and you can simply verify the Request Filters on your default access rights.

[Gina]

Pascal,

THANK YOU. you're a lifesaver!
It worked. Gatekeeper is alive and well.

anything i can do for you in melbourne, just let me know.
Gina