jrscs wrote:I exported the registery, did an uninstall, reinstalled a fresh copy of 6.2.2, imported the registry back and still have the same issue.
Nothing changed doing a clean install.
Now what?
I also have a server running Windows 98 SE and have just installed 6.2.2 and I get the same symptoms and have tried re-installing, re-activating, etc. So, "Me too!".
However, I can give you a kludge.
It starts with you going back to a version prior to v6.2.2
- make a copy of the pre-v622 "qbikhk98.vxd" eg "qbikhk98-works.vxd"
- install v6.2.2
- shut down Wingate server
- rename qbikhk98.vxd out of the way (eg "qbikhk98-v622.vxd")
- copy back the old qbikhk98.vxd from the backup (I used whatever version was current on 15/11/2006) eg "qbikhk98-v622.vxd" to ""qbikhk98.vxd"
- restart Wingate server
That has been running for me for about an hour and the machines on my network seem to be accessing the 'net OK. In fact, this message is being posted from one of the machines on the network.
I won't be surprised if the server locks up in the next 24 hours... so the usual "don't blame me" disclaimers apply!
ALSO: I have a Windows XP machine on the network that has never been able to access HTTPS (as opposed to http) web pages or anything involving SSL but it now can. So that problem has been fixed in v6.2.2 - at last.