NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
adamwilt
Jun 02, 2009Aspirant
Weird AFP permissions?
I'm using OS X 10.5.6 and 10.5.7 to connect via AFP to a ReadyNAS Pro running RAIDiator 4.2.5. When I copy files to the NAS, the resulting permissions normally look like this (using OS X's "Get Info" window):
user: adam, permissions: read & write
group: MTE, permissions: read & write
world: everyone, permissions:read & write
(And yes, I have advanced AFP permissions set to grant read & write to group and to world.)
But sometimes they look like this:
user: (unknown), permissions:read & write
group: avahi, permissions: read & write
world: everyone, permissions: read & write
Sometimes these oddball user & group names come and go; sometimes they persist. I can reset them using Frontview, but if I try to deal with them in the Get Info window, the file typically becomes unreadable (until I reset permissions on the entire share via Frontview).
The answer to the unreadability problem is "don't do that", grin, but what about the substitution of (unknown) for my user name, and avahi for MTE? If I decide to restrict read/write ops to the MTE group instead of everyone, then the file becomes unusable because the group changes from MTE to avahi, how do I fix the problem without changing file permissions on every file on the share?
Has anyone else seen this? Any suggestions as to why this is happening, and how to prevent it?
user: adam, permissions: read & write
group: MTE, permissions: read & write
world: everyone, permissions:read & write
(And yes, I have advanced AFP permissions set to grant read & write to group and to world.)
But sometimes they look like this:
user: (unknown), permissions:read & write
group: avahi, permissions: read & write
world: everyone, permissions: read & write
Sometimes these oddball user & group names come and go; sometimes they persist. I can reset them using Frontview, but if I try to deal with them in the Get Info window, the file typically becomes unreadable (until I reset permissions on the entire share via Frontview).
The answer to the unreadability problem is "don't do that", grin, but what about the substitution of (unknown) for my user name, and avahi for MTE? If I decide to restrict read/write ops to the MTE group instead of everyone, then the file becomes unusable because the group changes from MTE to avahi, how do I fix the problem without changing file permissions on every file on the share?
Has anyone else seen this? Any suggestions as to why this is happening, and how to prevent it?
14 Replies
Replies have been turned off for this discussion
- jongrahAspiranthave got exactly the same thing, only the group name changes to "(unknown)" as well (instead of "users")
mac os 10.5.7
readynas nv+
raidiator 4.1.4 - kermit4161AspirantThread resurrection time... did anyone ever figure this out? I'm installing a new NAS and am experiencing the same issue.
Also, when I go into Finder>Get Info on a folder to try and change a permission, it doesn't recognize any of the user/group names I try to enter. Anyone have any ideas?
Ultra 4
FW: RAIDiator 4.2.15
4x WD 2GB drives
OS X Snow Leopard - cguersAspirantIt seems no one got this resolved? :?
I have Mac OS X 10.6.8, updated ReadyNAS Pro firmware to 4.2.19 and I have the same behavior... no owner name, "avahi" as the group. I cannot make changes to these folders!! :oops: :oops: :oops:
Any suggestions would be welcome!!! - dhlLuminaryYep, I'm seeing this too. Very annoying! Anyone know what's up?
- cguersAspirantI decided to downgrade to version 4.2.17 and I got back the right permissions: I am back to how it was before. Anyway, most of the improvements in the newer version are not really that critical for my operation.
I imagine the issue is only with AFP, so probably Windows clients are Ok with the latest version. However, all my computers are Macs, so I'll have to wait until Netgear comes out with a version that fixes this and is tested to do so. - I'll bump this thread as I am having the same issues running OS X 10.7.4 and two NVXs and one Pro (all three running 4.2.20). I'd really like to get my permissions issues resolved as I believe it is causing problems with file transfers.
I am the only user on all three NASs so there is a single user (me). I have set the username to be the same as my MacPro - that didn't seem to help. I was going to set the group name to the same as the Mac also but I ran into a problem. The Mac group name is 'staff' but when I try to create this username on the NASs I get an error stating this name already exists. What confuses me is that this group does not exist. The only defined group is 'users'.
Is there any chance this is related to who is defined as the admin on the Mac? How is the admin username defined on the NASs?
Any thoughts? - cguersAspirantI ended up downgrading to 4.2.17... Not my preference as Time Machine in Mac OS X Lion (10.7.x) does not work with the service on the NAS. It would be great to have a solution for this. The rest of the NAS services seem to work ok, including file permissions.
- pszilardAspirantI find that even though I have Read/Write access to everyone, in AFS I can't write via my Mac. However accessing via CIFS seems to work. Go figure...
- victorhortaliveAspirantI had this sort of problem when I tried to delete some files I had created on another PC.
As I'm the only admin user I do this :
1. For the AFP and CIFS service I make sure the Allow guest access is checked and that default Access is Read/Write.
2. In Advanced Options I check - Grant rename and delete privileges to non-owner of files
3. If those don't work then I also check - Set ownership and permission for existing, etc, etc.
This solves my problems - cguersAspirantThis likely works because it grants everyone access to the files. I need to restrict access to the files.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!