Just updated to OS X server 3.0 now VPN is not working

I've just updated to the latest version of Maverick Server (3.01) and have been able to get it working without downgrading to Mountain Lion Racoon.

However, I did need to turn off UPNP on my router. As soon as I turn this back on, I cannot connect again.

I do not have (never had) Back To My Mac on, so this isn't an issue for me.

I'm port forwarding ports 500 (UDP), 1701 (TCP/UDP), 4500 (UDP).

It seems to be a short-term fix for me. Would like to turn UPNP back on my router though. C'mon Apple.

Edit:

Sometimes requires 2 or 3 attempts to connect before it finally does.

Message was edited by: MarkeMark

I have noticed that Mavericks assigns the worng permissions in certain folders. most importantly the user folders. For some reason, the admin user is not able to write to that folder.

I did a clean reinstall, and before recreating users , changed permissions to allow the administrator to wirte to the users folder. All my problems went away!

I also did a permissions repair right after reinstalling mavericks (and before installing server). A lot of stuff is wrong there. Not sure it makes a differnce, but worth a try.

Hi all,

I can confirm now that with OS X Server.app 3.0.1 VPN now works from external connection for my configuration. It did not work with app 3.0.

Hello Haykong,

Did you do anything special? I am trying to connect in with L2TP and the log just shows that it is "Listening for connections..." I can connect with PPTP and my ports (UDP and TCP) are fine, and I am using Server 3.01, all machines are Mavericks.

Thanks!

Bob

No special configuration besides making sure DNS and fqdn is setup right.

Then again my test server is using a static wan ip and not behind a NAT.

It's not working for me after the 3.01 upgrade. I had moved the 10.8 racoon binary and was using that... I reverted back to the Mavericks binary, then did the 3.01 upgrade. No luck.

I put the ML binary back and things are working for me. Ugh.

I have tried a bunch of different config's and it is not working for me. My setup is the server behind an airport extreme. FQDN and DNS appear fine as PPTP works. Ports in Airport Extreme are correct.

How about other's - is it just eribble and I that Server 3.01 is not working for? Please weigh in!

I am also sitting behind an airport extreme, ports are correct -- Obviously since the rollback to the 10.8 binary works just fine.

I upgraded to 3.0.1 and nothing. I rolled it back to the ML raccoon file and it worked perfectly. Thanks to all that found the fix and shared it with us.

Never mind...

So, I upgraded all my machines to 10.9.1, including the Mavericks server. L2TP now works internally for me, but it does not seem to be working externally.

How has it gone for you?

Make sure your Gateway/Firewall isn't blocking the port for L2TP (UDP 1701).

Yea, that port is fine, but thanks for the thought. It makes sense given that I can get in internally, but not externally. I have UDP ports (public and private) set to: 500, 1701, 4500 and TCP ports set to: 1723.

I wonder if 10.9.1 changed a port setting?

Are others VPN'ing in externally with L2TP using Mavericks (not modifying with the Mountain Lion Raccoon) 10.9.1 now? Or is it still broke?

bobgeo, if you have reverted racoon before, 10.9.1 has updated the racoon file once again to system default, so you may have to revert racoon again to make things work.

Looks like there is a VPN Update for OS X Server that just came out. It requires OS X 10.9.1. Installing it myself now.

Good luck to everyone.