NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
afp
8 Topics[smb/afp] group permissions executable bit set by default: chmod g-x does not remove
How can I mount on OS X with file permissions perserved? Which turns into, how can natatalk be configured to allow chmod changes and not default to group executable permssions? Summary: # -- on OS X in AFP mount (e.g. /Volumes/share) --- umask 022 # no effect touch test stat -f '%Sp' test # -rw-rwxr-- # why is the group exec bit set!? # -- try to change permissions, no luck -- chmod g-x stat -f '%Sp' test # -rw-rwxr-- # no error but still g+x # -- change permissions on local filesystem (or nfs mount) --- ssh user@NAS chmod g-x /data/share/test stat -f '%Sp' test # -rw-rw-r-- # success! permissions reflected within AFP mount I'd like to expose a share to OS X clients over afp or smb such that file permissions are preserved -- so file permissions on nfs mounts and afp mounts look the same. OS X doesn't do nfs well and I cannot find a way to enable unix extensions for samba, so I'm looking at afp (netatalk). Files created on AFP mounts always have the group executable bit set. chmod has no affect (chmod g-w, chmod g-x, chmod u+x, ... no change). Howver, AFP mount file permissons do reflect any changes made on the NAS share locally or on NFS mounts. I think this is similiar to https://community.netgear.com/t5/Using-your-ReadyNAS/AFP-Mount-Point-Permissions-Solved/m-p/695352#M2505767Views0likes0CommentsAFP corrupt and suddenly not working
Hello Community, my AFP Service suddenly stopped. How do I get the AFP service working again?? Stopping and Starting the service in the Browser Interface of ReadyOS gives error: Unable to start and modify service (error code: 15002030001) I even tried to reinstall OS i.e. I installed the 6.8.0 Beta - but still the same error and unavailability of AFP as before. the AFP log also shows errors (see below) - but I don't no any further measures to get the service working again. I need AFP working for MacOS TimeMachine Backups. Ideas and help greatly appreciated. NAS-SAN-NAS Sample of the Log-Download: AFP: Jul 20 21:12:55 nas[Nas-Name] afpd[28455]: transmit: Request to dbd daemon (volume [username]'s home) timed out. Jul 20 21:12:55 nas[Nas-Name] afpd[28455]: afp_openvol(/home/[username]): Fatal error: Unable to get stamp value from CNID backend Jul 20 21:12:55 nas[Nas-Name] afpd[28455]: AFP logout by [username] Jul 20 21:12:55 nas[Nas-Name] afpd[28455]: dsi_stream_read: len:0, unexpected EOF Jul 20 21:12:55 nas[Nas-Name] afpd[28455]: afp_over_dsi: client logged out, terminating DSI session Jul 20 21:12:55 nas[Nas-Name] afpd[28455]: pam_unix(netatalk:session): session closed for user [username] Jul 20 21:12:55 nas[Nas-Name] afpd[28455]: AFP statistics: 0.73 KB read, 0.62 KB written Jul 20 21:12:55 nas[Nas-Name] afpd[28493]: read: Connection reset by peer Jul 20 21:12:56 nas[Nas-Name] afpd[28493]: read: Connection reset by peer Jul 20 21:12:57 nas[Nas-Name] afpd[28493]: read: Connection reset by peer Jul 20 21:12:58 nas[Nas-Name] cnid_metad[28846]: Multiple attempts to start CNID db daemon for "/data/Documents" failed, wip4.8KViews0likes6CommentsFile access confusion with afp and smb
My environment is all Mac. Years ago I read that afp was the best access method in an all-Mac environment and my ReadyNAS 516 was set up that way. I've since learned that it's preferable to use smb. So, I added smb as an access method. I generally use that. The problem is that I occasionally run into a file that can only be accessed via afp. When I use smb I get this message: "filename" can’t be opened right now because it’s being used by another task, such as moving or copying an item or emptying the Trash. Try again when the current task is complete. First of all, nothing is using these few files. What's confusing is that, other files in that same directory can be accessed fine. AND another Mac on the network accesses all of the files still using afp. This problem is on a new Mac using Sierra. I figure that this is a problem with the Mac and not the ReadyNAS because when I go into Terminal and run "ls -l filename" all the files in that directory show the same access rights. Are there any Mac experts here who may have an idea how I can fix this problem on this Mac? In the past I would have tried "Repair Permissions" but since El Capitan it's no longer available. Thanks for any ideas you might have.3.3KViews0likes3CommentsBizarre Behavior: Data Missing, Shares Inaccessible
This morning my wife and I opened our laptops (MacOS Sierra; mine's running the Public Beta) and found that our machines wouldn't connect to our Time Machine backups on the ReadyNAS. Something along the lines of, "Someone may have changed the disk or tampered with the data." My ReadyNAS shuts down at 1am every morning and powers up again at 7am, so the chances of an error or malicious activity taking place overnight seemed unlikely. I tried accessing the ReadyNAS admin page through Safari (Technical Preview), as usual, but it wouldn't load. Had to use Firefox. There I discovered that all my data was missing. HDD bay 1 was reported as being empty, and the HDDs in the three remaining bays were red. An odd boot issue, maybe? So I restarted the ReadyNAS. It came back online and showed the data this time, expect my apps (Plex and LMS) were switched off. I turned them back on again. But then I tried connecting to my iTunes AFP share via a symlink and the authorization kept failing, even though my credentials were correct. This time, I restarted my laptop, thinking it was maybe a cache issue. The laptop rebooted, then suddenly reverted to a login screen once the desktop appeared. Weird, but maybe that's a beta bug. Once I got back to the desktop, I tried accessing the iTunes AFP share again. Still didn't work on account of failed authorization. I checked the AFP settings on the iTunes share via the ReadyNAS admin. The account I was using to connect ("admin") appeared to be just fine, but a separate read-only account I'd recently created for my Sonos Play:1 ("sonos") was now disabled. Finally, I went back to the macOS Finder to the top-level ReadyNAS AFP device, then drilled down to the iTunes share, at which point I was finally able to access it as normal. There are likely a number of things going on here, but I'm weirded out by all the warnings and bizarre behavior. Has anyone encountered anything like this since upgrading to 6.6.0? Could someone look at my logs and see if there's any suspicious activity?5KViews0likes22CommentsExplaining Permissions Mac OS X 10.11.5 / ReadyNAS OS 6.5.0 / AFP - Second Question
Following on from my First Question - https://community.netgear.com/t5/Using-your-ReadyNAS/Explaining-Permissions-Mac-OS-X-10-11-5-ReadyNAS-OS-6-5-0-AFP/m-p/1088919/thread-id/109697 This relates to accessing my 314 running OS6.5 via AFP from OS X 10.11.5 (latest El Capitan updates in place). This all for the user "admin" in ReadyNAS OS 6.5. I'm logging into via AFP using the user "admin" User "admin" (UID=98) primary group in FrontView is "admin" (GID=98) and its secondary group is "users" (GID=100) Here's what I see via SSH when I looked at the directory “test” within the share “shared” - also logged in via the user admin With the exception of the file “test - new file.txt”, these are the permissions in place after moving the directories and files from the USB backup disk of my old ReadyNAS NV+. These files were placed on the EXT3 formatted USB Backup disk but the ReadyNAS NV+ backup job, and restored to the 314 using a backup job. I checked the backup job option “after backup is complete, change ownership of files in the backup destination”. Here’s what I see in FrontView for the share called “shared” Here's what I see in the Finder for the directory “test” the share “shared”, logged in via the user admin via AFP. Again note “test - new file.txt” was created in this direction from the OS 10.11.5 machine, where as the director and file were created back the backup job copying from the USB disk. Can someone please explain the differences between these views... (1) why is the owner of these files in the Finder "(unknown)"? I was expecting "admin" (2) why is the group of the file “test - existing file.pdf” "staff"? I was expecting “users” (3) why is the group of the file “test - new file.text” “staff”? I was expecting the group of a new file created in this folder to be the primary group of the user admin i.e. admin (GID=98), or possibly “users” (GID=100) (the secondary group of user admin, inherited from the containing folder “test”). (4) why are the permissions the file “test - new file.txt” different from “test - existing file.pdf”? I was expecting, based on the “Default Access” settings and “Permissions” settings FrontView for this share (see screen shots above), that files created in this directory to be group Read & Write and everyone Read & Write. Thanks for everyone's help2.8KViews0likes1CommentExplaining Permissions Mac OS X 10.11.5 / ReadyNAS OS 6.5.0 / AFP - First Question
Recently transitioned from a ~2008 vintage 2TB NV+ to an new 9TB 314. It was saying goodbye to a rock solid old friend, but I have to say I'm loving the new 314 and the new OS. A big step forward - the ReadyNAS tradition of excellence continues. But I remain very confused about permissions. I lived with it on the old NV+ but I want to get it "right" this time. This related to accessing the 314 running OS6.5 via AFP from OS X 10.11.5 (latest El Capitan updates in place). This all for the user "admin" in ReadyNAS OS 6.5. I'm logging into via AFP using the user "admin" User "admin"'s primary group in FrontView is "admin" (UID=98) and its secondary group is "users" Here's what I see via SSH - also logged in via the user admin Here's what I see in the Finder, logged in via the user admin via AFP Can someone please explain the differences between these two views... (1) why is the owner of these files in the Finder "(unknown)"? I was expecting "admin" (2) why is the group of the files "staff"? I was expecting there to be no group permissions for a home share (3) why is the permissions the files of "staff" and "everyone" read only? I was expecting the "admin's home" share permission (no group and no everyone access - as shown in both SSH and Finder screen shots above) to be inherited at the file level (4) how could I change the default user permissions of files created in a home permission? Unlike other shares the FrontView "Access" settings for "home folders" doesn't allow any changes other than selecting the "Network Protocol" (other shares I can set the "Network Access" (share) and "File Access" default permissions) Thanks for everyone's help2.7KViews0likes1Comment(Still) Can't connect via AFP
Hi there. I'm running a ReadyNAS NV+ for home use. It's on firmware version RAIDiator 4.1.14. For no apparent reason, I stopped being able to connect using AFP (you can see the original thread relating to this problem here – it was never resolved). I can still connect to the shares using SMB / CIFS. Not being able to connect via AFP means that the disk cannot be discovered by Apple's Time Machine. Today I performed a factory reset on the volumes (clearing all disk contents), in the hope that this would fix the AFP problem. It remains. Any suggestions how I could go about fixing this? I thought maybe it was a permissions problem like this but that post refers to a different readynas firmware version.Solved4.9KViews0likes10CommentsAccess Denied on some folders on Mac via AFP
We have a ReadyNAS 312 set up at our company. It has 5 shares set up (not including /backup and personal shares). User access is divided into groups. We are having an issue with one of our shares that all groups have access to, called /Resources. I am the admin and the sole user in a group called "Full Access". My assistant is in a group called "Operations_HR". When either of us mount the /Resources share, we have the little red "Access Denied" icons on some (but not all) folders. Other users, within other groups, have no problem accessing all folders within /Resources. Below are some screenshots showing 1) Finder with Access Denied indicators 2) Network Access on this share, showing "FullAccess" as a read/write group 3) File Access on this share, showing 'FullAccess" as a read/write group 4) Just to confirm, my user account, showing me as in the "FullAccess" group. I've logged in multiple times on multiple computers to verify there wasn't some permission caching issue going on as i tried various fixes. My guess is that this may be related to who created certain folders and how, but i'm not sure why that would affect some groups and not others, if we both have matching "read/write" access. Any thoughts? My firmware is current, v6.4 Thanks in advance, devinSolved6.1KViews0likes6Comments