Previous 1 2 3 4 Next 82 Replies Latest reply: Jan 7, 2014 1:55 AM by healeydave Go to original post
  • AEMM Level 1 Level 1

    same issue here

  • Emilio Graveran Level 1 Level 1

    I can't connect locally or out on the public internet. One thing I did see is that my Mavericks machines can connect to a ML Server without any issue.


    I tried to remove the VPN ports and let Mavericks Server add it's own VPN port numbers and still nothing.


    I'm with someone else thinking that it's a new firewall issue or something. Wish Apple would chime in on this or send out a patch.

  • _cpo_ Level 1 Level 1

    same here for me, vpn simply not working.


    osx server stability is really bad - I never had a completely functioning environment since 10.6 anymore. this is really ridiculous for a so called "server software". and I paid for it once more.

  • fseyler Level 1 Level 1

    On the VPN Client put de local IP VPN Server ( and will connect. Actually it is a firewall problem, it's my opinion.

  • grumpytorpor Level 1 Level 1

    It isn't a firewall problem, exactly.  Admins with this problem (including myself) have reported switching back to ML Server and everything working properly, no firewall adjustments needed.  Given the volume of people reporting this problem and lack of solutions, it seems that something about Server 3.0 doesn't behave according to the L2TP specification and ends up being blocked by firewalls which are correctly configured for L2TP traffic.


    I have many networks with OS X Server VPN service functioning as the portal in.  They variously run SL Server and ML Server without problem.  It's only when I started this test network to check out Mavericks Server that I saw this problem.  The settings on the test machine's Mavericks partition are *exactly* the same as the ML partition and yet the Mavericks partition can only open VPN connections for people already inside the network, which is not useful except in very esoteric situations.

  • bfdulock Level 2 Level 2

    I just tested VPN access to a remote Mavericks server and it does work.  Be aware of the following bug:  the VPN menu icon in Mavericks on the client does not show an active connection.  You must view the VPN drop-down menu or open network preferences to see the active connection.


    My setup uses L2TP over IPSec with a Comcast modem and port forwarding.  Both server and client are running Mavericks.



    Bryan Dulock

    Houston, TX

    Apple Consultants Network

  • fseyler Level 1 Level 1

    Grumpy....At absolutely agree with you.


    Bryan.......The L2TP-VPN Server not Response........



  • grumpytorpor Level 1 Level 1

    bfdulock, that's interesting.  Do you just have the standard 3 L2TP ports forwarding: 500, 1701, and 4500?

  • bfdulock Level 2 Level 2

    Yes, those three UDP ports as well as pass-thru for IP-ESP protocol (IP protocol 50, ESP).  It may be that Comcast modems by default have the pass-thru enabled.



    Bryan Dulock

    Houston, TX

    Apple Consultants Network


    Message was edited by: bfdulock

  • fseyler Level 1 Level 1

    if you select PPTP work geat, the problem is L2TP, come on PATCH!!!!

  • Vraiment Level 1 Level 1

    I can connect to PPTP (in the local network, haven tried outside it) but it gives me an authentication error:


    25/10/13 11:38:36.877 pppd[1155]: DSAuth plugin: unsupported authen authority: recved Kerberosv5;;XXXXXXXX@LKDC:SHA1.3C1F3102A3C5684B8F305FFC23F8132F9030C554;LKDC:SHA1.3C1F3102A3C5684B8F305FFC23F8132F9030C554, want ApplePasswordServer


    Any ideas for a fix?

  • tdudley55555 Level 1 Level 1



    Had the boss look at the iCloud and turned off Back to Mac.  Everything was back to normal.   Thank you Egender.

  • _cpo_ Level 1 Level 1

    is just noticed that the vpn service is only listening on ports 500 and 4500:


    lsof -i4 -n -P | grep racoon


    racoon37755       root6u  IPv4 0x8e6f335c5caa21e7  0t0  UDP
    racoon37755       root7u  IPv4 0x8e6f335c5cf0d987  0t0  UDP
    racoon37755       root   12u  IPv4 0x8e6f335c5be31c2f  0t0  UDP
    racoon37755       root   13u  IPv4 0x8e6f335c5cf0db6f  0t0  UDP


    shouldn't it be listening on port 1701 and 1723, too? (no other program is listening on these ports, either)

  • Russell Wittmann Level 2 Level 2

    I can verify that after the upgrade vpn works.  but push mail does not

  • odx Level 1 Level 1

    I can verify the following:


    Mountain Lion Server with Port Forwarding 1701 TCP, 500 UDP and4500 UDP worked.


    L2TP is working when there is no firewall between client and server. (Locally inside the same network)

    With the same ports forwarded L2TP is not working through the firewall.


    PPTP with TCP Port 1723 is working also for Mavericks.


    Any hint how to fix L2TP appreciated!

Previous 1 2 3 4 Next