Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Does the built-in VPN client connect to SonicWALL?

share|improve this question
What VPN protocol does your device use? – Gerry Jul 27 '12 at 9:59

"The client side is set up in the usual fashion" - I've had different results due to Firewall Unique Identifier. At least on a Mac OS X 10.8 client.

The SonicWall configuration guide (Equinox document SonicOS_Standard-6-EN.pdf) clearly states a need for Firewall Unique Identifier. It's "Item 1" in things to write down and have users enter into the client software.

Firewall Unique Identifier appears to be a non-standard extension (its not discussed in RFC 2409). Fortunately, Equinox sells VPN Tracker Personal for $130. I believe that's known as Vendor Lock In.

share|improve this answer

Yes you can set up the sonnicwall to work with the built in L2TP vpn client. You are a little short on config options but it works for most setups. You have to leave the WANGroup profile on the sonnicwall as standard for its ipsec setup. You need to make note of your shared secret for the WANGroup profile.

Then turn on the L2TP vpn section on the sonnicwall. Set up a local ip address range for the l2tp users and make them of a group that has access. (trusteed users is a good default) Next in the PPP tab of l2tp setup please make sure MSCHAPV2 is at the top of the lists.

The client side is set up in the usual fashion. Should work fine.

In the client console if you see that Phase1 is not connecting check your shared secret.

If you need to change the WANGroup profile to work with other ipsec clients then you will not be able to make it work. In that case you may be better working with the ipsecuritas software on the mac.

Hope that helps.

share|improve this answer
It did not work for me when I had MSCHAPV2 first on the SonicWALL (error: MS-CHAPv2 mutual authentication failed). Once I moved CHAP before MSCHAPV2 it worked. My client is Mac OS X 10.8 – Daniel Jan 14 '14 at 20:55

While I cannot definitively say for every model of Sonicwall, it's unlikely. L2TP over IPSec is(and has been) available, I've never heard of Sonicwall being able to take advantage of that built-in configuration. You may know all of the following, but I'm throwing it out there anyway:

There have been three ways to connect to Sonicwall as VPN gateways in the past: the free IPSecuritas, the (paid) 3rd Party VPNTracker, or the (free) Java-based NetExtender SSL-VPN client that Sonicwall provides for some models that never was particularly optimized for a mac experience, but had basic functionality.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.