I have been using ASL since version 3 and with since Version 5 with the PPTP functionality.
I have a site with a number of PPTP VPN connections that terminate on the ASL v6.303 box. Some connections will not pass authentication. I have previously put this down to the idea the remote end was coming through a NATed firewall or device and were not running a NAT editor, until today.
A user called up and told me another user I configured was connected from inside the remote neywork. The connected user has never had any issues so this did not surprise me. If the problem for the user that could not connect was due to a remote network issue then no one should be able to connect. Clearly you could connect from this remote network.
The logs for the PPTP daemon kept indicating a GRE: bad checksum error and the process would make repeated attempts at authentication but never get past this phase. The client would stay paused at Authenticating Username and Password until the session timed out.
I then port forwarded Port 1723 to a Windows 2003 server running PPTP VPN RAS access internally plus setup a firewall rule to allow the Port 1723 traffic. Miracle of miracles the remote VPN connection that will not connect on the ASL v6.303 boxes connects and authenticates and passes traffic. The PPTP account on the ASL box is enabled for PPTP access, it has an assigned IP address from the PPTP pool.
Why would this be? Some of the threads are suggesting the PPTP daemon is possibly broken. Is this true?
BTW, for those people with the "connecting through the internet via the PPTP
" issue. This is how you really do it.
(1) Uncheck the "use remote gateway" check box in the advanced tab of the PPTP client configuration.
(2) Assign a static IP address for the client on the ASL gateway so you know what it is.
(3) Create a route on the Windows box that is the remote PPTP client for the "internal network" behind the ASL gateway the remote client connects to that uses the PPTP static assigned address as the gateway.
EG Internal LAN is 192.168.0.0 , assign PPTP client IP 10.65.100.5 then on the remote Windows box that connects by PPTP. Works a treat every time and no dropped packets in your ASL logs and no BS NAT rule required on the ASL box either. That is how it is properly done.
route add 192.168.0.0 mask 255.255.255.0 10.65.100.5
This thread was automatically locked due to age.