Problem Accessing Folder Share from Admin Panel

[JoePatane]

Hi there,

Ever since updating to 6.4.1 on my ReadyNas 104 I'm not able to access one of the folder shares. All other folder shares I can access via the admin and mapped drive in Windows, but there is one folder I'm not able to access via Windows Mapped drive and from the admin panel.

When I click on it on the admin panel it goes through the motion of trying to open it, but then just goes back to the main shares page.

I've enabled SSH access and logged into the nas via SSH as root, to see if I can access that folder via SSH and list the contents and I can without any problems, if I try to ssh as the admin user it just closes putty.

I tried to access the folder via my media streamer (Med8er) and it asked for credentials to access the the folder, entered the correct credentials and I'm able to see the contents and playback via the med8er OK. It's just via the admin area and windows I cannot view the contents of this folder and only this folder, all others are OK.

I'd apreciate some advice on how to fix this, it was working OK last night. I did play around with the permissions on the shares, they are all set the same, yet I can access the other folders OK, but not this one. Is there a way to reset all the permissions on the shares?

Better still if someone can let me know what the default ownerships and permissions should be, I can reset via SSH using chmod and chown.

TIA

Joe

[BrianL2]

Hi JoePatane,

Kindly check this article and see if it helps.

Kind regards,

BrianL
NETGEAR Community Team

[dyerdj1]

Hello, 

Im having the same issue since upgrading to 6.4.1, all my access has suddenly stopped working through my windows PC.

Plex seems to be fine as does READYCLOUD.

I tried to reset all shares to default user access (although it doesnt actually look like its updating at all) by using the link above.

It allows me into the main screen which shows me my 4 shared folders on the NAS, however I cannot seem to get past that....

Ideas?

[JoePatane]

Well as it came... it went, not sure if it's something I did with messing around the permissions or ownerships via ssh, but I was able to access the folder I was having problems with via Windows drive mapping. I still can't browse the contents of this folder via the netgear admin panel in shares, but in all fairness I can live with that now that I've managed to map that share in wondows OK again and my media streamer doesn't seem to have any issues doing any playback, so I'm happy with that.

[T1968]

hi there,

Same problem here...

Windows share to non public share on NAS stopped working after 6.4.1 firmware upgrade.

For the share that is giving trouble the settings box doesn't have the "file access" button. that makes it impossible to restore settings.

Any help is much appreciated!

Thanks,

Theo

[T1968]

edit: 

Home folder settings do not include "file access" whereas public does include this feature.

Suppose this has something to do with the problem. Am I looking at it the wrong way?

Thanks!

[JennC]

Hello T1968,

The Home Folders share does not really file access tab, what it has are the Snapshots and Access tabs.

Protocols that you can use to access the Home folders are under Access tab. Just make sure when you try to access one of the Home folders, you re logged in as either Admin or one of the local users.

Regards,

[T1968]

hello JennC,

Thanks for your reply.

Until yesterday I was able to access my windows share [Z:] as local user. This has been working for as long as I've had the RN102, until it suddenly stopped working after the upgrade to fw 6.4.1. That was the only change.

I'm still able to access the windows share to the public folder. I can even remove and recreate this share.

With the windows share to the home folder this proves impossible.

I'm under the impression that the fw upgrade is causing this. Windows access is impossible from a windows 10 machine and from a windows 8.1 machine.

Looking forward to further assistance, for which thanks in advance!

Kind regards,

Theo

[StephenB]

Try running CMD and entering

net use * /delete

net use z: \\nasipaddress\localuser /user:localuser localuserpassword

substituting the real names for the nasipaddress, localuser, and localuserpassword placeholders.

[T1968]

Hi StephenB,

Thanks, result: system error 5, access denied

Regards,

Theo

[StephenB]

---

@T1968 wrote:

Hi StephenB,

Thanks, result: system error 5, access denied

Regards,

Theo

---

If you right-click on cmd and run it as administrator, do you still get system error 5?

[T1968]

Result is still the same.

system error 5.

access denied.

one thing has changed, it seems (already after initial net use commands): now readynas shows up in explorer. This wasn't the case before running the net use commands.

[T1968]

Might it be that there is something wrong with the smb-protocol?

On the access tab in the home folder settings there is no possibility to configure the smb protocol, whereas I would expect such a possibility (based on information from the RN site)

[BrianL2]

Hi T1968,

Since it's now showing up in your network, were you able to login again as the admin or user and access the files? Also, was this the case on a different PC that uses SMB? 

I look forward to your response.

Kind regards,

BrianL
NETGEAR Community Team

[StephenB]

This works with my OS 6.4.1 systems and my Windows 10 client (without elevating to adminstrator).

The username and the password have to match the account that is configured on the NAS.  

Perhaps try setting a different password for the localuser on the NAS and see if it clears it.

You can also try 

net use * /delete

net use z: \\nasipaddress\data /user:admin nasadminpassword

That should mount the full data volume on z: - including showing the home folder.

[T1968]

hi BrianL,

it is showing up in the left pane in explorer under Network. However that's all, unfortunately... I am still not able to access the home folder. Public folder doesn't give any problems. That seems logical to me, as the public folder isn't exclusively associated with a user.

[T1968]

Hi StephenB

Still running cmd as administrator the command was executed, this time without error.

in explorer however, I don't see Z: showing up. Still only Readynas is shown in the left pane under Network. When I click the "username" folder, windows asks for my credentials (for that specific user). I can use another user (admin), but either way I get the answer access denied.

As far as I can tell, the cmd commands have the same effect as trying to create a network share (assigning a drive letter) in explorer.

[StephenB]

---

@T1968 wrote:

As far as I can tell, the cmd commands have the same effect as trying to create a network share (assigning a drive letter) in explorer.

---

That is correct, but there is no way to do the net use * /delete in explorer, and sometimes the errors are different.

Try the admin command again, but running cmd at the normal privilege level.

[T1968]

Hi StephenB,

now we are getting somewhere!

the command was executed and Z: shows up

when I go to the user folder, I'm able to access it

can I try to connect Z: directly to the correct user folder?

can you explain why on two different machines (one on W8.1 and the other W10) suddenly the shares stopped working?

[StephenB]

---

@T1968 wrote:

 the command was executed and Z: shows up

when I go to the user folder, I'm able to access it

---

Good.  So at least the NAS admin credential is presented correctly.

---

@T1968 wrote:
 can I try to connect Z: directly to the correct user folder?

---

That was what the first commands I posted were supposed to do.

net use * /delete

net use z: \\nasipaddress\localuser /user:localuser localuserpassword

localuser is both the home folder name you are trying to mount and the NAS account name for that folder - and localuserpassword is the associated password for that NAS account. That failed with the system error 5, correct?

What you could try doing is copying the contents of the home folder for that user to the local PC (using the admin mount that works).  Then delete the user from the NAS, and recreate it.  Then mount the folder using the newly created password (remembering the net use * /delete), and restore the folder.

Though if you didn't try just changing the password on the NAS for that account, I'd do that first.

---

@T1968 wrote:

can you explain why on two different machines (one on W8.1 and the other W10) suddenly the shares stopped working?

---

No.  Of course rebooting the NAS was part of the upgrade, so the PC shares would have all disappeared then.  However, you should have been able to remount them with the original user credentials.  So I can't explain it, but instead was trying to see if we can somehow get it back (leaving the cause a windows mystery).

[T1968]

Hi StephenB,

The local user doesn't work, it results in error 5/access denied. But what if I try to access localuser with admin credentials?

I can understand the suggestion of copying and creating a new user, but that doesn't really appeal to me as the amount of data involved is around 350 gigs...

Yesterday and today I have tried to change the password a few times, but I used the same password as the original one. I can try to use a different password.

The new Z: can be a good work around, provided I can use this new share in all programs that need data access on my nas.

[T1968]

Hi StephenB,

after changing the password in the user account on my nas, the command still results in error 5 access denied.

=> user FUBAR?

is there a way to move files to a new user folder directly on the nas?

[StephenB]

You can move the files from the admin mount, but the permissions will be wrong.  That was why I suggested a double move.

Maybe the right next step is to create a new user account, and see if you can mount that directly.

[T1968]

hi StephenB,

permissions are wrong even when using the new Z: as a workaround. Outlook for instance cannot write to pst files, even after changing permissions in windows...

when I try to use a new user (with Y: as windows share to the folder), windows returns a comment that it is not possible to create multiple connections with a server or shared source from a user with multiple user names.

Apparently I have to delete the other windows share Z: before I can make another?!

This didn't pose a problem before, with M: as share to the public folder and Z: to the home folder. If I understand correctly, this has to do with the character of the folders (home or share on nas).

[T1968]

hi StephenB,

Another observation: when I create this new user, in the nas I cannot see a home folder created for this new user. Also in windows explorer it doesn't show up at all.

It looks as if something isn't right with user accounts in my nas?

Please look into the fw upgrade, as my problems coincided with the upgrade to 6.4.1

Thanks a lot for your effort!