-
All replies
-
Helpful answers
-
Nov 7, 2013 7:30 AM in response to mnsaintby FabioFetter,For those who user Junos Pulse: there are a new version (4r6) that is working for me right now.
Hope to help...
Fábio
-
Nov 9, 2013 8:12 AM in response to mnsaintby OffieB,Had a similar problem, after upgrade to Mavericks I could not connect to my companies L2TP VPN. Followed the following suggestions:
- sudo sysctl -w kern.ipc.maxsockbuf=6291456
- restored the file "options" from my TimeMachine back-up in etc/ppp/
Connection to VPN works now, without a restart.
-
Nov 9, 2013 8:14 AM in response to mnsaintby OffieB,The options file only has one line: refuse-chap
-
Nov 9, 2013 8:51 AM in response to OffieBby SewHappy58,Hi everyone,
I too had issues and tried just about anything and everything. I was using the Cisco client that comes with Maverick. Worked great before the upgrade and then all of the sudden nothing. I tried to update some of the files as suggested to no availe. If anything, it made it worst. Finally, Friday, I decided to reinstall Maverick. It took two attempts but finally I got a clean download. Now everything works perfect. Just need exchange client for email to work.
Someone before mentioned that it's possible not all the files were being downloaded correctly, so that's what made me try it.
-
Nov 9, 2013 10:13 AM in response to billcoleby dmaccarn,This worked for me. There was an old setting in /etc/sysctl.conf created by the Apple Broadband Tuner dmg circa 2005.
http://support.apple.com/kb/DL420
Once removed I'm connecting again.
-
Nov 10, 2013 6:46 PM in response to mnsaintby Lime Mojito,You might want to try my respone to the VPN server not working after Mavericks upgrade as there appears to be some changes with how universal plug and play is working with the new Back to my Mac service and your router.
https://discussions.apple.com/message/23740790#23740790
The router changes may fix VPN client issues as well (NAT/T port forwarding).
-
Nov 13, 2013 11:31 AM in response to mnsaintby Michael Rimmer1,The latest server update has fixed my non working VPN server. I tried numerous tips from this thread but none of them worked.
Hopefully the update fixes the rest of the broken servers out there.
-
Nov 13, 2013 11:41 AM in response to Michael Rimmer1by kellentat,There's another thread and I got a working solution from that, do at your own risk!!!!
https://discussions.apple.com/thread/5468992?start=75&tstart=0
-
Nov 16, 2013 4:36 PM in response to mnsaintby dnar,Based on another post I replaced /usr/sbin/racoon with the Mountain Lion Server version from my Time Machine backup and rebooted my Mavericks sever and that fixed the issue of connecting from an external network for me. Assume Apple will fix racoon soon, hopefully :-).
-
Nov 17, 2013 5:38 PM in response to mnsaintby Arvin Bhatnagar,For me the latest OS X Server update did not resolve anything.
Summary of what is happening:
- Setup OS X Server 3.0 Clean (no upgrade)
- Setup VPN (both L2TP and PPTP)
- iOS: Internally L2TP works fine
- iOS: Internally PPTP works fine
- OSX: Internally L2TP works fine
- OSX: Internally PPTP works fine
- iOS: Externally PPTP works fine
- iOS: Externally L2TP does not work
- OSX: Externally PPTP does not work
- OSX: Externally L2TP does not work
Internally == Device is on the local network
Externally == Device is outside the local network
Everybody else experiencing the same thing?
-
Nov 17, 2013 5:42 PM in response to Arvin Bhatnagarby Lime Mojito,I had the same problem - it was an issue with other devices grabbing port 4500 on the router (UPNP and Back to Mac service). 4500 is needed for NAT traversal with L2TP.
See my response further back on this discussion.
-
Nov 17, 2013 6:17 PM in response to Lime Mojitoby Arvin Bhatnagar,I did turn off Back to Mac services and totally reset the Time Capsule.
Am I missing some extra step?
-
Nov 17, 2013 6:25 PM in response to Arvin Bhatnagarby Lime Mojito,Not sure I'm afraid - my fix worked on the Netgear router, not sure about time capsule. A couple of people mentioned that there was no UPNP admin on that router so if you have the same problem I'm not sure how to fix it
PS make sure back to mac is disabled on all devices not just the server. My ipad was actually the one that got the 4500 address on the router that stopped NAT/T going to the server!
-
Nov 17, 2013 6:27 PM in response to Lime Mojitoby Arvin Bhatnagar,I see what you are saying and did do that...perhaps though I did miss one of my many devices. Will be checking that here...thank you!
-
Nov 17, 2013 6:28 PM in response to Lime Mojitoby Lime Mojito,Though once I set up a manual configuration on the router for port forwarding to the server the router stopped giving out 4500 to UPNP, allowing me to let the devices to back to mac again.