Wingate 5 with outgoing Microsoft VPN inoperable

[andrewclark]

I used to run MS VPN successfully through Wingate (V4) from my client laptop machine.

Since upgrading to V5 none of my MS VPN connections on the laptop work any more - they just eventually time out without connecting.

However VPN connects successfully enough from the Wingate Server machine.

Do I have to explicitly open Ports/Protocols on this version or is there something else causing this?

One other point - I don't use the Wingate VPN after encountering problems with V1, though it is still installed, with the trial licence timed out.

Any advice appreciated.

Regards
Andrew

[labull]

Andrew,

This is a known issue. I believe someone said it would be fixed it the next release.

Larry

[andrewclark]

Larry

The story of the IT industry - Upgrade now and break everything that works!

Thanks for taking the time to reply.

Anyone at Wingate Development care to comment/update us?

Regds
Andrew

[tim]

Larry
The story of the IT industry - Upgrade now and break everything that works!
Thanks for taking the time to reply.
Anyone at Wingate Development care to comment/update us?

Hi, this is Anyone :-),
We have built and are currently testing WinGate 5.2. This fixes the VPN through firewall issue that you have, plus a number of other improvements.
We may be able to release this today assuming all goes well with testing, so far it has!

Tim

[andrewclark]

Tim

Thanks for the speedy reply!

I just checked the Wingate Home Page for any sign of 5.2, but I guess you are still testing it.

Regards
Andrew

[adrien]

it's there now, for about 2 hours.

[tjgulman]

I've installed 5.2 but when I run MS VPN from my company portable connected to my local network I get an "opening port..." message on the portable.

The NAT connection disappears from the gatekeeper activity window at the same time as this message comes up.

As far as I can tell, the MS VPN uses all default values apart from the VPN server to connect to.


I tried this in 5.0.7 and had the same problem. I removed that version before I installed 5.2. I took all defaults during installation, so Wingate should be clean.

Any ideas what is going on?

[labull]

Do you have port 1723 open in the firewall?

Larry

[andrewclark]

I've installed 5.2 but when I run MS VPN from my company portable connected to my local network I get an "opening port..." message on the portable.

The NAT connection disappears from the gatekeeper activity window at the same time as this message comes up.

As far as I can tell, the MS VPN uses all default values apart from the VPN server to connect to.

I tried this in 5.0.7 and had the same problem. I removed that version before I installed 5.2. I took all defaults during installation, so Wingate should be clean.

Any ideas what is going on?

I installed 5.2 and tested it today from my laptop thru WG on my server. It worked fine, as it used to before they broke it!

Only change from "default" MS settings I have is to deselect MS CHAP and make sure MS CHAP Version 2 is selected. This depends on your server but it doesn't like both.

I am not an expert in VPNs but can confirm it is now working in WG 5.2.

[tjgulman]

[quote="labull"]Do you have port 1723 open in the firewall?

Larry[/quote]
I've had the firewall set to medium and the security settings show that ports 1024 - 4096 are set to allow in both directions. I've also tested with the firewall disabled. In both cases I still get the "opening port' message. Is there any else I should be doing?

Tom

[tjgulman]

[quote="andrewclark"][quote="tjgulman"]I've installed 5.2 but when I run MS VPN from my company portable connected to my local network I get an "opening port..." message on the portable.

The NAT connection disappears from the gatekeeper activity window at the same time as this message comes up.

As far as I can tell, the MS VPN uses all default values apart from the VPN server to connect to.

I tried this in 5.0.7 and had the same problem. I removed that version before I installed 5.2. I took all defaults during installation, so Wingate should be clean.

Any ideas what is going on?[/quote]

I installed 5.2 and tested it today from my laptop thru WG on my server. It worked fine, as it used to before they broke it!

Only change from "default" MS settings I have is to deselect MS CHAP and make sure MS CHAP Version 2 is selected. This depends on your server but it doesn't like both.

I am not an expert in VPNs but can confirm it is now working in WG 5.2.[/quote]

I've checked this setting, but my company using smart cards to authenticate so the "Use Extensible Authentication Protocol" is set rather than "Allow these protocols". Anyone have any idea if this might be causing the problem.

I have plugged the portable directly into the DSL modem (by unplugging the wingate server) and then I can VPN successfully. This points the problem to the Wingate software in my opinion.

Tom

[labull]

I am able to make an MS VPN connection through WinGate 5.2.

I am using PPTP - not IPSec.

Now, I can't get anywhere on the remote network but I don't think that's a WinGate problem.

Larry