eribble
Level 2 (220 points)

Q: VPN giving me fits.  Help.

Had to do some things with my trudty mac mini that forced me to just start fresh with the OS install.  I am trying to get the VPN services back up and not having any luck. 

 

I am able to connect to the VPN from inside my home, but when coming from the outside, no luck.

 

What are the things I can troubleshoot?  When I connect internally, I can verify the traffic is routed through the server and out to the internet.  I watch the logs and see myself connect.  I have forward the proper ports (500, 1701 and 4500) to the internal IP.  When I try to connect to the server from the outside (via my iPhone) nothing hits the logs.  I use the no-ip dydns service and am able to hit the web server using the no-ip address, so I know I'm showing up out on the internet.

 

Since I am showing up on the logs when trying to access from the outside, I figured it was a port forward issue, but I verified everything is on the airport extreme (and was in there prior to the reinstall).

 

So I'm sort of at a loss...  Any ideas?

Mac mini, OS X Server

Posted on Oct 13, 2013 3:30 PM

Close
eribble

Q: VPN giving me fits.  Help.

  • All replies
  • Helpful answers

Previous Page 2

  • by eribble,

    eribble eribble Oct 23, 2013 4:31 PM in response to haykong
    Level 2 (220 points)
    Oct 23, 2013 4:31 PM in response to haykong

    Hey there...  I've done a clean install of Mavericks and still isn't working.  Based on some other threads, it appears there's a Mavericks issue.

     

    Also, I threw Mountain Lion back on prior to a clean install and the VPN was working.  I must have tweaked something and inadvertantly thought it was an OS issue, when it was me. 

  • by J Henselmans,

    J Henselmans J Henselmans Oct 23, 2013 5:23 PM in response to eribble
    Level 1 (30 points)
    Oct 23, 2013 5:23 PM in response to eribble

    I got PPT working:

     

    I noticed in the log a message that I had seen before, which most of the times meant something for VPNuser (VPN MPPE Key Access User) was hosed.

     

    So I did a vpnaddkeyagentuser -r

    which gave:

    deleting vpn_c9b31d359a02 from /Local/Default

     

    Just to make sure I also did:

    vpnaddkeyagentuser  -r /LDAPv3/127.0.0.1

     

    Enter admin name for node /LDAPv3/127.0.0.1:diradmin

    Password:

    deleting vpn_d6a69097a539 from /LDAPv3/127.0.0.1

    Then I did:

    vpnaddkeyagentuser   /LDAPv3/127.0.0.1

    Enter admin name for node /LDAPv3/127.0.0.1:diradmin

    Password:

     

    Which created a new VPN MPPE Key Access User

     

    After that I could consistently connect to the VPN PPTP connection. Mind you, I only tested it on a local network.

     

    Kind Regards,

    Johan Henselmans

  • by grumpytorpor,

    grumpytorpor grumpytorpor Oct 24, 2013 10:10 AM in response to Engender
    Level 1 (0 points)
    Oct 24, 2013 10:10 AM in response to Engender

    I had high hopes for this suggestion.  Unfortunately, Back to my Mac was disabled (as it should have been), so that wasn't a solution.

  • by grumpytorpor,

    grumpytorpor grumpytorpor Oct 24, 2013 10:40 AM in response to J Henselmans
    Level 1 (0 points)
    Oct 24, 2013 10:40 AM in response to J Henselmans

    I can't speak for others experiencing this problem, but I haven't had problems connecting on a LAN, only through the firewall.  This Mavericks test server is the only network that gives me this problem.

     

    I have seen posts to the effect that PPTP is unaffected, but I have not bothered to test that.  It's not an option for me since we're required to match an existing VPN specification on all of our networks.

     

    I have booted the same machine to a ML Server partition and everything immediately worked as expected, so it is not a firewall configuration problem per se.  It may be that Mavericks' LT2P server is now responding on unexpected ports or in a way that isn't protocol-compliant to be considered VPN traffic by firewalls.

Previous Page 2