VPN Works 1st Time then 807

[KenEsq]

I'm using the latest merlin firmware xxx.35 on an Asus AC66U Router

I setup a PPTP VPN to connect with a Win 8.1 client. First connection everything works correctly and the client can be seen in the VPN status list.
If I then disconnect and try to reconnect I get an 807 error. The VPN status list shows no clients
I have 10 IP addresses available for the VPN server.
If I then access the router and click "Apply" on the VPN settings page...which I assume causes the VPN server to restart and then try to connect again it will work.

Is this a bug in the VPN server or my own doing?

Thanks again for the great firmware!

 

[KenEsq]

I guess I could run a script that would restart the VPN server after every disconnection. Anyone have any other thoughts on how to fix this? It's consistent, I have to go to VPN Details and press Apply after every disconnection or Windows VPN client won't connect.

 

[sinshiva]

i guess changes have been made to vpn stuff in recent updates; i've tested both pptp and am running openvpn with no problems on my n66r via merlin 34_2

 

[KenEsq]

i guess changes have been made to vpn stuff in recent updates; i've tested both pptp and am running openvpn with no problems on my n66r via merlin 34_2

I'm pretty sure it's the firmware as I've now run into the same issue with two different clients.

 

[RMerlin]

See if you are able to connect to port 1723 using telnet. If not, then the problem is probably either your DDNS, or your modem firewalling connections.

 

[KenEsq]

So, I am able to connect to the router from the outside through telnet to login, but I can't connect on port 1723.

It wouldn't work if I used my DDNS or the direct IP address.

I'm using a Motorola SB6121 Modem which I own that doesn't appear to have any filtering going on. Comcast and/or Verizon are the ISPs.

It will connect first time, every time from any client. After that I get an error unless I go to the details page and click Apply. If my modem was blocking the port why would resetting the router change that...and why would it work the first time?

I then gave up and just configured and went with OpenVPN which works without issue.

 

[RMerlin]

It will connect first time, every time from any client. After that I get an error unless I go to the details page and click Apply. If my modem was blocking the port why would resetting the router change that...and why would it work the first time?

One reason I could see would be that the PPTP server would crash or somehow terminate itself when the client disconnects. That would be odd as I don't recall anything changing in the PPTP code in the past few months, but I never really kept a close eye on that part of the code.

I then gave up and just configured and went with OpenVPN which works without issue.

To be honest, this is probably for the best. PPTP is something people should be looking at moving away from as it has become quite trivial to crack due to recent weaknesses that were discovered in the last year.

I find it ironic when I see some VPN tunnel providers promoting PPTP support when the main reason people pay for such tunnels is for security (aside from the people looking to obtain an US-based IP).

 

[dssb2213]

So, I am able to connect to the router from the outside through telnet to login, but I can't connect on port 1723.

It wouldn't work if I used my DDNS or the direct IP address.

I'm using a Motorola SB6121 Modem which I own that doesn't appear to have any filtering going on. Comcast and/or Verizon are the ISPs.

It will connect first time, every time from any client. After that I get an error unless I go to the details page and click Apply. If my modem was blocking the port why would resetting the router change that...and why would it work the first time?

I then gave up and just configured and went with OpenVPN which works without issue.

Do you figure out why fw is doing this?

I have encountered the same issue with 380.62 build.