Some users unable to access share, AD mode (4.1.9)

[mrwilliams]

I thought I knew what I was doing until I performed the upgrade without first checking the forums for feedback. That much is on me. I'll try to SSH into the secondary machine and compare share permissions to the primary.

I do see a user indicating they had to reapply permissions over SSH every reboot? Was this simply because they failed to downgrade to 4.1.8 prior to trying this?

[mdgm]

Yes on 4.1.9 the problem would reappear every reboot.

[mrwilliams]

Shares.conf match on each server. Linux permissions match for on main shares for each user. Windows Advanced Security Settings for folder matches. What am I missing?

To be clear, I have no had any reported access issues to base shares (e.g."DOCUMENTS" share) or the majority of the folders in it. However, we have a few key folders inside of this share (e.g. "DOCUMENTS\IT") that are inaccessible. These folders ("IT") have identical permissions to our failover/backup NAS (running 4.1.8 without having done 4.1.9 ever).

I know of another share's subfolder (share is "LICENSING", folder is "LICENSING\Faxes") that a user is unable to access since the upgrade yet I and other users are able to hit without error.

Quite perplexing...

[mdgm]

What about if you try 4.1.10 beta? 4.1.9+ includes in a major samba update. It's possible that the samba downgrade could be related to the issue.

[mrwilliams]

Would you rate the 4.1.10 beta as being ready for production environment?

[mdgm]

Yes

[mrwilliams]

I nuked the DOCUMENTS share completely. I then recreated the share in Frontview (following here: http://www.readynas.com/?p=1987) then performed a full restore from off-site backup (including folder permissions) overnight (thankful for fast Internet connection). The backup was from day prior to upgrade (from a known to be good state on 4.1.. Again, all Windows permissions reflect properly.

Our IT dept still cannot access our primary folder on the DOCUMENTS share even though Windows permissions indicate we should. Our COO, who also has access to this folder, is able to get in just fine. He is not located in any other groups beyond where our dept is.

Again, very perplexing. Could you please indicate specifically how an upgrade to 4.1.10 will correct this issue? What was incorrect in 4.1.9 and how will 4.1.10 address it?

[mdgm]

4.1.10 is 4.1.9 with the ownership issue fixed.

If you were doing a full restore from backup did you downgrade to 4.1.8 then do that restore or did you stay on 4.1.9?

[mrwilliams]

This was after a downgrade.

History:

• Upgraded to 4.1.9
• Problems
• Downgraded to 4.1.8
• Problems remained
• Applied full permissions over SSH and Frontview, problems remained
• Nuked share, rebuilt it, restored data w/ permissions from known good backup (prior to 4.1.9 upgrade)
• Problems still remain

Is there not a more technical answer than "ownership issue fixed" ? What caused it? Does it fix it automatically simply by upgrading, or are further steps required?

Sorry, just a bit more cautious on upgrading the firmware after 4.1.9 experience, especially when considering to a BETA release.

[mdgm]

The issue will not reoccur after moving away from 4.1.9 to 4.1.8 or 4.1.10 beta.

Using the Advanced Options tab (Shares > Share Listing > Sharename > CIFS, select Advanced Options tab at the right) you can set the owner and group and click "Set Permissions for existing..." and click Apply. There's a good guide to configuring permissions here: How to Setup ReadyNAS Permissions

Edit: that guide focuses on user mode. Some things will still be relevant to AD users but some things won't.

[mrwilliams]

I did perform the suggested step:

Using the Advanced Options tab (Shares > Share Listing > Sharename > CIFS, select Advanced Options tab at the right) you can set the owner and group and click "Set Permissions for existing..." and click Apply.

after rolling back to 4.1.8 and it did not resolve our issues. That is why I do not see why simply going to 4.1.10 is going to make it any better if it was supposed to work on 4.1.8. I don't think the development team or many users on here rely on Active Directory for the units. I think that is why this particular issue is not getting resolved. If it were simply another security mode I am sure the suggestion would fix it. Perhaps we have outgrown the ReadyNAS product line.

[mdgm]

Have you tried contacting NetGear tech support to see if they have any suggestions?