Currently Being ModeratedJan 7, 2012 8:01 AM (in response to Mike Mackovitch)
The only item between the clients and server at the present time is a gigabit switch.
Are there any particular NFS options that OS X clients would require? I've recently seen mention that the server needs to support both privileged and unprivileged ports. I'm working to verify that on the Solaris server at the present moment.
One other thing I will mention is that after installing the 10.7.2 update and a reboot I can perform the mount, and get a directory listing, but copying a file is almost out of the question. I've tried the mount with each version of NFS, showing no behavioral differences between them.
Just wanted to report back that I just found a way to successfuly mount & use my NFS share!!!
Check out the following article:
I followed this article, used Disk Utility to define/mount the NFS share with the following options:
And for the local path I used /Network/share_name so that it will show up in the finder under:
Devices -> Name of my MacBook Pro -> Network
Please let me know if this works for you as well?
I appreciate your reply. I hadn't come up with a decent solution and ran out of time to troubleshoot. I'm now revisiting using NFS in my environment and tested your solution. Finder works spectacularly when giving the mount the nolockd option.
Very tanks! I mount NFS shares from a Seagate BlackArmor NAS and after passing these parameters the Finder stopped showing interrupted server connections error! On Mac OS 10.8.2 dont have more NFS Mount menu on Disk Utility ... but I use terminal command line: sudo mount -t nfs -o sec=sys,nolock,noresvport,inet,soft,intr,timeo=900,retrans=3,proto=tcp [SERVER]:/DataVolume/[SHARE] /Volumes/[LOCAL_MOUNT]
Now I will look for folder owner problem on mounted folders. Tanks again!