Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.6: Add NFS Mounts using Disk Utility Network
NFS mounts are now added using Disk Utility. To add a Linux-hosted NFS share on my network, I did the following
  1. Start Disk Utility
  2. Select NFS Mounts from the File menu
  3. Click the plus sign in the lower left corner
  4. Enter in your remote NFS URL info as described
  5. Enter the mount point. If you add it to /Network, then it will show up in the Shared section of Finder, in an entry called All.
  6. If you're using secure ports on your server, then click the Advanced option and enter -P
  7. Click Verify
  8. Save your settings
The NFS mount is now available.
  • Currently 2.45 / 5
  You rated: 4 / 5 (20 votes cast)

10.6: Add NFS Mounts using Disk Utility | 12 comments | Create New Account
Click here to return to the '10.6: Add NFS Mounts using Disk Utility' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.6: Add NFS Mounts using Disk Utility
Authored by: patashnik on Sep 02, '09 08:20:11AM

The method I use is Command-K in Finder (Connect to Server) and enter the NFS-url there (possibly followed by the + button next to the URL field to add it as a favorite). Mountpoints appear in /Volumes/ (and cannot be specified by the user, so the Disk Utility method gives more finegrained control).

[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: thecoleorton on Sep 02, '09 06:57:48PM

any tips on how to connect to a share like so:


the drive letter's throwing me for a loop.


[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: ljharb on Sep 02, '09 10:06:58PM

That looks like a Windows SMB share - this hint is about NFS.

For that one, try hitting command-K in the Finder and smb://username:password@server/path/to/share

Automatic drive letter shares (like c$) should work in this way as well.

[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: timcrawf on Sep 11, '09 09:26:48AM

If anyone can help I would appreciate it. I have an NFS sharepoint being shared by a Tiger server. When i use the method in the hint, or the mount command, I end up with a folder that I cannot access even using sudo. I cannot even run ls -le on it to see the problem. Sandbox shows no ACLs.
Any idea what I am doing wrong?
My url is like this nfs://
and the location is /Volumes/full
It is the /Volumes/full that ends up unreadable

[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: MickPunk on Sep 18, '09 08:59:23AM

Doesn't work for me.

I used to connect on Leopard via cmd+K like this:

In Snow Leopard I cannot.
Using Disk Utility I can mount the directory, but it does not show the content, is not writable and soon dismounts automatically.

[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: benkelly76 on Oct 14, '09 12:09:03PM

I had the same problem with the mount appearing, but being inaccessible. Adding the following to the Advance Mount Parameters in DiskUtility solved the problem for me:


This was connecting to an ubuntu 2008.04 server.

Hope that helps.

[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: PicklePumpers on May 30, '10 11:49:50AM

That's only half of the story. How did you create the NFS share in the first place?

This "hint" is like saying, "OK, to get to Mars first you step out of your space ship and put your foot on the planet Mars." Yeah? Well how did you build the space ship, launch it, travel across the solar system, land, etc. in the first place?

[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: laurel on Jul 01, '11 02:58:20PM

I have tried all the hints here and none work to connect my imac to my linux nfs server. I even downloaded and installed NFS Manager software. This program sees the NFS mounts requested in disk utility, but none of them work. I can use NFS successfully to connect my Sun workstation, and two other linux boxes to the NFS server. I can even get a PC to do the NFS mounts correctly (windoze 7). I tried command K, disk utility, manual mounts, and NFS manager. Any suggestions?

[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: CoolMischa on Dec 28, '11 09:07:39AM

Moin, moin together,

if you set the "insecure" attribute on the server for the share, then your Mac should connect without any problems. A far as I know allows this attribute to connect with to the nfs-server over non-privileged ports (>1024). These ports are used if you are not root to open the connection :-) This helped me in the first step.

Now I got two other problems:
1. Write access is not given on directories below the exported one. The Mac user is not known by the nfs sever, must she?
2. If I set up iptables firewall the nfs mount failed and I donnot know why, because with a Linux client it works. Any ideas are welcome



[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: unixer on May 27, '12 08:53:21PM

I have been attempting to add my nfs mounts via disk utility for awhile now and it always fails, with an error unable to verify server or whatever.
I can mount the nfs shares via the command line and go connect, but not through disk utility. Does anyone have a solution to this?
OSX 10.6.8


[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: Berk on Jun 07, '12 04:37:10PM
I've ran into this before and I see a lot of people having issues with this. I have solved the issue for myself on both 10.6 and 10.7. The issue you are having is with automounted nfs shares and finder. The solution comes with configuration on both the server side and the client side.

Server - OpenSuse 11.4 32-bit
Client - OS X 10.6.8

The Solution:

nfs server configuration

This is what my /etc/exports looks like and an explanation of the options.,:

/Media *(fsid=1,crossmnt,rw,insecure,all_squash,async,no_subtree_check,anonuid=1000)

the fsid=1 and crossmnt may be just a suse thing. I work with a lot of Suse (OpenSuse, SLES, and SLED) systems and I have had to put this in all of them, but I haven't when hosting from ubuntu and whatnot.

The rest of the flags are

rw=read/write, insecure allows for ports beyond 1024 to connect to the share

all_squash allows for all users to access and be treated as the owner of the share (I think this is right, either way I had set the flag this way for it to work for me)

async allows for better performance by allowing the server to respond to requests before any changes made by that request have been comitted to stable storage.

no_subtree_check improves performance. I have never had any issues with this affecting my systems before. More info on all of these can always be found on the man page for nfs.

anonuid=1000. 1000 is the user id of the user that owns the nfs share on my server. This makes it so that all requests appear to the server as if UUID 1000 is writing to the share, regardless of who is actually doing the writing.

Client Setup
1) Created a directory for my nfs share to be mounted at:

#mkdir -p /mnt/nfs/Media

2) mount the nfs share

#sudo mount -t nfs -o resvport /mnt/nfs/Media

Share mounted just fine. Everything worked from terminal. I then fired up 2 finder windows and dragged and copied a file from my mac to the nfs share. It let me drop it there. Hopped on my nfs server to make sure and the file opened just fine.

If you want to mount this share at boot everytime do the following:

1) Open Disk Utility

2) File --> NFS Mounts

3) Click the '+' in the bottom left corner

4) Enter the Remote NFS URL. In my case: nfs://

5) Enter the mount location. Once agian, in my case: /mnt/nfs/Media

6) Click on "Advanced Mount Parameters" and enter "resvport"

7) Verify that you are communicating to the NFS server

8) Save

[ Reply to This | # ]
10.6: Add NFS Mounts using Disk Utility
Authored by: unixer on Jun 14, '12 06:31:07PM

Thanx Berk,
I found my problem was leaving the : in the address field in disk utility, once resolved all drives mounted. Odd that disk utility doesn't pick this up an error.

Thanx again

[ Reply to This | # ]