Hello everybody. I just encountered some problem that is killing me. For some reason, I need to do VPN connection for Internet in my new office. The problem is, the VPN is L2TP without IPSec. I tried to simply clear the machine certificate section in the VPN settings, but that will just give me error about "missing machine certificate". So, does anyone have an idea how to do that or is it simply impossible? Tons of thanks in advance!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac VPN: L2TP without IPSec...
- Thread starter fatfatwolf
- Start date
- Sort by reaction score
It totally depends on how your network is set up. It sounds like you need to generate a certificate somehow. I'd find another Mac user hanging around and ask them how they got set up the first time.
For my corporate network, I have to go through a Windows box to generate the certificate I need. But yours might be different, so you're probably going to have to ask around.
For my corporate network, I have to go through a Windows box to generate the certificate I need. But yours might be different, so you're probably going to have to ask around.
Thanks for the reply. But I don't think certificate is the problem I have. The networking center said this VPN does not use IPSec to secure data transfer (which sounds just stupid to me), and if you are using Windows, you actually have to use regedit to disable IPSec to function. The certificate is for IPSec as far as I know, so the only problem I guess is how to disable it in Leopard.
ObDisclaimer: I'm no security expert, so I could be totally wrong here. 
But L2TP is just an extension of PPTP, so create a new VPN connection using PPTP and see if that works.
But L2TP is just an extension of PPTP, so create a new VPN connection using PPTP and see if that works.
ObDisclaimer: I'm no security expert, so I could be totally wrong here.
But L2TP is just an extension of PPTP, so create a new VPN connection using PPTP and see if that works.
Well, I tried that, but it doesn't work...
I have the exact same problem. We have to connect to a company called Crossbridge Solutions to access wireless modems over a vpn. They disable IPSec in the registry and I have not been able for the life of me how to connect using a Mac instead of windows. All you use is the vpn servername, username and password. No certs or shared key.
L2TP without IPsec on Mac
Hi Guys Iam having problems connecting my macbook pro through a VPN using L2TP without Ipsec. Ipsec is suppressed for Windows... and works fine on windows. However I cannot connect using mac because it keeps asking for a preshared key? CAN ANY ONE HELP PLEASE?
Hi Guys Iam having problems connecting my macbook pro through a VPN using L2TP without Ipsec. Ipsec is suppressed for Windows... and works fine on windows. However I cannot connect using mac because it keeps asking for a preshared key? CAN ANY ONE HELP PLEASE?
It would be much more helpful if you posted the exact message mac os x is giving you when you cant connect.
However if this is for work, then its up to your IT dept to sort it out.
The issue you may well be having is that Mac OS X requires forced encryption when connecting to a VPN, however if the VPN hasnt been set up as such then you may have issues connecting. I set up a PPTP vpn on a ddwrt router. The router as default however does not require encryption, so I had to use a command line on the linux ddwrt router in order to change the settings file on the router itself. This was giving me a similar certifcate error before i did the change.
However if this is for work, then its up to your IT dept to sort it out.
The issue you may well be having is that Mac OS X requires forced encryption when connecting to a VPN, however if the VPN hasnt been set up as such then you may have issues connecting. I set up a PPTP vpn on a ddwrt router. The router as default however does not require encryption, so I had to use a command line on the linux ddwrt router in order to change the settings file on the router itself. This was giving me a similar certifcate error before i did the change.