Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Cannot Connect PPTP VPN

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    36 Posts 14 Posters 19.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O
      Ozzik
      last edited by

      Hi,
      I have the same bug, but in my case I managed to solve it.
      I have a setup at home, where only one machine (Win7) has to connect via PPTP VPN.
      So I did port forwarding, where anything that goes to PPTP port (TCP/1723) and GRE - goes to the Win7 machine. Firewall rules were added automatically upon the creation of those.

      Also, I had to enable the built-in Win7 firewall rules: allow GRE-In and allow PPTP-In.
      The VPN works.
      Before that I had a 1.2.2 version and everything worked fine. All these steps are new.

      Maybe this will lead you to the the solution.

      P.S. I'm on the October 29-th snapshot.

      1 Reply Last reply Reply Quote 0
      • C
        CryoGenID
        last edited by

        Great workaround, thanks  :D :D :D

        I just had to add the two rules inside pfsense, didn't have to do anything on my Win7-Client…

        It works now  :)

        Hopefully the bug will be resolved soon, then I can remove the rules again...

        Thanks and best regards,

        Chris

        1 Reply Last reply Reply Quote 0
        • S
          safetynet
          last edited by

          Hi,

          thanks for the info and the suggested workaround, not gonna work for me though as we have multiple PC's initiating PPTP connections to different PPTP servers throughout the day.

          Before anyone says anything about the known bug with multiple connections to the same PPTP server not working, this IS NOT the same issue - we can't connect a single client to an external PPTP server, never mind multiple clients to the same one !!

          Think I'll try rolling back to see if that does the trick.

          Thanks

          Jake

          1 Reply Last reply Reply Quote 0
          • E
            erialor
            last edited by

            Updated (from amd64 Oct 28th build to Nov 2nd build) and also (still) experiencing problems connecting to remote PPTP-servers (pfSense PPTP-server disabled) - adding a NAT-rule to route incoming GRE to the IP I try to connect from works for a temp. solution…

            Would prefer something more friendly though ;) especially as I occasionally switch which computer I want to connect from...

            1 Reply Last reply Reply Quote 0
            • W
              woeper
              last edited by

              What is the status of this very annoying problem ?

              1 Reply Last reply Reply Quote 0
              • S
                sparc317
                last edited by

                yes this is incredibly frustrating. Any update on a fix, had a great, stable experience with previous builds but being able to make an outbound PPTP connection is critical for us so very tempted to rollback to 1.2.x until 2.x is ready for the time being.

                currently using 2.0-BETA4 (i386) built on Mon Nov 1 01:27:31 EDT 2010

                was tempted to update to latest but saw people are still having issues

                1 Reply Last reply Reply Quote 0
                • S
                  sparc317
                  last edited by

                  couldn't actually see this reported in redmine.

                  have reported now, http://redmine.pfsense.org/issues/989

                  1 Reply Last reply Reply Quote 0
                  • J
                    Juve
                    last edited by

                    Is there a known workarround (like a kernel parameter)?
                    Do you know where does the bug comes from ? pfSense code or kernel update issue ?

                    Thanks

                    1 Reply Last reply Reply Quote 0
                    • S
                      sparc317
                      last edited by

                      Other people have reported success if they manually forward 1723/tcp and GRE through to an internal IP and then make a connection outbound from the machine with that address. It appears to be the traffic coming back in without an explicit NAT rule that is the issue, so you can't just plug say a laptop in, get an IP via DHCP and establish a PPTP VPN.

                      I was hoping to dig further but in the middle of a big project at the moment, will try add some beef to the PR at somepoint.

                      1 Reply Last reply Reply Quote 0
                      • J
                        Juve
                        last edited by

                        Ok so it seems to be a state tracking problem ?
                        When you watch the logs during a connection attempt (tcpdump -i pflog0 -ttt -n) you can see GRE responses from the outside server being blocked by pf.

                        1 Reply Last reply Reply Quote 0
                        • J
                          Juve
                          last edited by

                          No news neither a clue about this issue ?

                          1 Reply Last reply Reply Quote 0
                          • E
                            eri--
                            last edited by

                            Wait for a new image to get built, just committed the fix.
                            https://rcs.pfsense.org/projects/pfsense-tools/repos/mainline/commits/1c33e5128463d84dcedb71c9480a126dd8a6466e

                            1 Reply Last reply Reply Quote 0
                            • J
                              Juve
                              last edited by

                              will try it asap.
                              Thanks Ermal.

                              1 Reply Last reply Reply Quote 0
                              • T
                                toomeek
                                last edited by

                                Same issue here.
                                Tried to use it with Win2k8 TMG.
                                TMG's gateway is pfSense LAN IP (this is important! without this forwarding doesn't work)
                                Seems it even don't try to connect, just refusing connection with CLOSED:SYN_SENT.
                                Just ignoring firewall rules… or I have missed something in pfSense firewall?
                                Check screenshots attached.

                                EDIT: sorry for information missed: tested on pfSense-2.0-BETA4-20101116-1840-i386.iso
                                EDIT: Thanks for fix for Ticket #989. Will try this as soon new snapshot will be available.

                                pfsense_pptp_redirect.png
                                pfsense_pptp_redirect.png_thumb
                                pfsense_PPTP_firewall.png
                                pfsense_PPTP_firewall.png_thumb
                                pfsense_ppt_diagnostic.png
                                pfsense_ppt_diagnostic.png_thumb
                                pfSense_Windows_TMG_rule.png
                                pfSense_Windows_TMG_rule.png_thumb

                                1 Reply Last reply Reply Quote 0
                                • E
                                  eri--
                                  last edited by

                                  You do not need the gre allowance with latest snaphots.
                                  Your problem is that you do not need to specify the gateway in firewall rules.

                                  1 Reply Last reply Reply Quote 0
                                  • E
                                    erialor
                                    last edited by

                                    Confirming that outgoing PPTP VPN now works w/o incoming GRE-rule - thanks :D

                                    1 Reply Last reply Reply Quote 0
                                    • J
                                      Juve
                                      last edited by

                                      Confirming this too.

                                      Thanks

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        Digital
                                        last edited by

                                        Confirming that PPTP limitations are gone for good :)

                                        Thanks!

                                        ermal: just curious - will there be an OpenBSD pf patch in the future?

                                        1 Reply Last reply Reply Quote 0
                                        • E
                                          eri--
                                          last edited by

                                          You can try yourself.
                                          From my side i am done with OpenBSD folks doing politics.

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            Juve
                                            last edited by

                                            nice reply Ermal  ;)

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.