Switch to full style
Forum for all technical support and trouble shooting of the WinGate VPN.
Post a reply

cannot connect to vpn.

Aug 18 04 7:34 pm

i keep getting a failure to connect by SSL - error code 5. what is this?

Aug 18 04 8:20 pm

It means the SSL layer could not be negotiated. This is normally caused by problems with the certificate or the connection negotiation by SSL. Things to check would be free disk space, the expiry date on your certificate, etc.

http://forums.qbik.com/viewtopic.php?t= ... hlight=ssl
http://forums.qbik.com/viewtopic.php?t=60&highlight=ssl

Aug 19 04 7:23 am

hm. there's definitely plenty of free space on both computer's drives (around 15 GB on one, 80GB on the other.) i haven't messed with the certificate on the server since i upgraded to 6.0, generated a new one, and exported that configuration to the vpn client. this configuration worked fine until the server was rebooted, and i have been unable to access it remotely since.

any other ideas?

[n]

Aug 19 04 10:30 am

Is it still giving the same error message then ?

Aug 19 04 11:28 am

yes. i did all of that before my first post here.

Aug 20 04 8:16 am

tried exporting it again. still doesn't work.

i'm using NTLM authentication for Wingate. isn't this supposed to work with the new version of Wingate VPN?

Aug 20 04 2:02 pm

I'm getting the same error. In addition to the client getting the error code 5, the VPN server is generating a system message of "There was a problem configuring the SSL objects for "XXX VPN" Please verify this VPNs security settings.". I have regenerated the certificate and everything seems to be the same as before my upgrade to version 6.

Brian

Aug 20 04 2:18 pm

Hm. That means it failed to find the certificate / key information. Did you use encryption for the certificate or not ?

Aug 20 04 2:34 pm

I did not use encryption for the Certificate. Do I need to?

Brian

Aug 20 04 2:41 pm

It should not be necessary. By default, however, in version 5.2.3 VPN Certificates were encrypted. (Mail certificates were not) So, any certificates that were migrated will still be encrypted.
Post a reply