VPN

There’s nothing that can make setting up VPN (Virtual Private Networking, which allows access to your network from other networks) truly simple, but Lion Server includes an L2TP VPN host that tries very hard - flip the switch, set a password, and determine what IP addresses will be used for connecting clients. By default, it takes 30 addresses from the high 200s, addresses that are unlikely to be in use on a small network. Make sure that your IP settings won’t conflict with addresses used by local clients.

If you need to provide PPTP VPN to your clients, you can also set this up via the Terminal (PPTP is hidden by default because, in short, it’s unencypted - Apple only wants you to use the more secure L2TP if possible. More about L2TP and PPTP can be found here).

You’ll also need to make sure that your router is configured to forward the correct ports - I can tell you that, according to Apple’s list of ports used by OS X, the VPN service uses UDP 500, UDP 1701, TCP 1723, and UDP 4500, and I can tell you that this site is a good resource to use if you’re new to port forwarding. You’re on your own for the rest.



From here, you can setup clients to connect manually, or save a mobile configuration profile that can be used by Lion and iOS clients. Both OS X and iOS have their own built-in VPN clients that can use these profiles, and any Windows client that supports L2TP (or PPTP, if it’s enabled) should be able to connect as well.

VPN is a service that can be very useful in multiple settings, whether you’re a business user who needs access to files or systems from home, or a home user who wants to be able to remote into their home computer from work or a public Wi-Fi hotspot. While it does take some intermediate skills to setup, Lion Server’s VPN solution is relatively simple and sufficiently functional to serve most purposes.
 

Web

 
Many services in Lion Server have been simplified or streamlined relative to their Snow Leopard Server counterparts, but of everything we’ve looked at so far, the Web service is the only one that has truly been changed for the worse.

Configurable only via Server.app, the Web service (which uses an Apache backend) allows you to create multiple websites with customizable domain names, port numbers, and access permissions, and you’re also given the option to choose where the files are stored on the server.

The bad news is that if you need to do anything more advanced than that, you have to leave the warm comfort of the GUI and dive straight into TextEdit editing of configuration files. From Lion Server’s Help file:

“Web service uses Apache server. You can customize Apache settings by editing configuration files or creating web app plist files.”

Hardly user-friendly.

This is a far cry from the Web service in Snow Leopard server, which gave you a GUI for enabling and disabling modules, setting up aliases, and other advanced functionality. Comparatively speaking, Web server in Lion seems mostly content to provide a backend for things like Wiki, Mail, iCal and Profile Manager without doing a whole lot by itself.

It’s frustrating to see Apple do this to one of its services, especially when (for example) the Mail service maintains both its simplified Server.app administration panel and its advanced Server Admin counterpart. Advanced controls for the Web service already existed in Server Admin prior to Lion, and keeping them would have required little extra work on Apple’s part. Now, if you make heavy use of the Web service in your organization, you’re going to have to tool around in Terminal to perform many advanced functions, which runs counter to the simplification present in most of the other services.
 

Wiki

The Wiki service is similarly simplified in Lion, at least as far as Server.app is concerned - you can turn it on/off and manage what users can make wikis, but that’s just about it.

The meat of the Wiki service is accessed via your web browser, where users with the appropriate permissions can both create personal wiki entries and create new general-use wikis.

I’m not a particularly authoritative source on wiki software, so I’m not really comfortable comparing the Wiki service in Lion Server to other Wiki products, but I can say that the Lion service seems to do the job reasonably well as long as you're not doing anything too advanced. The appeal for a small business is that Wiki is a simple-to-setup service that can host easily-edited internal documentation, or perhaps information and progress reports on ongoing projects, or maybe even meeting notes - the service is there to use, but as always your wiki is only as good as the information you put into it.

Podcast and Time Machine Server Admin Tools: DHCP, DNS, Firewall, NAT, and RADIUS
Comments Locked

77 Comments

View All Comments

  • the_engineer - Thursday, August 4, 2011 - link

    Indeed, and that's the plan, assuming nothing else I like more comes along. I was really sort of tantalized by the possibility of software RAID in OSX, and still haven't been able to get a straight answer on it. Currently it is looking like it's a no go.
  • tff - Tuesday, August 2, 2011 - link

    As a home user, I've been frustrated by the inability to have two users edit a shared calendar in OS X/iOS without using 3rd party software.

    How would it differ using Lion server to accomplish this rather than Lion and iOS 5 clients using iCloud?

    Typical Mac home user- iPhones, iPads, Mac laptops.
  • Omegabet - Tuesday, August 2, 2011 - link

    You can install server.app on a client. Just copy the app over from the server. The first time you launch it, choose connect to a server. It will then run server.app from your client. Otherwise it will upgrade lion to the server version. This was recommended in the apple documentation (can't remember where though).
  • qiankun - Tuesday, August 2, 2011 - link

    One instance I found frustrating is that non-HSF+ volumes like NTFS and exFat cannot be accessed from other computers using SMB or AFP. You can add the volume to the file sharing list, pick whatever protocol you like, but when you try to access it you'll get an error. Same thing applies to the bootcamp partition.

    I like to use NTFS or exFat on external drives, for simple fact that whenever needed you can simply disconnect them from the mac server and plug into a PC. I know there are software that allows reading HSF+ partitions on windows, but it's not installed everywhere, very unlikely if you want to use the drive on a random computer you or your friend uses.
  • damianrobertjones - Tuesday, August 2, 2011 - link

    Windows Home Server. That's all I have to add.
  • justinf79 - Friday, August 5, 2011 - link

    WHS isn't even in the same league...
  • rs2 - Tuesday, August 2, 2011 - link

    I've used a number of different wiki solutions, and the one included on OS X Server is a toy compared to most other popular wikis. There's just no comparison between the OS X wiki and something like Confluence or MediaWiki.
  • gamoniac - Tuesday, August 2, 2011 - link

    At first glance, this looks impressive, given the price tag and the myriad of features provided. However, the author should note the huge maintenance costs of this at best rudimentary product. Anyone who has used Apache or IIS 7 knows the Lion web server is years away from catching up.

    What good is a cheap product if you have to to spend, say, 40 hours, trying to get something to work. The TCO is too high even at $10/hour, and even for home users.
  • gamoniac - Tuesday, August 2, 2011 - link

    PS: Good article nonetheless. Thank you AT. Keep them coming!
  • repoman27 - Wednesday, August 3, 2011 - link

    What's good about a cheap product with a myriad of features is that if even one or two work as advertised out of the box, it was worth it. If not, you're only out $50. I configured Snow Leopard Client on a MacBook Pro to work as a NetBoot / NetRestore server because I happened to find that functionality useful, and although it was trivial to do so, I'm perfectly inclined to shell out the $50 for Lion Server going forward rather than monkey around with another client version.

    In general, you're right though, it's stupid to cheap out on a capital expenditure and then spend an order of magnitude more trying to get someone who knows what they're doing to make it work.

    Really, though, who doesn't spend at least 40 hours setting up a new server for the first time?

Log in

Don't have an account? Sign up now