Q: VPN not working after upgrading to Mavericks

Ok, I can try that too.

I just double checked that all my Mac's have "Back to my Mac" off...

Well I'm not sure what else you can do.

FYI maybe you can try this (I don't know if its applicable to your Time capsule though).

Disable airport base station back to my mac:

http://support.apple.com/kb/HT3944?viewlocale=en_US&locale=en_US

Thank you...I did do that, but after exporting the config I noticed some related entries. That's why I reset the whole thing to factory defaults.

I just checked all my devices and also set ports 1723, 4500, 1701, 500 all manually. Same results where only PPTP on iOS works externally.

I did contact Apple but they would not help me any further except to note there is a known L2TP issue.

I've been trying to get vpn to work all weekend.  I've  never used it before and thought I just wasn't using the right info but now it seems it's a Maverick problem. 

I certainly don't have a solution, I'm a complete novice in this area, and I'm not digging through any data to try and fix something. 

I just want Apple to know I'm having this problem and I'll get updates when other post to this thread.

I saw this discussion about using OpenVPN to replace Apple's:

https://discussions.apple.com/message/23711942#23711942

Anyone else trying this?

Solved enabling l2tp and pptp option on Server app, creating a NAT of 1723 tcp port. Now, my L2TP vpn work from outside using my iphone or mac.

(i don't understand why....)

I had the same problem after upgrading to Mavericks. Solved it by deleting the profile in system preferences and setting up the L2TP manually like in Snow Leopard & earlier.

Just read on MacRumors.com that 10.9.1 will include a fix for the L2TP problem.

I'm using L2TP, and it works just fine - once you're connected that is.

This may apply to some of the discussion here...or not.

Previously the traffic I want to go through VPN was still registering on my local IP (geographically), despite being connected. There's a bugger of a new checkbox in VPN Advanced Settings: "Send all Traffic through VPN Connection".

I've been having one **** of a time getting this going.  I tried the ML racoon swap, clean install, server.app reinstall...  After all of that, I never checked how my DNS changed.  So I setup my DNS all over again, and now I have VPN. 

I also finally resolved the issue:

- Remove all VPN settings from the devices (iPhone iPad and laptop)

- Setup your VPN with the server app on the server with the public IP adress as host name

- Let the Server app configure your airport or configure your router to forward TCP 1723 and UDP 500, 1701 and 4500 to your server IP adress.

- Click on save configuration profile button in VPN settings of the Server app and mail the .mobileconfig file to your iPad/iPhone.

- Install the settings on your devices and the connection works!

Hope this helps for the most of you. It seems that with the last update of the server app the issue is resolved. It only worked for me when I configured everything from the beginning.

Hello everyone!

I’ve got L2TP VPN working in Mavericks 10.9 and Server App 3.0.0 / 3.0.1.

First things first, who thought it would be a good idea to erase your mac just to fix VPN?!! I just wanted to make clear that you DO NOT have to go to those extremes! It really is quite a simple fix.

Obviously, the standard caveats apply: This is a temporary, unsupported, workaround, and only a suggested idea at that. Again, this workaround is NOT supported by Apple.

Proceed with this workaround on your own equipment at your own risk. And remember the golden rule: Always backup your data!

OK so here goes… copy and paste the following into termini ONE LINE AT A TIME!

cd /tmp
curl -sO http://c5mart.co/mavericks-vpn-fix/racoon.tar.gz
tar -xzvf racoon.tar.gz
rm racoon.tar.gz
sudo chown root:wheel racoon
sudo chmod 555 racoon
if [ ! -f /usr/sbin/racoon.mavericks ]; then sudo mv /usr/sbin/racoon /usr/sbin/racoon.mavericks; fi;
sudo mv racoon /usr/sbin/racoon
sudo killall racoon

This works fine for me and I'm running a OSX Server for my entire office.

…et voilà!

Worked for me too!

Hello msaint.

I removed entirely the file /etc/sysctl.con and rebooted. I now have no problem. Give it a try (with a security copy in your hands, of course).

l

Hello davedavedave.h

Yes, it works perfectly; no need to reboot. The problem is solved

Thank you very much