NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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
- I too have run into this issue. Support recommended I upgrade to .17 (Not .19) to fix an Iscsi connection dropping issue. After the upgrade, I can no longer create users in AD and point their home folder to the "Users" share I created on the NAS. I get the "Parameter Incorrect" error. Also, when I try to add users, or change permissions on other existing shares (Departmental drives), I get the Parameter Incorrect error! So far, no one has reported any issues accessing existing shares since the "upgrade" (to use the term loosely). I am just dead in the water when it comes to moving forward. However, I have been able to create new shares, and set permissions which allowed me to point user's home folders to this new share in AD. I don't plan on using this though, because I have no intention of adding more users to what I consider a broken box. This really worries me because I have about 100 user's home folders, a bunch of departmental folders, and an Iscsi connection to a Symantec Enterprise Vault email archive on this box! If this goes down, I'm screwed! Support seems to be taking stabs in the dark telling me to do some of the workarounds that are posted here. Considering the mixed results, I'm sitting tight until an actual solution is reached. Any word as to what's happening with this?
I have a Windows 2003 AD environment with XP workststions. - I'm not sure why support would recommend 4.2.17 and not 4.2.19, considering how out of date .17 is. The current 4.2.20 t-28 beta has actually had some fixes for windows ACL issues since an earlier beta build. I suggest checking that.
- The support person said there had been some issues regarding Iscsi connections dropping with .19, so recommended going to .17.
Here's the case number:17495725. When is the new firmware coming out of beta? - We're looking into why support said that, you should definitely be running 4.2.19 and not 4.2.17 at this point.
I don't believe we have a timeframe for a final build of 4.2.20 at this time, however in it's current beta form it is stable enough to be put into place in a production environment, especially considering that the alternative would be permissions not working correctly. If you want to make absolutely certain that it fixes it without touching anything else and maintaining your ability to downgrade, update to the latest beta, create a new share and test your permission changes in that first. - I do have the same "parameter" errors . Even after working long with support with several work around... waiting for the new firmware ..
- What is the status on the beta firmware?
Has anyone tried it? - It looks like there has been quite a bit of buzz on this post. I would like to provide a quick fix for the issue that I have discovered with the current (4.2.19) version of firmware. Under Share Listing > Share in question > CIFS > Advanced; set the owner to "nobody" and the group to "nogroup" (without the quotes of course) then check the set ownership and permissions to the above.... and then apply. This should release any ownership issues that may be causing the issue. Then go into Services > Standard File Protocols and disable; then re-enable the CIFS protocol. This is what fixed the issue for me.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
