[b]WG licence issue with 5.0.2 (Build 780)[/b]

[St_Jammy]

I'm having issue with upgrading WinGate beyond version 5.0.2 (Build 780)

I purchased WG back at version 4.4 (or there abouts) and am a bona fide licenced user.

My licence enabled me to upgrade as it was anounced (then by Deerfield) all the way up to 5.0.2

Since then, I've been unable to upgrade further.

Is this an issue with my licence?

Or is it something to do with the Deerfield debacle?

Cheers

[Pascal]

What kind of problems are you experiencing when you upgrade ? Any version 4.x license will work with 5.x (Any version) - you will just not have access to any of the new features.

[St_Jammy]

What kind of problems are you experiencing when you upgrade ? Any version 4.x license will work with 5.x (Any version) - you will just not have access to any of the new features.

The answer below is a bit protracted, sorry for that, but I always feel that us folks never give you guys enough info to work with :o)
____________________________________________________________

The installation of any version of WinGate later than version 5.0.2. (Build 780) on my Win2000 Prof SP3 Build 2195 machine goes like this:-

Log on as Administrator, close GateKeeper and shutdown WinGate engine; ok.

Install newer version (any); ok.

Reboot PC; ok.

WinGate engine start (automatic); ok.

Launch GateKeeper; ok.

Logon dialog box appears. Enter my old GateKeeper password, click 'OK' button.

New dialog box pops up entitled: "Problem connecting to server" and says:-

"There was a problem connecting to the server.
Connection refused by server. Check your
server name and port number"

This occurs even if I don't put a password in (which I would expect).

Then I have to uninstall WinGate in it's entirety, reboot, and reinstall version 5.0.2... AGAIN!

A rollback option would be useful here!

Any help on this matter would be appreciated. If you need any other details like proof

of purchase let me know.

Best regards

[Pascal]

When it refuses the connection, can you check with "netstat -an" to see if anything is listening on port 808 ? That would be the first step. If there is, we can try re-creating the Remote Control Session. I posted details on how to do this in http://forums.qbik.com/viewtopic.php?t=1164.

If that still does not resolve the problem, can you export the WinGate registry setup, then I'll have a look at it here to see if I can see any specific reason for it failing.

[St_Jammy]

When it refuses the connection, can you check with "netstat -an" to see if anything is listening on port 808 ? That would be the first step. If there is, we can try re-creating the Remote Control Session. I posted details on how to do this in http://forums.qbik.com/viewtopic.php?t=1164.

If that still does not resolve the problem, can you export the WinGate registry setup, then I'll have a look at it here to see if I can see any specific reason for it failing.

Thanks for your help so far. As you may appreciate, until this gets resolved, I have to keep installing and uninstalling different versions of WinGate in order to test your suggestions and remain internet ready!

I've printed off your replies, but as it's 12:40am and I'm a science teacher (don't groan) I have to grab some shut eye, for today is the start of another week listening to the little urchins... (sorry), little dears bicker with each other and pay me no attention what so ever!!!!

I'll try your suggestions tonight, local time, if I survive the day ;o)

Cheers

[adrien]

Hi

Sounds like something is stopping WinGate from starting up.

We don't stop WinGate from starting even with an invalid or no license, since you need to be able to log in to even enter a license, so it is something else.

I have a sneaking suspicion that it is your history files that are stopping WinGate from starting. If you try deleting the files History.dbf and History.cdx from the WinGate directory, then see if it will start.

Regards

Adrien

[St_Jammy]

If you try deleting the files History.dbf and History.cdx from the WinGate directory, then see if it will start.

Regards

Adrien

Hi guys, I tried what Adrien suggested. No dice :o(

I've also had a go at what Pascal suggested. I have screen shot of what "netstat" shows for WG 5.05 (The first version of WG that I cannot logon to GateKeeper.)

I have also re-created the Remote Control Session as per Pascal's instructions. That to didn't work :o(

The only bit I haven't tried yet is to export the WinGate registry setup. Basically because I'm not sure what I need to do here. So a bit of advice would be apprieciated :o)

Cheers.

P.S. I know I said I'd do this tonight (my time), but I'm actually full of cold at the moment and decided to skip school today ;o)

[Pascal]

The WinGate Engine is started, correct ? What OS are you running ?

Note: Any editing to registry (We're not editing though) should only be done after you have an appropriate backup / system restore point set.

To export the registry, open RegEdit. Navigate to HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate. Select "Registry" from the menu, then "Export Registry File". Save that file somewhere, and email it to me.

[St_Jammy]

Yes, the WinGate engine is started. I cannot logon to GateKeeper.

My OS is Win2000 Prof SP3 (Build 2195)

I will do as you ask re: the registry. I'll need to install a newer version of WG first, export the reg and then re-install WG 5.02 in order for me to contact you again! Phew... what a pain in the backside!

To Be Continued...