Cannot export nfs-share over ipv6 in OS X 10.8

I've successfully exported my nfs share over ipv4 and can access this with a nfs-client from a linux machine. However, I'm not able to export the same share over ipv6.
In my /etc/exports I have:
/Volumes/Harddisk
-network 10.0.0.0
-mask 255.255.255.0
/Volumes/Harddisk
-network fd60:760d:98ec:8588::/64
However, from the linux client I can only mount the ipv4 share, but not the ipv6 share.
Is it possible to export nfs-shares over ipv6 in OS X 10.8?

I would suggest testing a connection from a second Mac also running 10.8 via IPv6. At least then you know both will be using compatible versions. If that does not work then it would seem to be an IPv6 issue on the Mac server.

Similar Messages

Windows 2012 R2 - Access problems to NFS shares via IPv6

Hello,
we setup some NFS shares on HNAS storage box. The connection to this storage is only possible over IPv6 network.
My server with Windows 2012 R2 has the feature 'Client for NFS' installed and a 'showmount -e servername/or IPv6 address' works. I can see all shares when i try to open the storagebox in Windows Explorer with the command "\\servername" or "\\IPv6
address", too.
My problem is, when I try to mount the share via "Map network drive" or "mount \\servername\sharename *" I get Error 53 - Network path not found.
The share is configured that every server in the IPv6 subnet could access it and it works on Unix machines, but not on Windows.
It does not matter if i set some option parameters for the "mount" command like sec=sys or anon, everytime error 53.
I don't know, if the share needs special options for Windows. I hope somebody can help.
Kind regards

Hi,
here is the output of your 2 commands:
PS C:\Users\admin> get-SmbConnection
PS C:\Users\admin> get-SmbServerConfiguration
AnnounceServer                  : False
AsynchronousCredits             : 64
AutoShareServer                 : True
AutoShareWorkstation            : True
CachedOpenLimit                 : 0
AnnounceComment                 :
EnableDownlevelTimewarp         : False
EnableLeasing                   : True
EnableMultiChannel              : True
EnableStrictNameChecking        : True
AutoDisconnectTimeout           : 0
DurableHandleV2TimeoutInSeconds : 30
EnableAuthenticateUserSharing   : False
EnableForcedLogoff              : True
EnableOplocks                   : True
EnableSecuritySignature         : True
ServerHidden                    : True
IrpStackSize                    : 15
KeepAliveTime                   : 2
MaxChannelPerSession            : 32
MaxMpxCount                     : 50
MaxSessionPerConnection         : 16384
MaxThreadsPerQueue              : 20
MaxWorkItems                    : 1
NullSessionPipes                : HydraLsPipe
NullSessionShares               :
OplockBreakWait                 : 35
PendingClientTimeoutInSeconds   : 120
RequireSecuritySignature        : False
EnableSMB1Protocol              : True
EnableSMB2Protocol              : False
Smb2CreditsMax                  : 2048
Smb2CreditsMin                  : 128
SmbServerNameHardeningLevel     : 0
TreatHostAsStableStorage        : False
ValidateAliasNotCircular        : True
ValidateShareScope              : True
ValidateShareScopeNotAliased    : True
ValidateTargetName              : True
EncryptData                     : False
RejectUnencryptedAccess         : True
I try to access the file share with Windows Explorer. When I enter \\fe08--babe-face-cafe-dead.ipv6-literal.net (just example), I can see all shares on the storage box. When I double-click the share, I want to access, where an access is definitely allowed,
it takes a while and then the error "\\fe08--babe-face-cafe-dead.ipv6-literal.net\share is not accessable. You might not have permission to use this network resource. ..." appears. Of this action a recorded the trace.
Another way I tried is to open command line an type "mount \\fe08--babe-face-cafe-dead.ipv6-literal.net\share *". After this an error 53 occurs immediately without any wait time.

Cannot mount nfs shares

Hello,
since Sunday I'm unable to mount NFS shares:
mount.nfs: No such device
The server-side is working fine, I can mount all shares from my FreeBSD Desktop machine.
I'm using netcfg and start rpcbind and nfs-common upong connection before mounting NFS shares (via netfs). Is this maybe related to some recent pacman updates? It was working flawless just until Sunday.

As it turns out, It now works. I did load the nfs module manually during my troubleshooting but it was already loaded or built into the kernel or whatever.
The thing that made it work is changing the nfs mount lines in /etc/fstab from the hostname of the server to the ip address of the server. I don't know why that worked on both machines since I could ping the hostname of the nfs server which is a Freenas server and it always worked before.
@ jasonwryan
rc.d start rpcbind && rc.d start nfs-common
start fine after stopped and restarted. Have you replaced portmap with rpcbind in pacman? rpcbind superceded portmap a while back. gl.
@.:B:.
lol, snide remark succesfully detected. In my defense I was half guessing and half sniding (or some percentage thereof). I have to admit I do get a bit snippy over this since nfs is necessary for my little clients to run mpd and I gets a bit cranky when I gots no musics! Fueling my frustration, it seems I have to chase down nfs problems frequently after "pacman -Syu".

Cannot mount NFS shares using the Finder

Hello all!
I have a directory structure on a OpenSuse NFS Server which I like to browse/read using my MAC OSX 10.5.6. It works like a joy when I am mounting the NFS share on the command line using "sudo":
sudo mount -o resvport nfshost:/full/path/NFS/share /My/mount/point
However, this is kind of unconvenient as I need to start Terminal and sudo always asks me for the root password. I would appreciate to mount the NFS share just as I mount afp shares using the Finder. But the NFS share is neither searchable using the Finder nor does it show up in the list of host in the side bar of the Finder.
Does anyone has an idea how to solve that? Thx for your information!

The problem is most likely that your NFS server requires that connections come from reserved ports but you can't connect that way from the Finder GUI.
Your example:
sudo mount -o resvport nfshost:/full/path/NFS/share /My/mount/point
shows that you need to use "-o resvport" and that you need to do the mount as root. (This is because the networking stack requires you to be root to get a reserved port.) When you try to mount it via the Finder, you can't specify any mount options like "-o resvport" and even if you could the mount would fail because the Finder isn't running as root.
My first suggestion would be to change the configuration of your server to not require clients to use reserved ports for the NFS protocol. Unfortunately, Linux chooses to call that option "insecure" even though requiring the use of reserved ports (using "secure") doesn't actually make NFS more secure.
Alternatively, you could configure the mount to be performed by something that does do the mount as root - e.g. automount/autofs. You can do this by configuring the mount on Directory Utility's "Mounts" section... you'll want to add "resvport" to the "Advanced mount options" field.
HTH
--macko

Cannot export or share project error (-50)??

I've made a 4 minutes 31 seconds video and tried to export and exporting through quicktime then this message occurred:
Unable to prepare project for publishing
The project could not be prepared for publishing because an error occurred. (-50)
I've even tried to share via itunes and youtube; still didn't work. I've made only 3 videos in the past and all of them were under 5 minutes long; there's never been any problem exporting or sharing, or even finalizing. I've checked the space on the system, there's still A LOT left. I'm using iMovie version 9.0.4
I did download the most up to date iMovie, however it said that my Mac OS X version is not supported. I'm all out of solutions here...

Thanks Russ. Yes, the frame rate is different. I shoot in 720p 60 and for some reason the output of the smaller file was 29.97p. It Looks good, does it matter if I change the timeline to 29.97? Or should i just shoot in 720p30? I shoot a sports show and stream it on the web. All looks good, but I am trying to keep the file size down a bit, so the smaller bit rate seems to help. I am an old Betacam shooter and still confused by all of the different formats. Any insight will really help. www.northcoastgameoftheweek.com
Best.
Tom

I cannot export or share a ProResLT movie, why?

I have never had this problem before. I exported a 59:00 master from FCP as a ProRes LT movie, but when I try to export said move to an iphone or Apple TV template using the QT player, I get a warning the operation has stopped because file not supported. Even if I try to "share" the movie using any of the share templates, I get the same warning. I tried this with an ProResLT movie and a ProRes 422 movie. I am currently downloading Mountain Lion, maybe that will cure the problem. Any ideas what is going on?
Best.
Tom

Thanks Russ. Yes, the frame rate is different. I shoot in 720p 60 and for some reason the output of the smaller file was 29.97p. It Looks good, does it matter if I change the timeline to 29.97? Or should i just shoot in 720p30? I shoot a sports show and stream it on the web. All looks good, but I am trying to keep the file size down a bit, so the smaller bit rate seems to help. I am an old Betacam shooter and still confused by all of the different formats. Any insight will really help. www.northcoastgameoftheweek.com
Best.
Tom

Cannot search NFS shares using finder

Having connected ubuntu 11.04 NFS4 share, searching in finder apparently doesn't do anything.
Search works fine when the same folder is mounted using SMB or AFP.
Tested using two different OSX machines both running 10.6.8.
Does it work for anyone here?

correction. it's just regulrarly mounted using nfs3.
apparently no one is using nfs here at all

How can a mount a NFS share exported from OpenBSD?

Hello Apple Discussions:
I've been experimenting with NFS in a mixed OS environment, and have been successful exporting nfs share with tigerserver, and mounting it on both a powerpc linux system, and on a powerpc openBSD system.
Likewise, I can export a NFS share from the linux powerpc box, and mount it on the openBSD box and on the tigerserver, although, the latter required using the options (ro,sync,insecure) in my exports file.
However, when I export a share on the OpenBSD box, I can mount it on the linux box, but not on tigerserver.
I would like for the OpenBSD box to export a NFS share securely, with read-write permissions, to the tigerserver.
After reading so many tutorials, that it would be a page of links, just to list them all, I am pulling my hair out. However, I have found one thread that suggests, that perhaps what I'm trying to do is impossible:
http://www.bsdforums.org/forums/showthread.php?t=54308
Here it is suggested that the NFS won't work because tigerserver is not using UTF-8?
I will have to say, that I was somewhat alarmed, that the only times I succeeded in mounting an nfs share exported from linux onto tigerserver, it was when the "insecure" option is used in the /etc/exports file. There doesn't seem to be an equivalent for the linux style exports option "insecure", in the bsd style options of --maproot=user:group1:group2.
But I don't like using any options that say "insecure" anyways, so rather than trying to find out how to make openbsd "insecure", I would rather like to find out if there is a way to get tigerserver using UTF-8, at least when mounting NFS shares, if this is indeed the issue.
Here are the more technical details. I've created a user on all sytems named "fives" with the userid of 5555 and the groupid of 5555. I made the user local user in the local net info domain, but I've tried it with an LDAP user as well. The folders I wish to export and the folders into which to mount them are all owned by user fives and group fives, and have permissions set to 0775. The ip addresses are OpenBSD=192.168.222.111 TigerServer=192.168.222.233 LinuxPPC=192.168.222.253. I've included the relevant NFS setup files and running processes below:
ON THE OPENBSD BOX:
#/etc/exports
/fives -alldirs -network=192.168.222.0 -mask=255.255.255.0
/exports/fives -mapall=fives:fives 192.168.222.233 192.168.222.253
#/etc/hosts.deny
ALL: ALL
#/etc/hosts.allow
ALL: 192.168.222.233 192.168.222.253
#/etc/rc.conf.local
portmap=YES
lockd=YES
nfs_server=YES
#here's proof that the daemons are running on the OpenBSD box;
rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 863 mountd
100005 3 udp 863 mountd
100005 1 tcp 613 mountd
100005 3 tcp 613 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 895 nlockmgr
100021 3 udp 895 nlockmgr
100021 1 tcp 706 nlockmgr
100021 3 tcp 706 nlockmgr
# actually, I don't see statd, but haven't found the equivalent in openbsd. There's rpc.rstatd, and maybe it should be listed here, but there doesn't seem to be a way to launch it directly. This is a competitor with the UTF-8 theory about why it's not working.
ON THE TIGER SERVER:
# here's proof that tiger server sees the mounts:
showmount -e 192.168.222.111
Exports list on 192.168.222.111:
/fives 192.168.222.0
/exports/fives 192.168.222.233 192.168.222.253
# here's the result of user fives' attempt at mounting a share:
sudo mount -t nfs 192.168.222.111:/exports/fives /imports/fives
mount_nfs: /imports/fives: Permission denied
# yet user fives has no problem mounting same share on linuxppc box.
What is different about OSX server? I thought it was supposed to speak NFS?
---argh... I'm steppin out for a pint.. Hopefully when I'm back it'll just work.

One thing not mentioned is that if you decide on the multiple user approach, you can have your music folder in Shared Documents so you only store the tracks once.
Each user is free to choose which of those tracks they want in their library.
There is an Apple help article on multiple users.
http://docs.info.apple.com/article.html?artnum=300432

Export gives "Unable to create" error,Can't EXPORT or SHARE modified images

I am running iPhoto 8.1.2 and I cannot export or share any images I modify.
Upon editing images (cropping or enhancing color profile), I am unable to drag and drop images to my desktop (gives a "∅" symbol) which I used to do all the time. I cannot export them - iPhoto gives an error: "Unable to create" filename error...
If I look at the "Show file" and verify the contents of the folder, none of the images I have modified appear there. If I look at "Show original file" all the original files are there but do not have my edits/cropping, etc. Where are my modified images going and how can I get to them? iPhoto seems like it is getting Alzheimer's or something...
I have tried closing and re-opened iPhoto and all the images thumbnails appear to be ok with my updated crops/enhancements. Double-clicking and opening them opens files with the correct edit/enhancements. Everything seems ok until I try to export or share any of the modified photos.
I tried rebuilding iPhoto and selecting the first 4 options but after the rebuild the problem still persists...
None of the files that I cropped/enhanced appear in the "Modified" folder for that date. There are some files there, but they appear to be files that I deleted!
So, where are my cropped/enhanced photos going??? iPhoto shows them ok in the Events, etc. but they are not in the "Modified" folder and I cannot export, drag/drop, email or share them...
This has been happening to me for awhile now and it is very frustrating. iPhoto is ok so long as I don't do any cropping or enhancing. If I do that, then it gets all screwed up...
I know that I can use something like "iPhoto Library Manager" to rebuild stuff but I don't want to lose any of my data. I have done extensive work with faces, places, attributes, names, etc...
I JUST WANT iPHOTO TO WORK LIKE IT IS SUPPOSED TO AND LIKE IT USED TO!
Thanks,
Steve

Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Include the option to check and repair Library permissions.
If the permissions have been mucked up somehow, it's likely that your edits have not been saved.
If the fails:
Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD

[Error 333] Cannot export movie at all

Hi All,
I have created a new movie using iMovie 8.5 (latest version included in iLife 09).
Unfortunately, when I try to export my first project, after few minutes of processing (the blu progress bar fully completes the process) it gives me an error saying that is Imposssible to export the movie, error 333.
I have not registered yet my iLife, could be that one the reason or could be something else?
To me is so weird, if was the registration it should have been said before..
Thanks a lot
Daniel

Hello,
Are you having a similar problem as this?:
CIRCUMSTANCES:
I have the most recent version of OSX and of FCPX and yet I cannot export or "Share" my timeline's Project.
I have the simplest project (a sequence of small video clips with no effects at all) and the program does not let me "share" anything.
I have been using FCPX since the first week it came out; it's not like I'm completely lost (I have already done many jobs).
DOUBT:
WHY ARE ALL THE SHARE* OPTIONS INACTIVE?
*Either selecting the Project from the browser or clicking directly on the Timeline, the Share options I'm referring to are found on File > Share > ....
ANSWER:
If your Sequence contains one single Clip which was not well imported from the camera, FCPX will not let you "Share" (Export) the Project at all (The timeline's sequence). FCPX is probably wanting to alert you by means of a yellow triangle on the Event's icon, right at the corresponding missbehaving Event. Click on that Event, scroll down through all your clips on the Browser and you will most probably find a clip with the same yellow triangle with exclamation mark.
In order to detect the wrong clip (or clips) on the timeline, you shall click on the timeline you are not able to export (that is, to "Share") and, once you have clicked on the timeline itself, open your "Timeline Index" ( which shortcut is: shift cmd 2 ).
Once in the Timeline Index, click on "Clips" (upper left, under the small search window) and also click on Video (at the bottom of the whole Timeline Index box).
Now you have the whole list of all your clips which are used in the Timeline. Scroll down until you find all the marked clips (they are all marked with the same yellow triangle with an exclamation mark). Eliminate them from either the Timeline Index or directly from the timeline if you want to export anything.
I hope this was helpful to anyone with erroneously imported clips or any misbehaving imported media.

Motion 5. I have a Mac Book Pro and am trying to export my project, but cannot as the SHARE options are all faded out.

I have a Mac Book Pro and am trying to export my project, but cannot as the SHARE options are all faded out. All I am doing is adding text to a movie. It plays back fine in motion.

Hey Adam. Try this link and see if any of the suggestions help: https://discussions.apple.com/thread/5216906?tstart=30

HT5824 I have a shares dealing account and the keychain account number seems to take over the stock codes I input meaning I cannot deal in shares any more. How do I turn that off?

I have a shares dealing account and the keychain account number seems to take over the stock codes I input meaning I cannot deal in shares any more. How do I turn that off?

should I just cry uncle and go to the local genius bar for instructions lol

New files and folders on a Linux client mounting a Windows 2012 Server for NFS share do not inherit Owner and Group when SetGID bit set

Problem statement
When I mount a Windows NFS service file share using UUUA and set the Owner and Group, and set the SetGID bit on the parent folder in a hierarchy. New Files and folders inside and underneath the parent folder do not inherit the Owner and Group permissions
of the parent.
I am given to understand from this Microsoft KnowledgeBase article (http://support.microsoft.com/kb/951716/en-gb) the problem is due to the Windows implmentation of NFS Services not supporting the Solaris SystemV or BSD grpid "Semantics"
However the article says the same functionality can acheived by using ACE Inheritance in conjunction with changing the Registry setting for "KeepInheritance" to enable Inheritance propagation of the Permissions by the Windows NFS Services.
1. The Precise location of the "KeepInheritance" DWORD key appears to have "moved" in Windows Server 2012 from a Services path to a Software path, is this documented somewhere? And after enabling it, (or creating it in the previous
location) the feature seems non-functional. Is there a method to file a Bug with Microsoft for this Feature?
2. All of the references on demonstrating how to set an ACE to achieve the same result "currently" either lead to broken links on Microsoft technical websites, or are not explicit they are vague or circumreferential. There are no plain Examples.
Can an Example be provided?
3. Is UUUA compatible with the method of setting ACE to acheive this result, or must the Linux client mount be "Mapped" using an Authentication source. And could that be with the new Flat File passwd and group files in c:\windows\system32\drivers\etc
and is there an Example available.
Scenario:
Windows Server 2012 Standard
File Server (Role)
+- Server for NFS (Role) << -- installed
General --
Folder path: F:\Shares\raid-6-array
Remote path: fs4:/raid-6-array
Protocol: NFS
Authentication --
No server authentication
+- No server authentication (AUTH_SYS)
++- Enable unmapped user access
+++- Allow unmapped user access by UID/GID
Share Permissions --
Name: linux_nfs_client.host.edu
Permissions: Read/Write
Root Access: Allowed
Encoding: ANSI
NTFS Permissions --
Type: Allow
Principal: BUILTIN\Administrators
Access: Full Control
Applies to: This folder only
Type: Allow
Principal: NT AUTHORITY\SYSTEM
Access: Full Control
Applies to: This folder only
-- John Willis, Facebook: John-Willis, Skype: john.willis7416

I'm making some "major" progress on this problem.
1. Apparently the "semantics" issue to honor SGID or grpid in NFS on the server side or the client side has been debated for some time. It also existed as of 2009 between Solaris nfs server and Linux nfs clients. The Linux community defaulted to declaring
it a "Server" side issue to avoid "Race" conditions between simultaneous access users and the local file system daemons. The client would have to "check" for the SGID and reformulate its CREATE request to specify the Secondary group it would have to "notice"
by which time it could have changed on the server. SUN declined to fix it.. even though there were reports it did not behave the same between nfs3 vs nfs4 daemons.. which might be because nfs4 servers have local ACL or ACE entries to process.. and a new local/nfs
"inheritance" scheme to worry about honoring.. that could place it in conflict with remote access.. and push the responsibility "outwards" to the nfs client.. introducing a race condition, necessitating "locking" semantics.
This article covers that discovery and no resolution - http://thr3ads.net/zfs-discuss/2009/10/569334-CR6894234-improved-sgid-directory-compatibility-with-non-Solaris-NFS-clients
2. A much Older Microsoft Knowledge Based article had explicit examples of using Windows ACEs and Inheritance to "mitigate" the issue.. basically the nfs client "cannot" update an ACE to make it "Inheritable" [-but-] a Windows side Admin or Windows User
[-can-] update or promote an existing ACE to "Inheritable"
Here are the pertinent statements -
"In Windows Services for UNIX 2.3, you can use the KeepInheritance registry value to set inheritable ACEs and to make sure that these ACEs apply to newly created files and folders on NFS shares."
"Note About the Permissions That Are Set by NFS Clients
The KeepInheritance option only applies ACEs that have inheritance enabled. Any permissions that are set by an NFS client will
only apply to that file or folder, so the resulting ACEs created by an NFS client will
not have inheritance set."
"So
If you want a folder's permissions to be inherited to new subfolders and files, you must set its permissions from the Windows NFS server because the permissions that are set by NFS clients only apply to the folder itself."
http://support.microsoft.com/default.aspx?scid=kb;en-us;321049
3. I have set up a Windows 2008r2 NFS server and mounted it with a Redhat Enteprise Linux 5 release 10 x86_64 server [Oct 31, 2013] and so far this does appear to be the case.
4. In order to mount and then switch user to a non-root user to create subdirectories and files, I had to mount the NFS share (after enabling Anonymous AUTH_SYS mapping) this is not a good thing, but it was because I have been using UUUA - Unmapped Unix
User Access Mapping, which makes no attempt to "map" a Unix UID/GID set by the NFS client to a Windows User account.
To verify the Inheritance of additional ACEs on new subdirectories and files created by a non-root Unix user, on the Windows NFS server I used the right click properties, security tab context menu, then Advanced to list all the ACEs and looked at the far
Column reflecting if it applied to [This folder only, or This folder and Subdirectories, or This folder and subdirectories and files]
5. All new Subdirectories and files createdby the non-root user had a [Non-Inheritance] ACE created for them.
6. I turned a [Non-Inheritance] ACE into an [Inheritance] ACE by selecting it then clicking [Edit] and using the Drop down to select [This folder, subdirs and files] then I went back to the NFS client and created more subdirs and files. Then back to the
Windows NFS server and checked the new subdirs and folders and they did Inherit the Windows NFS server ACE! - However the UID/GID of the subdirs and folders remained unchanged, they did not reflect the new "Effective" ownership or group membership.
7. I "believe" because I was using UUUA and working "behind" the UID/GID presentation layer for the NFS client, it did not update that presentation layer. It might do that "if" I were using a Mapping mechanism and mapped UID/GID to Windows User SIDs and
Group SIDs. Windows 2008r2 no longer has a "simple" Mapping server, it does not accept flat text files and requires a Schema extension to Active Directory just to MAP a windows account to a UID/GID.. a lot of overhead. Windows Server 2012 accepts flat text
files like /etc/passwd and /etc/group to perform this function and is next on my list of things to see if that will update the UID/GID based on the Windows ACE entries. Since the Local ACE take precedence "over" Inherited ACEs there could be a problem. The
Inheritance appears to be intended [only] to retain Administrative rights over user created subdirs and files by adding an additional ACE at the time of creation.
8. I did verify from the NFS client side in Linux that "Even though" the UID/GID seem to reflect the local non-root user should not have the ability to traverse or create new files, the "phantom" NFS Server ACEs are in place and do permit the function..
reconciling the "view" with "reality" appears problematic, unless the User Mapping will update "effective" rights and ownership in the "view"
-- John Willis, Facebook: John-Willis, Skype: john.willis7416

Mounting an NFS share

Hi,
I'm attempting to mount an NFS share and having no success. Regardless of the settings I try, the Finder still denies me access to the NFS share, even though it mounts fine. I seem to have no read or write access to the share.
I've tried exporting the share (in /etc/exports on the server machine) in two ways: with
/home/REDACTED/share REDACTED/28(rw,sync,all_squash)
And
/home/REDACTED/share REDACTED/28(rw,sync,insecure,all_squash,anonuid=1001,anongid=1001)
In the second example, the anonuid and anongid are those of the shared folder's owner and group. I added "insecure" because a how-to on the web claims that OS X won't work with any shares that don't have this specified.
With either of these settings applied, Disk Utility verifies the existence of the share, and mounts it. However, I can neither read files within, or add files to, the shared folder. The error produced is:
The folder “share” can’t be opened because you don’t have permission to see its contents.
I have tried the following Advanced Mount Parameters, each to no effect:
nodev resvport nolocks locallocks intr soft wsize=32768 rsize=3276
nodev nosuid resvport nolocks locallocks intr soft wsize=32768 rsize=3276 ro
nodev,nosuid,resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
nodev,nosuid,resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276 ro
resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
-i,-s,-w=32768,-r32768
-P
I'd rather not employ SAMBA, and the Apple File Sharing package for my server's OS (Ubuntu 11.10) appears to be bugged currently. Besides, NFS would be a far neater solution.
Any helpful advice?
S.

Scotch_Brawth wrote:
I've simply come at NFS as being the most appropriate file-sharing implementation for my needs - it supports automatic mounting at boot using tech native to both my Linux OS and OS X.
That is part of the problem. NFS is designed for environments where all servers are mounted (by root) at boot time and permissions are managed via NIS or LDAP. That is the default setting. If you are using something else, it requires some hacking.
I've had SAMBA working in the past, but I guess a certain air of contamination creeps in when using a Windows protocol to allow interaction between two UNIXy systems.
Plus, you would now have two different 3rd party reverse-engineered reimplementations of a foreign protocol.
AFP would be great, but despite receiving support on the Ubuntu forums and IRC, I failed to get it to work - it may be bugged; which would not be surprising, as 11.10 (with Kernel 3) has proved problematic in several other ways.
Perhaps Ubuntu is targeted more towards desktop rather than server usage. About the time I last played with NFS, I also played with Netatalk - with disastrous results. Supposedly Netatalk is better now. It's authors would be more than happy to sell you a support package.
I did use the default settings - they failed to allow a working NFS share. I then applied the variety of settings as recommended by apparently knowledgeable people. Still no success. I have read that UID/GID settings are an important aspect of NFS, but the issue in this case (as far as I understand it) is that all UID/GIDs below 1000 are privileged in Ubuntu 11.10, whilst on OS X these are below 501. So, the choice is either to give the shared folder owner a privileged UID/GID pair, or change the UID/GID of my Mac users to meet the NFS servers needs - not something I'm happy to do for so small a gain.
You can create a throwaway account on the Mac and just reset the GID/UID to values equal to an account on the Linux machine. That would establish that it is properly working in the default configuration. Then you could edit /etc/idmapd.conf.
For that reason, I use the "all_squash" option, because the share in question is not for anything remotely critical and the data to be transferred and stored is both worthless and transitory.
Since all_squash maps everything to nobody, you would have to hack up the permissions on the server to make everything world writeable. I think it will work with /etc/idmapd.conf and without all_squash.
I know nothing about NFS other than that its capabilities and integration meet my needs.
Just what are your needs? If the data is worthless and not critical then Netatalk might be the best option. If you can't get that to work, you could try MacFUSE on the Mac side and mount over sshfs. That is normally what I do. It isn't all that reliable, but you don't seem to require that.
What information I did find regarding OS X and NFS was that there were peculiarities that required certain settings to be present on the server and the client respectively - for example, OS X apparently requires "insecure" to be set as an option, or it simply won't connect properly. I don't know why, but I have no choice to trust to the advice of others in this case, until I have sufficient grasp to take care of the whole thing myself.
This goes back to the expectation that NFS expects to be always connected and mounted by root. Apple sells very few desktop machines anymore so it assumes a different, user-centered environment. You could use "insecure" on the server side to allow connections from "insecure" ports > 1024 that a regular users can connect with via the Finder. You could use the terminal with "sudo mount_nfs -o resvport" to tell the Mac to use the root user to connect via a secure port instead.
If you genuinely think you're able to help, then I'm happy to hear your advice. What would you recommend?
I appreciate your meeting me halfway. I think all you really need is /etc/idmapd.conf without all_squash. Then you could setup AutoFS and you could use NFS in a modern environment without even bothering to mount it.

Adding NFS Share to Mountain Lion Server

Alright, here goes.
The company I work for has been using SL server for years and wanted to test a possible upgrade to ML server for NFSv4. Downloaded ML to test machine and ML server. I mounted it via server connector (nfs://blah blah..you get the idea) volume that I want to share comes up on desktop but will not show under the server app. I also have access to posix but I need full access to acl as well.
I'm trying to figure out how to access this NFS share so that I can share it from the server but cannot seem to get it working. To those who know OSX servers I probably sound like a moron, but I'm just an I.T. guy tasked with setting up a test server even though I'm not a "server guy". Any information would be greatly appreciated.
One more question. Would a migration from SL to ML server also bring along this volume? Thanks again.

I upgraded today and had the same issue. I took following steps to fix my computer.
Boot into Recovery Partition (Hold Option Button while booting)
Open Terminal.
Type resetpassword
Select your hard drive
Select the user account (Administrator)
Enter a new password for the user
Reenter password
Save
Restart
Boot normally, Login as Adminstrator with the new password and add "Admin" permission to your account.
Restart
Everything should be working as expected

Cannot export nfs-share over ipv6 in OS X 10.8

Similar Messages

Maybe you are looking for