Menu
For the VPN services in Lion Server, we will only be looking at L2TP, or the Layer 2 Tunneling Protocol. The L2TP server is simple to configure. Simply open the Server application and then click on the VPN service in the SERVICES section of the Server sidebar.
'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 SonicOSStandard-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.
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. 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.
A VPN, or Virtual Private Network, connection on your iPad gives you remote access to a network - and the folders and files on the host computer - using a Wi-Fi or cellular data connection. Creating the VPN configuration and enabling the feature in the Settings menu will not give you immediate file and folder access, however. Because iOS lacks the browsing support of a file manager, you'll also need to install a third-party app that can explore and display the contents of the host server for you. Tips.
Determine your needs before selecting a file management app. Cloud Connect Pro, for example, is the priciest option of the three - $19.99 as of January 2014 - but it features a much larger variety of options. You'll gain access to a variety of services - including Dropbox, local and remote computers, AirPort Disks and FTP.
The app also includes a screen-sharing app, so you can take complete remote control of the host computer. FileBrowser and Remote File Manager are less feature-filled, but come at a lower price point - as of January 2014, FileBrowser was $5.99 and Remote File Manager was $4.99. Both enable remote connections to computers, shared folders and network drives, yet neither support screen sharing.
Remote File Manager also supports cloud access, a feature unsupported by FileBrowser. Failure to connect to the VPN connection - or an alert that tells you 'Shared Secret is missing' - indicates that the current VPN configuration is incorrect or incomplete. Attempt set up again, and if you continue to have problems, consult with your network administrator or IT professional to confirm VPN settings. If you are able to access the VPN but have trouble viewing certain files or folders, file sharing privileges may not be enabled or may be incorrectly configured on the host server.