Then click on Save and you’re done: you should be able to browse and interact with it as needed. You can see how these shake out in the following screen:Ĭlick on Verify if it looks right and provided that the file system can be properly mounted then you’ll receive a message saying such. For most scenarios, /Volumes/ followed by the name of the mount will suffice. The Mount Location is going to be where on the client computer that you would like the folder to be. The Remote NFS URL: field will be nfs:// followed by the name or IP of your server followed by the name of the mount you just created. Then, click on the File menu and select NFS Mounts… to bring up the NFS Mounts screen.įrom the NFS Mounts screen, click on the plus sign (+) and you will see an overlay with fields for Remote NFS URL: and Mount Location. From a client that can access the NFS server, open Disk Utility from /Applications/Utilities. Now, we need to verify that Mac OS X clients. Next up, let’s port scan for nfs (port 2049) from Mac OS X using the stroke command: Now save and close the file and then run the exportfs command with the -a option (all) and you should be done with the server configuration portion: The above CIDR allows all IP addresses from 192.168.210.1 to 192.168.210.254 to access the export. This could just be one IP address, or it could be a range of IP addresses. In the above line, we’re defining the path to the directory, followed by the address(es) that access the export. To do so, paste this line in at the bottom: Now, let’s open up /etc/exports and allow access to Homes by configuring it as an export. Then we need to define the permissions for /Homes (ends up similar in functionality to the export to option in Server Admin for Mac OS X Server users): Then let’s create a directory to share (aka export): To get started, let’s install the nfs-kernel-server, nfs-common and portmap packages on our Ubuntu 10.04 box:Īpt-get install nfs-kernel-server nfs-common portmap With the release of OS X 10.9 Mavericks, Apple fully supports both SMB2 and AFP. So AFP is the best protocol for all Mac clients through OS X 10.8, SMB is the standard for Windows clients, and NFS is perfect between UNIX servers. Once it’s configured, you use it in a similar fashion as you do in Mac OS X Server. But for the best performance, and 100 compatibility, the native client file sharing protocol is the right choice. It seems that it’s about as old as the hills and while it can be cranky at times, it’s pretty easy to setup, manage and use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |