Only change was upgrade to 4.1.9 over the weekend on ReadyNAS 1100.Now, one user is unable to access a particular share. Confirmed in AD (using Domain Security Mode) that account is not locked and could login to user's account on domain, so have proper password.In viewing user/group list on NAS, it shows the user in question listed, so in theory it is synchronizing with AD properly.Of 15 members in same group as this user, the one is question is only one having problem. I've tried logging in to shares as the problem user from my computer and it does not work (Mount Share As different user), but mounting share as my user still works just fine.What would cause a single user's permissions not to work on the ReadyNAS share when it worked for 2 years straight, the password is confirmed correct, AD account is not locked, is still a member of same group that has Read/Write rights to the share, and all other users working just fine.Is this a 4.1.9 issue, or does someone have another suggestion?

Pulled logs.---Sample log entry prior to 4.1.9 upgrade yesterday---[2012/08/03 17:52:58, 2] auth/auth.c:check_ntlm_password(309) check_ntlm_password: authentication for user [sharp] -> [sharp] -> [AIMC\sharp] succeeded---Sample log entry after 4.1.9 upgrade---[2012/08/06 08:25:39.009177, 2] auth/auth.c:314(check_ntlm_password) check_ntlm_password: Authentication for user [sharp] -> [sharp] FAILED with error NT_STATUS_NO_SUCH_USER

There are some security and ownership issues known to 4.1.9, and its suggested to downgrade to 4.1.8 or upgrade to 4.1.10 beta and turn off automatic updates. Although your error message seem to indicate that the NAS doesn't recognize the user. Does AD create local users or does the user authenticate with the AD server?

Since the upgrade process took a couple of hours, I can't do the downgrade during business hours. I saw a mention of people having to downgrade, was hoping my issue was unrelated.I'm not quite sure I follow your question. Active Directory is a server and therefore would be a server based user authentication. They are Domain Users (default group, in fact) and credentials are authenticated to the domain. Does that answer your question? Sorry if I am missing your point here.

My question might have been somewhat unclear. I'm not familiar with how the user authentication works between the NAS and AD. Thats why I asked the question, but while thinking a tad further; Does the NAS create users in AD or does it use already created users in AD?Since the NAS don't recognize the user its not definite that it can be blamed on the firmware, but it wouldn't hurt as a last resort to try a downgrade. The upgrade process itself shouldnt take as long as that (just guessing here, again not familiar with the 1100).There are some reports that some shares are inaccessible after upgrading to 4.1.9 on some users but not everyone, so its still a viable guess.

That makes more sense and to be honest with you, I am not 100% sure if the ReadyNAS periodically syncs with the AD server to obtain users and groups, or if it polls the AD server every login/connect attempt by a user.If it is the latter, then I would think that since the user exists on the User/Group report listing on the ReadyNAS, it would simply have responded with a valid user when connecting and not indicate the user did not exist.I wonder how the 4.1.9 issues were not detected prior to public release? The NAS seemed to be operating a bit quicker this morning than with 4.1.8, but if we trade off a little speed boost for failed connectivity, I guess we will roll back down to 4.1.8 tonight until 4.1.10 is out of beta and has been tested in the wild for a little while.

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

26 Replies

Replies have been turned off for this discussion

mrwilliams1
Aspirant
Aug 07, 2012
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.8). 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-ntgr
NETGEAR Employee Retired
Aug 07, 2012
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?
mrwilliams1
Aspirant
Aug 07, 2012
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-ntgr
NETGEAR Employee Retired
Aug 07, 2012
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.

mrwilliams1

Aspirant

Aug 07, 2012

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-ntgr
NETGEAR Employee Retired
Aug 08, 2012
Have you tried contacting NetGear tech support to see if they have any suggestions?

Forum Discussion

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

26 Replies

Related Content

Unable to access 'access control' Orbi 770 RBE771

Unable to access NAS via WIN11 File Manager

unable to access router admin page due to https

Unable to access RN304 and RN102

Netgear Armour unable to unblock access

NETGEAR Academy

ProSupport for Business