Wingate 8 service ends

[ChadRA]

I've been running v8 for just over a month now and have seen what *could* be quirks.
Twice the Wingate service has "ended unexpectedly" and it looks like a couple crash dump files were produced, could I provide these through the forum or should I open a support ticket?

I have also been having issues with connecting to a VPN server for work, I have to use an AT&T client (from a Linux OS). Everything seems to initially connect ok, but after 80 seconds the connection is dropped. From the detailed information provided from the AT&T client it looks like something ends up not getting received back from the server (SLR record response??), the activity shown in the Wingate console shows the port 443 connection right up until the client disconnects. This could be something in my setup, but I'm not sure what... this used to work under v7. Since I don't connect to work on a regular basis I can't say exactly when it started having issues so it could have started prior to installing v8.

For now I've been bypassing Wingate and using a direct wired connection to my high-speed modem, but this means I can't work from my couch in front of the TV (whaa whaa! ;-)

Thanks,
Chad

[adrien]

Hi Chad

if you could email those wingate_crash_ file to support@wingate.com that would be great, also if you can let us know which build of WinGate 8 you're running (can see this in the modules panel - part of the full version number of the modules, or in the WinGate update panel).

As for the VPN, I wouldn't expect behaviour to be any different for WinGate 8 than it was with 7. We didn't make any significant changes to the WinGate Network driver (couple USB-related fixes only).

Regards

Adrien

[ChadRA]

Hi Adrien,

I was afraid you were going to say that about the VPN, the probelm is that even though my work forces us to use the AT&T client they don't support it on Linux (and they also force me to use Linux as the main OS).

I've sent in the crash dumps, hope they help.

Thanks,
Chad.

[adrien]

Thanks for sending those in.

As for VPN.. I'm wondering what changed then, if it used to work. No change to OS?

Adrien

[ChadRA]

I've been both thinking and working on this VPN issue... along with the Wingate version change my internet provider switched out my modem (actually a 2Wire router) because I was also having service issues which ended up being a line issue.

Tried a few things so far, opening additional ports on both the router and Wingate since I found some doc that indicates part of the VPN authentication process can use UDP ports 500 & 4500 (which I'm certain I didn't do on the previous modem), along with temporarily disabling the Wingate firewall during a connection test. The thing that's really bizarre to me is that once the VPN connection is established using a direct connection to the modem I can unplug this connection and let it switch over to wireless going through Wingate and it continues to work. The AT&T client provides connection logging, and I've compared the logs between one that works and one that fails. Everything looks the same through the connection sequence but once that's done the connection using Wingate just spits out a "VPN program signaled error condition [!Error 248 SSL TCP connection failed(probably due to network problems). Please attempt to reestablish your VPN connection.]" error line.

Maybe I'll create a proper thread for this issue and see if anyone else has come across something like this.

Thanks,
Chad.