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
- GrievousAspirantNot everything slated for 4.2.16 is necessarily in the current public beta.
- ConnAspirant
Grievous wrote: Not everything slated for 4.2.16 is necessarily in the current public beta.
No response to the other posts? - GrievousAspirant
Conn wrote: Grievous wrote: Not everything slated for 4.2.16 is necessarily in the current public beta.
No response to the other posts?
In this thread? No. I already stated that if I have more information, I'll post more information. Someone asked a question about the likelihood of it being in 4.2.16 because it's not in the beta, and I simply pointed out that the current public beta does not necessarily have every feature/fix slated to be in the final build. - jyarboroughAspirantGrievous - Seriously?! Thats it?! So no other updates? This is a pretty major issue for some of us with no real work around. I understand you guys need to research, develop, test, etc, and do not want to disclose things about release dates, etc, but come on! Throw us a bone of some kind. Is this issue even on the to-do list for 4.2.16? Based on your previous responses you would update the masses "if [you] have more information". I find it pretty hard to believe that you do not have any "more information" after a month and a half.
- ConnAspirant
Grievous wrote: In this thread? No. I already stated that if I have more information, I'll post more information. Someone asked a question about the likelihood of it being in 4.2.16 because it's not in the beta, and I simply pointed out that the current public beta does not necessarily have every feature/fix slated to be in the final build.
You (or someone else) can't answer this?devgav wrote: Having the same problem. File permissions are a MESS, and seem to take ages to propergate. I'll make a file permission change, and nothing will happen until about an hour later - when I'll suddenly find it's decided to block all users.
Any update on this?
Grievous - an ETA would be nice, even if it's rough - and as asked by several users, what did you do to recreate this issue? If we know how you turned a working system, into a non-working system, then we may be able to work around this.
Many thanks. - GrievousAspirantNo, we don't give out every detail of our development and testing procedures.
Guys, look. I said I'd update the thread when I have more information. Getting hostile and jumping down my throat about things isn't going to get anything accomplished. If it keeps up I'll have to lock the thread, I'd rather not. Remember, I'm also an admin. - ConnAspirant
Grievous wrote: No, we don't give out every detail of our development and testing procedures.
Guys, look. I said I'd update the thread when I have more information. Getting hostile and jumping down my throat about things isn't going to get anything accomplished. If it keeps up I'll have to lock the thread, I'd rather not. Remember, I'm also an admin.
I think part of the issue is that when nothing is reported back on here, people assume this issue is not being looked at. Even posting on here every other week that you're still working on this would be helpful. - GrievousAspirantIt's simple, I'd rather post "I'll let you guys know in this thread when we have more information" than posting "nothing new yet" on a daily or weekly basis. Also, just because I haven't replied to each post on an individual basis, doesn't mean that I haven't been keeping up with posts in this thread, as I get an email every time someone replies, and I check the thread to see what it's about.
- sicabreAspirantHi Grievous,
We understand what your are saying. I worked with some US and UK netgear engineers and i hope i found a workaround.
Now the UK engineer told me. Make new shares and set BASIC permissions and copy the folders over. Your NTFS permissions want be restricted but users can read/write/modify in it. THis is for the customer acceptable. MY customer is currently saying : Ok no problem, if the workaround is to make new shares and put basic permissions on in font vieuw and all users can access data. Then that's the workaournd.
Now that's what we are missing here. You are telling us that you will let us know when something will change. Now what do you think what we can say our customer who we promoted readynas? " Look customer, the readynas is a neat thing, but it has a bug. When we ask the developers of netgear they say; we know it's a issue but we haven't more information". It's all about communicating with us. We promoted netgear with several customers because it's really neat stuff. But this is not the way how to communicatie with us. Remember, people paid for functionality that doesn't work and we don't know if you addressing this issue.
We don't need all the details, but give us information so we can share it with customers so they know somebody is working on it. This customer now is really thinking about returning the readynas as i can't give him the information he wants. He's okay with the workaround but when is there a final resolution? - GrievousAspirantI understand that, but if I don't have anything to communicate to you, you still don't have anything to tell the customer. Make sense? I could go to the extreme of posting every 5 minutes saying "We're still working on it but it's not done yet" but that doesn't accomplish anything either. If I don't have anything to tell you, I can't post anything. As I've said, when I have information I will post it, asking me to post info I don't have will not get either of us anywhere.
Related Content
NETGEAR Academy

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