'Fraid not. See this from the ASL Known Issues List:
ID598 o 4.008 Incoming PPTP connections may fail ------------------------------------------------ Description: Some incoming PPTP connections may fail due to a problem in one of the kernel-nat-modules Workaround: --- Fix: ---
I attemped a connection at 10:34pm EDT using the username "jimmtest"
I got as far as "Authenticating username and passwod" at which point it failed. I got the 619 error.
If I attempt to connect to my own VPN and use a bad password I get a window asking for username and password.
Dump Zone Alarm (this is not just my advice, I've read other articles about ZA). I use Kerio 2.1.5 on all my machines and have ZERO issues.
Kerio shows the application that attempts an outbound connection with protocol 47 (used for PPTP) when I try to establish a VPN connection to my ASL as "tcpip kernel driver".
What kind of hardware are you running this on?
Are you geting something like this in your PPTP Roadwarior logs? GRE: read(fd=5,buffer=804d5a0,len=8196) from PTY failed: status = -1 error = Input/output error PTY read or GRE write failed (pty,gre)=(5,6) CTRL: Closing child BCrelay with pid 0 CTRL: Closing child ppp with pid 6584 CTRL: Client 64.83.8.216 control connection finished
There is no executable; it is part of the OS (remember? they wanted to be clever and get away from modular design after the court case)
So you can try opening ports for either the Services and Controller, or SvcHost.
I have a 4X version of Zone that appears to know how to handle Windows PPTP connections; I remember older versions of Zone could not (and PGP queries for Email were problematic too!!)
What you did is exactly what I would have fallen back to.
Oct 14 21:14:29 (none) pptpd[11191]: GRE: read(fd=5,buffer=804dbe0,len=8196) from PTY failed: status = -1 error =
Input/output error
Oct 14 21:14:29 (none) pptpd[11191]: CTRL: PTY read or GRE write failed (pty,gre)=(5,6)
Oct 14 21:14:29 (none) pptpd[11191]: CTRL: Closing child ppp with pid 11192
Oct 14 21:14:29 (none) pptpd[11191]: CTRL: Client 172.16.0.10 control connection finished
Oct 14 21:14:29 (none) pptpd[11191]: CTRL: Exiting now
It's running on an older dell desktop machine (GX1). The nic for the outside interface is a 309x 3Com onboard network adapter.
I haven't tried to connect to the external interface. I am using PPTP for securing my wireless connection. I try to connect from work today and see how it goes. I'll also check out kerio.
I tried to connect to the external interface and I get the same error you do as well. When connecting at home on an interface that is designated as a wireless DMZ it works fine. the card is a linksys. I'm not sure which model. It's the same one they are selling at bestbuy. Is there an issue with the 3Com card?
AppSec:
I know services is set to allow. I got tired of it complaining all the time. I'll check the other two and see what I can come up with.
I get those errors once in a while. I guess sometimes connecting to VPN is a little flaky (rarely). When it does decide to act up, those are the errors I get. For the most part, It's reliable. I only use it to connect to for remote administration of internal computers. I'm using an old IBM PC300XL, PII-400, 128 MB RAM with an Intel onboard NIC, RTL-8139, and a 3C905 (I think). I.d like to get this straightened out. I guess Dan Martin's suggestion of staying with 4.007 is a good idea until you get other, configuration related, issues resolved. Can someone from ASL pop in here with some advice on the posted error text?
Perhaps I spoke (or wrote) too soon. I was VPNed to my home network and all was working fine. My connection got dropped and cannot get re-established. I always blamed it on other things, but this is rediculous. As soon as I can get reconnected, I'll post the logs.
Is this an issue that Astaro is looking into?
Usually it works and then it gets flaky sometimes.
Perhaps I'll set up another ASL machine (4.007) behind my DSL router to handle VPN connections until my primary ASL (4.015) gets the next Up2Date.
I recant my prior statements that my VPN works fine.
You got it! It's unstable!! It will work reliably for a long time for a few users, and then one day it goes up and whoop! Not working. Reboot of the client (as windows tells you to do) does not help!! Try permutations of MS's advanced PPTP settings -might work once, then it stops working. This is a job for tcpdump! Anybody wanting to trade notes on the dump analysis offline, let me know (I think that will be a bit much for this board!).
I was reading a post elsewhere where other Linuxes are having this problem too (reliably interoperating with Windows PPTP). I am slated to really start chopping away at the problem for a client. A key tool I will be using is pptp ping (a Windows utility).
One guy (on Debian?) said it required a number of MS-CHAP patches for Linux, and he had to recompile the kernel. The first thing I will try though is a step-down to 4.007 (!). If that fixes it, I know where to look for the problem (what in the patches throws things a-kilter??)
Never was able to reconnect last night. Sometimes it would go as far as "Connecting to home_vpn", other times it would hang at "authenticating username and password".
Never was able to reconnect last night. Sometimes it would go as far as "Connecting to home_vpn", other times it would hang at "authenticating username and password".
