NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unable to save permission changes ... parameter is incorrect
ReadyNAS Pro 4
RAIDiator 4.2.19
I have a share that has been working perfectly for months, since it's creation. I have had no issues adding or removing users from the share via \\readynas-name\c using Active Directory ACL's. The share has functioned perfectly, allowing only the ACL users access. Suddenly today when I try the exact same thing as before I get the error message indicated in the subject line above. I'm logged into Windows from a domain controller as the exact same user I always use to manage the share (the domain administrator) and everything. What now?
RAIDiator 4.2.19
I have a share that has been working perfectly for months, since it's creation. I have had no issues adding or removing users from the share via \\readynas-name\c using Active Directory ACL's. The share has functioned perfectly, allowing only the ACL users access. Suddenly today when I try the exact same thing as before I get the error message indicated in the subject line above. I'm logged into Windows from a domain controller as the exact same user I always use to manage the share (the domain administrator) and everything. What now?
6 Replies
Replies have been turned off for this discussion
- bedwardsnexlearn
Have you tried the process of leaving and rejoining the domain? Sometimes this will fix the issue. If that does not work; then you may want to try exporting and importing the domain ID map. Also, do you have multiple Domain Controllers on the network? If you do, did you specify the IP address of this Domain Controller when you were joining the domain? - If I unjoin then rejoin the domain, will that affect people who are currently using files stored on the NAS?
I don't recall if we specified the IP address of the domain controller originally or not. That DC has since been demoted and a new DC put in place. The old DC was an SBS server, the new DC is not. - So ... no dice. Unjoined domain, rejoined domain. Tried applying ACL again, exact same result. Next option?
- bedwardsnexlearn
Go into the share listing, select the share's CIFS, then select advanced. Change the owner information to "nobody" and "nogroup". Make sure to check the box below that states that it will set the share options to the above information; then apply. When you apply, it will act as though it didn't change. Don't worry, it did. Then you will want to go and disable, then re-enable CIFS under Services > Standard File Protocols. After that is all said and done, give it another try. These steps may interfere with production. So to be sure that you aren't interrupting someone or something; you may want to schedule downtime or do this after hours. - I may give that a try before re-creating the share. I noticed that other shares on the same NAS are not experiencing this issue so I'm leaning towards just re-creating the share from scratch. I probably screwed something up on this one myself, months ago, and forgot about it. Thanks for the ideas though!
- Not a problem, I've seen this happen before. I don't know why or what happens to cause it. I just try to get you back up and running. Those last steps have been useful in the past. So if you run into it again, it never hurts to try.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
