Error: Connection with wingate server terminated

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Error: Connection with wingate server terminated

Postby xgorrea » Feb 28 04 2:33 am

Help!

I can not logon to Gatekeeper to perform administrative tasks. After introducing the password for 'Administrator' I receive the message "Connection with wingate server terminated".
Could you please give me any suggestion to fix this problem? Could it be related with system policies or 'Assumed Users'? (I think it was the last thing I was changing)

Thank-you.
xgorrea
 
Posts: 8
Joined: Feb 27 04 10:19 pm

Postby ChrisH » Feb 28 04 3:40 am

Hello,

I have copied a response by Adrien to a similar problem on another post.

you can reset the Administrator password if it thinks it has one already.

To do this,

1. Stop the engine.

2. open regedit.exe, go to

HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate\UserDatabase

delete the Administrator subkey from here

3. start the engine again.

Then try logging in with no password, and the username Administrator to the local machine on port 808 (default port for Remote Control Service)


I would add to do a backup up of the registry before you do this - just in case something goes awry. You are probably right - something you changed in policy is preventing gatekeeper password authentication.

Hope this helps.
Chris H.
ChrisH
WinGate Master
 
Posts: 388
Joined: Sep 13 03 1:38 am
Location: Canada

Postby xgorrea » Mar 01 04 10:09 pm

Hi,

I have tried to do that, but when logging to local machine whith blank password I get the following: 'You have not specified a password. Do you want to continue without password?'. I choose OK and I received again the message'Connection with wingate server terminated' being not possible to log on. Now I have restored the registry to the previous status.

Any other suggestion?

Thank you very much.
xgorrea
 
Posts: 8
Joined: Feb 27 04 10:19 pm

Postby timg@monsom.co.za » Mar 02 04 3:27 am

Hi

I have the same problem. I fisrt installed Wingate on an NT server 4 computer and the system worked fine. Then the message appeared i then built a dedicated Windows 2000 Pro computer and loaded Wingate on it, again started out fine, two days later the offendin message appeared and I have not been able to log int Gatekeeper.


Any Suggestions

Many Thanks

Tim
timg@monsom.co.za
 
Posts: 2
Joined: Mar 02 04 2:44 am

Postby asevnov » Mar 02 04 5:18 am

CONNECTION TERMINATED - Same error message with 5.2.3. as colleague reported: can not logon to Gatekeeper to perform administrative tasks. After introducing the password for 'Administrator' I receive the message "Connection with wingate server terminated".

Any cues?

Thanks.


Andrei
asevnov
 
Posts: 2
Joined: Mar 02 04 4:59 am

Postby ChrisH » Mar 02 04 7:23 am

Hello,

I think in all cases we will need more information then. Give us as much information as you can about system setups. Are you using NT user database? Active Directory? Trying to log on to GateKeeper locally or remotely? WinGate version? Using WG as DHCP? etc. Thanks.
Chris H.
ChrisH
WinGate Master
 
Posts: 388
Joined: Sep 13 03 1:38 am
Location: Canada

Postby asevnov » Mar 02 04 9:08 pm

Chris,

We are NOT using NT database or Active Directory ( I guess we have no domain). It is small network in the hospital including W2k and WP workstations and we tunnel through one WinGate (v.5.2.3) computer (W2k) to Internet. Recently we decided to watch traffic by user putting some restrictions in WinGate settings. After this we constanly have this "connection to server terminated" message trying to login locally.

Thanks.

Andrei
asevnov
 
Posts: 2
Joined: Mar 02 04 4:59 am

Postby xgorrea » Mar 02 04 10:22 pm

Hi,

I have tried by deleting the .../Services/Remote Control Service from registry as suggested by a member of Qbik Technical Support, but it does not solved my problem. But try It, perhaps this action could solve yours...

Because it was one of the latest options I was modifying on the system, I post here the 'default rights' entries on regedit, just in case anybody finds something suspicious on it:

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access]
"RightType"=dword:00000000
"IncludeDefaultRights"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Edit]
"RightType"=dword:00000002
"IncludeDefaultRights"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Edit\Recipient0]
"UserName"="Administrators"
"Description"="Unrestricted rights"
"SpecifyUser"=dword:00000001
"SpecifyLocation"=dword:00000000
"SpecifyTime"=dword:00000000
"SpecifyBan"=dword:00000000
"SpecifyRequest"=dword:00000000
"MinimumSecurityLevel"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Edit\Recipient0\BanFilter]
"Name"=""
"Description"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Edit\Recipient0\ExcludedLocations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Edit\Recipient0\IncludedLocations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Edit\Recipient0\RequestFilter]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Edit\Recipient0\TimeFilter]
"Name"=""
"Description"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\MultiAccess]
"RightType"=dword:0000000e
"IncludeDefaultRights"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\MultiAccess\Recipient0]
"UserName"="Everyone"
"Description"="Unrestricted Rights"
"SpecifyUser"=dword:00000000
"SpecifyLocation"=dword:00000000
"SpecifyTime"=dword:00000000
"SpecifyBan"=dword:00000000
"SpecifyRequest"=dword:00000000
"MinimumSecurityLevel"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\MultiAccess\Recipient0\BanFilter]
"Name"=""
"Description"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\MultiAccess\Recipient0\ExcludedLocations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\MultiAccess\Recipient0\IncludedLocations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\MultiAccess\Recipient0\RequestFilter]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\MultiAccess\Recipient0\TimeFilter]
"Name"=""
"Description"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\StartStop]
"RightType"=dword:00000001
"IncludeDefaultRights"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\StartStop\Recipient0]
"UserName"="Administrators"
"Description"="Unrestricted rights"
"SpecifyUser"=dword:00000001
"SpecifyLocation"=dword:00000000
"SpecifyTime"=dword:00000000
"SpecifyBan"=dword:00000000
"SpecifyRequest"=dword:00000000
"MinimumSecurityLevel"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\StartStop\Recipient0\BanFilter]
"Name"=""
"Description"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\StartStop\Recipient0\ExcludedLocations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\StartStop\Recipient0\IncludedLocations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\StartStop\Recipient0\RequestFilter]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\StartStop\Recipient0\TimeFilter]
"Name"=""
"Description"=""

Regards,
xgorrea
 
Posts: 8
Joined: Feb 27 04 10:19 pm

Postby ChrisH » Mar 03 04 2:43 am

xgorrea,

After looking at your Registry entries I would have to say that you deleted the Everyone user from system policies and as a result you are not able to log onto GateKeeper. Add the following back into
HKLM\Qbik Software\WinGate\DefaultRights\Access and hopefully you will be OK. Again do a registry backup as a precaution before adding these entries. As a suggestion, what I do before making any changes to WinGate policies is back up the WG registry in GateKeeper by going to
Options, Advanced,Save Registry Settings just in case I mess something up:)

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access\Recipient0]
"UserName"="Everyone"
"Description"="Unrestricted rights"
"SpecifyUser"=dword:00000000
"SpecifyLocation"=dword:00000000
"SpecifyTime"=dword:00000000
"SpecifyBan"=dword:00000000
"SpecifyRequest"=dword:00000000
"MinimumSecurityLevel"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access\Recipient0\BanFilter]
"Name"=""
"Description"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access\Recipient0\ExcludedLocations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access\Recipient0\IncludedLocations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access\Recipient0\RequestFilter]

[HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights\Access\Recipient0\TimeFilter]
"Name"=""
"Description"=""

Edit: Just another thought. Perhaps the Remote Control service default right policy was modified and it now uses the System policy which has effectively no access rights so right would not be granted to use RC service.
Chris H.
ChrisH
WinGate Master
 
Posts: 388
Joined: Sep 13 03 1:38 am
Location: Canada

Postby ChrisH » Mar 03 04 3:02 am

Andrei and Tim,

Could you post the
HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Services\Remote Control Service and
HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights Registry Keys and sub keys here? This might help in solving problem. It is probably something fairly easy to fix. I suspect a policy change now precludes anyone from accessing the remote Control service.
Chris H.
ChrisH
WinGate Master
 
Posts: 388
Joined: Sep 13 03 1:38 am
Location: Canada

Postby xgorrea » Mar 03 04 4:41 am

SOLVED !!

I have restored the "Everyone user" to system policies with the options provided by CrisH and... It worked!
You are right, it is a good suggestion to save the registry before make any configuration changes. I will keep it in mind.

Thanks CrisH, and others for your interest.

Best Regards. ;-)
xgorrea
 
Posts: 8
Joined: Feb 27 04 10:19 pm

Postby timg@monsom.co.za » Mar 03 04 8:41 pm

ChrisH wrote:Andrei and Tim,

Could you post the
HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Services\Remote Control Service and
HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\DefaultRights Registry Keys and sub keys here? This might help in solving problem. It is probably something fairly easy to fix. I suspect a policy change now precludes anyone from accessing the remote Control service.


Hi i made the registry changes to put Everyone back and I can now log into gatekeeper. How can I remove the Everyone user from System Policies without ending up with the same situation ?

Mant Thanks

Tim
timg@monsom.co.za
 
Posts: 2
Joined: Mar 02 04 2:44 am

Postby ChrisH » Mar 04 04 3:49 am

Tim,

Generally, WinGate has a two level policy structure. There is a System wide policy that covers everything WinGate does, and then each service or proxy that WinGate offers, can have its own policy independent of the System policy.

By default, WinGate installs Everyone into System Policies. That way most setups can have internet access right away. Also all services eg. DNS, WRS, GDP, POP3 server etc. all have the Default rights(System policies) of their policies set to may be used instead, they have no individual policy. This means that those services check what the System policy says and then grants access accordingly.

On default then, Everyone has access. In general, if you do not want to allow Everyone to have access to a particular service then you must restrict by a service policy who can acess the service. To do this, you must go to the service or proxy policies and change the Default rights (System Policies) to are ignored then add the groups or users who can access this service or proxy. Of course, this may mean that you have to add users or groups to the WinGate database through the Users tab.

The GateKeeper uses the Remote Control Service to log a user on. By default the system policy applies to this service. If you do not want the system policy to apply, then you must ignore the system policies and tell the service who can have access - as outlined above. Alternatively, if you do not want to do this, then change your system policy so that only the users or groups you want using WinGate are able to. The Everyone group is just that - everyone - including guests. By deleting Everyone from the system policy and not adding back who should have access, no one would have access to any service that required system policy verification - and if it is the default setup, basically nothing would work. So I would stress that making a backup of the WinGate registry is a good idea before changing policies as the change could potentially cause a lot of grief.

The Qbik knowledge base has some good articles. Check these out (and the others too!)
http://support.qbik.com/index.php?_a=kn ... %3C%2Fa%3E
http://support.qbik.com/index.php?_a=kn ... ails&_i=98

Hope this helps.
Chris H.
ChrisH
WinGate Master
 
Posts: 388
Joined: Sep 13 03 1:38 am
Location: Canada

Postby seatrain » May 21 04 3:58 am

Well done, Chris H!! Will this problem always occur when I change System policies in wingate? All I tried to do was limit user access between certain times!

Thanks again to all who assisted - Nigel Devey.
seatrain
 
Posts: 1
Joined: May 17 04 1:09 am


Return to WinGate

Who is online

Users browsing this forum: No registered users and 3 guests

cron