NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
arunasad
Aug 25, 2010Aspirant
Can’t change permissions – “The parameter is incorrect”
I have three ReadyNAS Pro Business boxes on Windows Server 2003 domain.
Just noticed that there are some issues with changing permission on Windows machines. Basically if a user creates a folder and then he or an administrator tries to change some permissions (add additional user, propagate permissions to child objects, allow or disallow inheritance) this fails with error
“An error occurred applying security information to: <path/folder> The parameter is incorrect”
Or:
“Unable to save permissions changes on <foldername> The parameter is incorrect”
The same happens for the domain administrator account which was used to add ReadyNAS to a domain.
If I try to add additional user this actually works even after the error is displayed, however it doesn’t propagate down and only affects one folder.
This definitely used to work so I suspect problem occurred after one of the recent firmware updates. I am currently on 4.2.13, but the same was happened on 4.2.12 (just upgraded hoping this would sort the problem).
Also, this seems to affect only newly created folders. With old folders everything works fine.
Any ideas how to fix this?
Just noticed that there are some issues with changing permission on Windows machines. Basically if a user creates a folder and then he or an administrator tries to change some permissions (add additional user, propagate permissions to child objects, allow or disallow inheritance) this fails with error
“An error occurred applying security information to: <path/folder> The parameter is incorrect”
Or:
“Unable to save permissions changes on <foldername> The parameter is incorrect”
The same happens for the domain administrator account which was used to add ReadyNAS to a domain.
If I try to add additional user this actually works even after the error is displayed, however it doesn’t propagate down and only affects one folder.
This definitely used to work so I suspect problem occurred after one of the recent firmware updates. I am currently on 4.2.13, but the same was happened on 4.2.12 (just upgraded hoping this would sort the problem).
Also, this seems to affect only newly created folders. With old folders everything works fine.
Any ideas how to fix this?
137 Replies
Replies have been turned off for this discussion
- Dear Grievious,
please found my PM, thanks alot~ - arunasadAspirantGrievous,
What is the status of the original issue? Is it fully resolved in the current RAIDiator version (4.2.17)?
I still have the same problems with old shares, but couldn’t reproduce it newly created test share. To fix this permanently do I need to recreate all shares and move the data, or it can be resolved with original shares? - GrievousAspirant
arunasad wrote: Grievous,
What is the status of the original issue? Is it fully resolved in the current RAIDiator version (4.2.17)?
I still have the same problems with old shares, but couldn’t reproduce it newly created test share. To fix this permanently do I need to recreate all shares and move the data, or it can be resolved with original shares?
The status would be that we can no longer reproduce it in 4.2.17. Yes, I'd advise creating a new share and copying at least a portion of the data over and checking that it works. - hovermanAspirantI am having this issue as well, with two different customers. Once customer is user a 2003 Domain with an NVX, and the other on a 2008R2 Domain using a 2100. Both are running 4.2.17 of the firmware.
Only reason I came across this is both of my clients asked to change the permissions on a single folder inside of a share that is shared to "domain users". I went in the un-inherit permissions and then add only those domain users I wanted with Read/write. This seemed to work, but when users started complaining, I went back in to just reset everything back to normal, and then I got the infamous "Paremeter is incorrect".
I even went into the ReadyNAS frontView and went to the advanced tab and reset the permissions there. IT said it was successful but that one folder it didnt have an effect on. I did this on both users 2003 with NVX and 2008R2 with 2100)
I tried this on existing shares (created before the 4.2.17 updates) and on brand new shares (created today) and have run into the same issue.
I have read in other forum posts that this all goes back to having the "Domain Users" as the folder read/write group and that is I just make up a new security group, add the users to the new group, and reset all the permissions these issues go away. Can anyone confirm this?
If I dont hear by about 8 tonight, I will remote in to my customers and give this a shot. - generalimagingAspirantI don't know if this has been resolved somewhere else...
I spent the whole freakin day researching this problem.. I found a solution that worked for me so I want to share it to save people time... It's a great product but the support for this problem is bad from the threads i've seen - even seeing the admin locking the thread because users were frustrated.
I'm using AD with a ReadyNas 2100. I'm setting up Department Folders (which means alot of different variations of permissions per folder)...
(i'm doing this from memory - but get the main idea) What I did was to go to the root folder --> get to the Security Tab and remove the Domain User account. Click Advanced and then remove the Domain User account from that screen... --> Check "Replace permissions entries on all child objects with entries shown here that apply to child objects." It will warn you but go ahead anyways.. If this works then I believe it will reset all the subfolders Domain User account permission. Click Apply....(There are 3 opportunities (screens) to click Apply during this process - i think you do it last, but try to click it before the last window if it doesn't work) My un-educated guess is that there are conflicts with the Domain User permissions on the subfolders that is preventing you to save the configurations on the Root.
The drawback is that you have to go back and verify all the folders' permissions (to be sure) and add Domain Users when needed.
I'm not a guru or anything, but I think the Linux file permissions are conflicting with Windows. I have a problem giving users Write permission without assigning Full Control with the NAS.. Anytime I click Write permission, it ends up giving the FULL Control permission - hence, i think it's the OS's permission conflicts behind this whole mess... Hope I helped..... - generalimagingAspirantForgot to mention that - after I reset the Domain Users permissions (from my posting above) - when I go back to the main Security window, I can't assign any permissions to Domain Users directly there. Instead, I click on Advanced and then Edit the Domain Users account and assign permissions from there. When you click Apply and go to the main Security window --> Domain Users will only have a check on Special Permissions, even if you give Full Control.. .. but it still should honor the permissions set on the Advanced window..
- NoiaAspirantWe're experiencing the same issue under certain conditions, which seem to be easily replicable, at least on our 18 TB ReadyNAS 3200
1) Create share default (no public access)
2) Under advanced, set user and group to domain account and domain group, keeping R/W for the group, and disabling Everyone
3) Take properties for the share, take the domain group, and change it from "This Folder Only" to "This Folder, Subfolders, and Files" in advanced.
4) "The parameter is incorrect"
This is probably by design somehow in the way that the NTFS access rights are used through this system, but it's MILDLY annoying. (Which means: My table has teeth marks at this point)
I can do it by using a separate group I guess, but I'm trying to avoid that for multiple reasons. Also, adding SOME groups, they just disappear again with no error, when hitting apply. (for instance adding a group for all users in a specific OU - I add, set rights, and it just disappears when hitting Apply)
Note that this is a setup with 800 local users (for our 6 OUs), in a global AD with over 200 OUs - from an enterprise point of view, it's not really giving me the options I need, sadly. - NoiaAspirantEven more odd - the only groups I can add have the prefix E130_ - all others just disappear. E129_, E131_, etc. - they all just disappear. Note that the NAS is located OU-wise in an OU called E130 - is there a problem adding groups from outside the same top-OU somehow? I can't see any other reason for this behaviour.
EDIT: Updating from 4.2.15 to 4.2.19 fixed the problem with the groups somehow, so that one isn't relevant anymore.
EDIT EDIT: Aaaand removed all the settings I had put on the shares, replacing the owner with the guy that added the NAS to the domain, and the group to "Domain Users". Changing them, they revert back instantly... :evil: - brassmonAspirantNoia - I have seen having this issue as well but have not updated firmware. Did upgrading your firmware remove all individual file/folder permissions as well as ownership?
Thanks! - NoiaAspirant
brassmon wrote: Noia - I have seen having this issue as well but have not updated firmware. Did upgrading your firmware remove all individual file/folder permissions as well as ownership?
Thanks!
Sorry about the slow reply.
Upgrading the firmware removed ALL rights on ALL shares - AND now the problem is back where I can't change access rights reliably, plus all users have again lost access despite the ACL showing them being correct. For the 215.772th time. I cannot explain exactly how unimpressed I am with this so-called business grade NAS.
Related Content
NETGEAR Academy

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