VPN tunneling no longer works in 5.1

[ChadRA]

I have been using Wingate since v2, and once the v4? allowed VPN tunneling I have never been happier with a sofware product. Sure, occasionally bugs creep in, but as a software developer I understand things happen and no one can ever test every possible situation.

I installed v5.1 a couple days ago, and found that everything that I use still seems to work great <except> for the VPN tunneling. With v5.07 I would initiate a VPN connection from a Win2K pro machine to my work, which uses a Cisco VPN router to allow external connections. Now when I do this I can see in the GateKeeper activity log my machine using NAT to connect to the Cisco router, but then in the System messages I can see "Authentication failed - user Guest on 0.0.0.0 requested NATlink" which I believe to be the response from the router to complete the NATlink to my initial request.

If anyone knows of a setting that may have changed between v5.07 and 5.1, or if it seems I am doing something incorrect please let me know. Or if I have left out any details required that would help in tracking down what is preventing the VPN tunneling to work properly please let me know.

Thanks,
Chad.

[saubrey]

I have a similar problem that may provide additional details to help Qbik fix this issue. I use a dial up modem and now that I have upgraded to 5.1.0, when a client computer uses Cisco VPN tunnleing to connect to a Cisco VPN server at work, Wingate causes my modem to hang up in almost exactly 10 minutes...which just happens to be the "idle time out" that I've configured within Wingate to hang up the modem. The problem is that the modem hasn't been idle for 10 mintues it has been in constant use. It is as if Wingate doesn't detect that the modem has activity when using a NAT TCP connection. (I've configured my client Cisco VPN software to use TCP tunnling on port 10000). This problem did not occur in 5.07 or previous versions. I have Transparent redirection thru www proxy. Thanks, Steve