Permissions not getting set automatically

[youngmn]

Using the NVX with the latest firmware levels. Issue is when someone adds a new folder or file to a share they can access it but all other users can not.

Logged in as the Admin user, going to the share and select "advanced Options" and then checking the box that says to set permissions on existing files is used then applied resolves the issue.

This is happening on multiple shares and users and the the above process fixes it each time. This is a work around but not a long term solution.

Ideas on where to check?

Thanks!

[arjoseph]

Please verify if you have tried these steps:

To open the file permission for NEW files, follow the steps below:

Configuring Advance CIFS Permissions:
1. Go to Share listings
2. Click Cifs icon of the specific share name
3. Scroll down and put a check on "Automatically set permissions on new files and folders" under Advance CIFS Permissions.

To open the file permission for EXSISTING files, follow the steps below:

Configuring Advance Options:
1. Go to Share listings
2. Click Cifs icon of the specific share name
3. Go to Advance Options tab
4. Share folder owner: (type the share name)
5. Share folder group: (nogroup)
6. Put a check on "Set ownership and permission for existing files and folders in this share to the above settings" and click Apply.

P.S.
After you put a click on the Apply button the check will disappear inside the check box, it's normal because it's an action box.

[clewis]

arjoseph - I'm experiencing the same thing, with greater frequency, since upgrading nearly all users to Win7 pro. One user will modify a file within a share, or they'll create a folder, and then no one else can access the file or folder until I go to frontview and set ownership permissions for existing files and folders to the above settings and click apply.

[readysecure1985]

clewis, which ReadyNAS are you using and what exact firmware version do you have?

[clewis]

Readynas 1100 with 4.1.8.

[readysecure1985]

Ok. Go ahead and try the steps arjoseph listed. If those don't work, you may want to try opening a ticket with the support team.

[clewis]

I do arjoseph's steps all the time when my users report they cannot access a file. The question is, how do I keep this from happening to start with? If I'm out of office or something and someone needs to get to a shared file which has had its permissions changed by one user (or the Win7 OS, whatever) then going through arjoseph's steps is not a good option. I need to prevent, not react.

[readysecure1985]

6. Put a check on "Set ownership and permission for existing files and folders in this share to the above settings" and click Apply.

P.S.
After you put a click on the Apply button the check will disappear inside the check box, it's normal because it's an action box.

This step is the one that is used to fix the issue you are having. Since that isn't fixing it I would suggest opening a support ticket.

[door.jar]

6. Put a check on "Set ownership and permission for existing files and folders in this share to the above settings" and click Apply.

P.S.
After you put a click on the Apply button the check will disappear inside the check box, it's normal because it's an action box.

This step is the one that is used to fix the issue you are having. Since that isn't fixing it I would suggest opening a support ticket.

You aren't reading and comprehending his question. Basically, something is going wrong and breaking permissions, not just for clewis but for MANY ReadyNAS users (including myself). Your solution is to follow a set of steps to fix the issue for current files, it does nothing to prevent it happening again with new files. This isn't a practical long term fix as it needs to be done CONSTANTLY.

Netgear need to sort the problem out so users aren't required to babysit file permissions.

[readysecure1985]

Netgear need to sort the problem out so users aren't required to babysit file permissions.

This is why I am suggesting opening a support ticket so that Netgear can find the cause and correct it.

[door.jar]

Netgear need to sort the problem out so users aren't required to babysit file permissions.

This is why I am suggesting opening a support ticket so that Netgear can find the cause and correct it.

I did that. I got told that you can't reproduce it and the case closed with notes indicating that support tried to call me when in fact they did no such thing. Netgear support is terrible and their products are too.

If you give a damn then you can find the case number in the title of my unanswered thread here:
http://www.readynas.com/forum/viewtopic.php?f=23&t=64022

[clewis]

In addition to door.jar's comments - my device is out of warranty so I'd have to pay for support. I'd prefer not to have to do that...and I can see it would be a waste of money, based on what door.jar has said.

I'm shopping around for cloud-based storage for my users. The readynas boxes will make some good storage for backup data, maybe, but nothing else.

I have noticed this issue is spotty. I have a situation where when one user opens up a file and then saves it, it locks for everyone else (6 other users.) However, when one of those other users opens the file and then saves it, it doesn't get locked. I know which user is doing it because in windows explorer I can look at the security on the file and see "Everyone" with their rights all turned off, and I can see the particular user's name with full control. If logged in as admin then I can modify the permission there and suddenly everyone's able to see it again.

I'm also seeing this on a Mac user too. The Mac user opens the file and it gets locked to where only he can open it.

[StephenB]

In addition to door.jar's comments - my device is out of warranty so I'd have to pay for support. I'd prefer not to have to do that...

That should only apply to phone-in support. The on-line email support should still be free.

[clewis]

Netgear support recommended the following steps:
1. upgrade firmware (Radiator 4.1.9 just came out.)
2. Do a firmware reinstall - this wipes admin password and network settings.
3. Reset permissions on affected shares.

Questioning them on step 2 they suggested doing 1 and 3 first to see if any impact before doing 2. I have done 1 and 3. The workgroup impacted by this is out of office for the week so I have to wait till next week to see if the issue is resolved.

Release notes for 4.1.9 mention something about CIFS permissions being part of the bug fixes...so I am hopeful.

I'll try the OS reinstall only if I have to...it's a little scary since it involves powering the machine up while holding the reset button in.