Yes
I have the same problem with VPN..
I reformat and I did a clean install of Mavericks Server twice, every thing is working (mail, websites, DNS, ) accept when i try to connect my iPad to the server using VPN does not work.
But i can connect using my MacBook Air, so must be an iOS issue.
*** So hopefully Apple will resolve this problem quickly ***
Sigh, L2TP VPN is no longer working on my server Mac now that I've upgraded to Mavericks and the required Server 3.0 ($20, grr).
Both iOS and OS X devices report, "The L2TP-VPN server did not respond."
Other services running on this machine seem to be fine. Unfortunately this is an important one.
Same here. I have been reading the apple discussion boards and some people seem to be having luck with running the VPN over PPTP only and ditching L2TP for the mean time until a proper fix is done.
I would like to try that but am not sure how to go about doing that on iOS? any suggestions?
PPTP is a little less secure than L2TP, but iOS supports it. Set-up is very similar to setting up the L2TP connection on those devices. Just select the "PPTP" tab.
Having said that... I'm not having luck logging in remotely via PPTP either after enabling it on the server and restarting the VPN process. But the error message is different: instead of a timeout, I'm getting an authentication error. Maybe that's progress. I am assuming the password would be the same as for the L2TP connection so maybe that's my error. Diagnosing...
UPDATE: I'm not seeing any server log entries for my L2TP VPN connect attempts. Still haven't figured out the PPTP authentication issues, but that seems odd..
UPDATE: Lacking time to mess with a clearly under-tested update to OS X Server, I'm reverting to a backup from before my upgrade to Mavericks. I love Mavericks on my laptop but it clearly isn't quite ready for prime time as a server.
I tried PPTP as you have with the exact same results. for L2TP there are no logs either as the server is not even seeing the incoming request.. 🙁
I don't have the time or patience to learn - far more than i need for what i want/need to do - how exactly the server/osx is dealing with VPN connections so i can more effectively troubleshoot.
So i did what many are doing, entrée: Time Machine 😀
SO back to 10.8.5 and the 2.2.2 (or whatever that was) Server app. That being said my MBA is still on 10.9 and it can connect to the 10.8.5 server L2TP no problem…. so…..
Apple what gives….? 😀
It took a little while to restore here (I'm rocking a Time Capsule with four connected USB drives for alternating backups of our various machines here-- a solution which works brilliantly) and the server is currently returned to its pre-OS X 10.9/Server 3 configuration and works without issue.
I fired off an email via Apple's support web form (http://www.apple.com/support/mac/app-store/) describing the problem and requesting a refund of my $20. The VPN is mission critical here and I spent entirely too much time fussing around trying to make it work. I'd used a Linux server before, and went OS X Server precisely to avoid these opaque issues where various chicken-sacrifices and entrail-readings must be performed to get things working. I've found OS X Server to be mostly better than that, but it's hardly a panacea. Networking is not kiddie stuff, I understand, but there's little excuse for what we on this thread have gone through.
sysctl -a|grep maxsockbuf
sudo sysctl -w kern.ipc.maxsockbuf=1000000
It seems that changing the max socket buffer size in osx solves the problem. At least, it worked for me.
Here are the commands. The first one gives the current value while the second one sets it to a highe value.
Code:sysctl -a|grep maxsockbufCode:sudo sysctl -w kern.ipc.maxsockbuf=1000000
Source
Edit: worked only once here. Tried with higher values, no success.
# IPv4/v6 addresses
# 10.160.94.3 asecretkeygoeshere
# 172.16.1.133 asecretkeygoeshere
# 3ffe:501:410:ffff:200:86ff:fe05:80fa asecretkeygoeshere
# 3ffe:501:410:ffff:210:4bff:fea2:8baa asecretkeygoeshere
# USER_FQDN
# macuser@localhost somethingsecret
# FQDN
# kame hoge
Just did a clean install of Mavericks on my MacBook Pro, Late 2008. I skipped signing in to iCloud or any other services and avoided made no other changes to settings. I installed Server 3.0 and configured only VPN for L2TP and PPTP. Problem persists. A packet trace on the client device shows the device is indeed receiving the IKE Phase 1 packet from the server, however it appears to ignore it or otherwise finds it to be invalid.
The strange thing that I have found is what is in /private/etc/racoon/psk.txt file:
Code:# IPv4/v6 addresses # 10.160.94.3 asecretkeygoeshere # 172.16.1.133 asecretkeygoeshere # 3ffe:501:410:ffff:200:86ff:fe05:80fa asecretkeygoeshere # 3ffe:501:410:ffff:210:4bff:fea2:8baa asecretkeygoeshere # USER_FQDN # macuser@localhost somethingsecret # FQDN # kame hoge
First, I obviously did not make the pre-shared key "asecretgoeshere" and the other IPs in this file do not refer to my network at all. It is my understanding, based on the information in /private/etc/racoon/racoon.conf, psk.txt is the file that is looked at when checking for the PSK. Every line in the PSK file is commented out with #. So what is going on here?
I already restored from Time Machine Backup. Sorry I didn't see your request to run that command in terminal beforehand. This is what I see right now:
Code:Gerus-MacBook-Pro:~ geru$ sysctl -a|grep maxsockbuf kern.ipc.maxsockbuf: 4194304
kern.ipc.maxsockbuf: 4194304
31.10.13 18:14:10,961 racoon: Received retransmitted packet from ...IP...[500].
31.10.13 18:14:13,965 racoon: IKE Packet: transmit success. (Phase1 Retransmit).
31.10.13 18:14:14,256 racoon: Received retransmitted packet from ...IP...[500].
31.10.13 18:14:16,259 racoon: IKE Packet: transmit success. (Phase1 Retransmit).
31.10.13 18:14:17,487 racoon: Received retransmitted packet from ...IP...[500].
31.10.13 18:14:28,497 racoon: IKE Packet: transmit success. (Phase1 Retransmit).
31.10.13 18:14:30,413 racoon: Received retransmitted packet from ...IP...[500].