File Permissions To Not Propogate Down From Root Folder

[srgalpin]

Hi All,

I am trying to set up a ReadyNAS Duo running dashboard 1.0.0.168R. It has two 2Tb drives installed.

I have set everything up fine but I am experiencing a reall ball ache with file permissions on shared folders.

We have a micture of Windows and Mac's on the network. Every machine can see the network shared folders absolutely fine. I have set up the root folders through the web dashboard and selected everyone access with read / write.

If a user creates a folder, everyone else only has read access, but no write access. Only the person that has created the folder has write access.

This is obvioulsy not acceptable as the folders need to be accessed by all users.

I found the following other topic that appears to be the same problem - http://www.readynas.com/forum/viewtopic.php?f=23&t=61586

According to this it is a known bug and nothing can be done about it.

I would be very grateful for any support or help on this, as in its current state the NAS box is only useful as a doorstop!!!

Cheers

Scott

[fraser-j]

Hi fellow frustrated ReadyNas users

I'm having the exact same problems & have probably wasted the whole day one way or another on this issue.

I know that this is not the answer but to eliminate any errors on my part in creating a new 'share' I copied a complete set of Sage accounts files for one of our companies (this is the network version of the Sage 50 Accounts) into the default 'Backup' folder/share/directory or whatever you'd like to call it and bingo everyone who should have access has!

I therefore checked all my previously set up share settings again and tweaked them so that they were EXACTLY the same as the 'default 'Backup' share. Unfortunately it's made no difference whatsoever so I'm back to square except that at least I have something to go on now.....

[fraser-j]

PS I should have mentuioned that I'm running a ReadyNas Duo v2 with RAIDiator 5.3.4

[srgalpin]

I spent some time on the phone to Netgear Support today and they confimred that it is a bug in the ReadyNAS Duo v2 boxes.

If you have one of the older ReadyNAS Duo boxes with the older style dashboard it is absolutely fine.

I was told that they have no planned date for a firmware upgrade to fix this probelm, so I could return the box under warranty.

I will see if I can find an older ReadyNAS Duo from another supplier as I know these boxes work fine.

I can't believe Netgear are not working their cotton socks off to fix this as it is a fundamental problem and means the box is rendered useless as a network share!!

Come on Netgear sort this mess out and make sure you test your products fully before you do "Product Improvment Upgrade"!!!!!

[fraser-j]

It's unbelievable that Netgear are prepared to knowingly sell kit that's basically unfit for purpose. For years we've run a (touch wood) bullet proof Novell server which I thought was about time to retire. Obviously not!

If my research serves me correctly the older Duo version runs a much slower processor which is why I went for this one. Before I throw in the towel I'm going to try & find a work around - but then I always was a masochist!

Cheers- Fraser

[wipeout]

edit - working in latest beta

[fraser-j]

Sorry, I don't have much time to reply at the moment but I have mine running beautifully at the moment (fingers crossed it remains that way) with a basic workaround.

The quickest way to get around the present bug is to use the default shares 'Media' and 'Backup'. You can create your own shares but as you will have found out you then end up having to manually change all the permissions.

The solution for me was fairly simple as I'm using this NAS to replace an ageing Novell server. All I've done is to rename the Media share to one more appropriate and copied all the files from our old server over. I've kept the original Backup share and will use this for backups.

To date all's working well, and our networked Sage accounting software is performing as it did on the Novell. As far as security goes I've created all the users with their User Name and passwords EXACTLY the same as their Windows PC's and switched off 'Everyone' in the user permissions. Each user's PC has a drive mapped to the NAS so they are automatically logged into it when they log in to their PC's.

I've tested the security and all appears to work as it should.

I know that you shouldn't have to put up with kit that's not fit for purpose but I looked at it that I'd already invested (wasted) too much time on the problem so plumped for my workaround until Netgear release a fix.

Good luck.

Fraser

[wipeout]

hi fraser -

you just made my day, reusing media folder worked - subfolders can be edited / deleted by everyone

THANK YOU for taking the time to post your solution, solved my problem!

[Mirel]

Hello,

I have a file permission problem at my work. I moved all my files from server to NAS Drive (ReadyNAS Pro 4). Users have been created on NAS Drive and all the employee are connected to NasDrive using their own "user".

Even on the main folder is set full rights for "everyone", for some of the sub folders and files they don't have access and they cannot rename or change the content.

I have found "advanced option" from Shares->Share Listing sub menu and I ticked "Set ownership and permission for existing files....." but after I click apply, the box become unticked. My question is if this is normal, or the box should stay ticked?

Why my users don't have full access after "everyone" is set with full rights? Why "everyone" don't propagate correctly to all sub folders and files?

For some of my files even "everyone" is set there, my employee don't have full access.

Is this an error from my ReadyNAS model?, Should I look for an update?

Thanks,
Mirel

[StephenB]

...I have found "advanced option" from Shares->Share Listing sub menu and I ticked "Set ownership and permission for existing files....." but after I click apply, the box become unticked. My question is if this is normal, or the box should stay ticked?...

It is normal. That is a command, which resets permissions, not a configuration option.

Did you notice the "Advanced CIFS Permissions" section on the CIFS Tab? That is a configuration, and those options will control permissions for new folders and files in the share.