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
- GrievousAspirantncamhi, what firmware version are you using and how exactly are you configuring the permissions?
- ncamhiAspirantWe are using WIndows Explorer to set permissions - tried on 2003 server sp 2 standard and 2008 server r2 standard.
Model: ReadyNAS NVX Business Edition [X-RAID2]
Serial:
Firmware: RAIDiator 4.2.15
Memory: 1024 MB [6-6-6-24 DDR2]
Thanks,
Neil - GrievousAspirantUpdate to 4.2.16 and try again. I suppose my question about the permissions wasn't quite clear enough, what exactly are you trying to set the permissions to be.
- ncamhiAspirantI download and try to update and get Invalid checksum detected in update file. Update aborted.
I am using file RAIDiator-x86-4.2.16
The permissions is full control to the users. - GrievousAspirantI get that permission for the users is full control on the file, but what about the folder that the file is in?
- ncamhiAspirantThe issue is that I cannot write to any sub folders.
\\NAS\Directory I can write to
\\NAS\Directory\SubDirectory I cannot write to = I get access denied.
The user has WIndows security full control with all subdirectories below it.
Also, the service pack get the check sum error as previously mentioned.
Thanks - smemaineAspirantThis is a work around that we've been using for months, for what its worth:
Hostname: NSERVER
Model: ReadyNAS 2100 v1 [X-RAID2]
Firmware: RAIDiator 4.2.16
Memory: 1024 MB [5-5-5-24 DDR2 ECC]
Windows 2003 Server Domain: SMEMAINE
1. regular user George creates a new folder (aaaatest) on the root of share //NSERVER/CFS using a windowsXP
workstation with the latest SPs and updates.
2. No other users can access the folder aaaatest.
3. As a domain user and admin I also cannot access the folder.
I have a mapped drive (N:) to //NSERVER/CFS and a DOS batch file named fixp.cmd
I do the following work around:
---------------------
From a DOS shell run cacls (with arg: aaaatest) to view the Windows Access Control List; the output is:
N:\aaaatest SMEMAINE\Domain Guests:(OI)(CI)(special access:)
SMEMAINE\george:F
SMEMAINE\Domain Users:(special access:)
Everyone:F
CREATOR OWNER:(OI)(CI)(IO)F
CREATOR GROUP:(OI)(CI)(IO)(special access:)
Everyone:(OI)(CI)(IO)F
----------------------
from a DOS shell we run the fixp.cmd passing it the folder name 'aaaatest'.
The batch file contains the single line:
cacls "\\NSERVER\CFS\%1" /C /T /G "SMEMAINE\Domain Users":F
------------------------
running cacls again with the following:
N:\aaaatest SMEMAINE\Domain Users:(OI)(CI)F
Everyone:(OI)(CI)(special access:)
SMEMAINE\george:F
CREATOR OWNER:(OI)(CI)(IO)F
CREATOR GROUP:(OI)(CI)(IO)F
-------------------------
We use no special permissions so this is about the simplest case you'll find.
Any user authenticated on the domain can now access the folder aaaatest and all the files under it.
Folders and files created subsequently are also accessible to domain users. - We've recently upgraded one of our NAS's to .17 and this ugly little issue has popped up now.
It doesn't matter if we create new folders, or even try older folders... ANY new folder created, is given a default permission set of read-only.
Grevious: Not sure if you're still following this, but I can give you guys access to anything you need, I work directly with Netgear regularly and will provide anything you guys need to finally squash this bug.
As of right now, it's killed productivity to near standstill in several departments, and as you well know, we can't roll back to the previous version of the firmware we were running to revert this problem.
(if you'd like a way to contact me directly to iron out details, let me know and I'll PM you Instant messaging/phone number info)
As of right now, here's a full rundown of everything we have setup.
ReadyNAS 2100 setup running latest .17... I've not run a volume scan or a quota fix since loading .17.
It's setup on a 2003 AD Domain.
NAS Name is: NAS01
Share name is: 'DEPTS'
Permissions on DEPTS set as follows:
CIFS: Default Access - Read/Write
Recycle Bin: 10 days
2Gig
NOT Automatically Setting permissions on new Files and Folders (Though, I could SWEAR we had this checked prior to the update)
Opslocks enabled
I'll give Cacls outputs upon request. - GrievousAspirantSend me the cacls output of a newly created file(created as a user besides the admin account used to add the nas to the domain) as well as the config backup from Frontview. Just send them as logs(instructions are in my signature).
- Have sent the cacls to you via PM, and I'm doing the full config backup as we speak. Will send momentarily.
Related Content
NETGEAR Academy

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