NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Home folders visible in admin page but not accessible
Have two NAS's, both with 6.10.8. Running Win 10. Both have only one user---the admin--me. The one I have been using the home folder for some time without issue. The other one, I recently wa...
Normally the home folder itself will not show up in the shares list. Each user account on the NAS will have a shared folder inside "home". That is created the first time that user accessed the NAS using SMB with their account credentials. That will show up in the shares list when you access via Windows or Finder.
If you are seeing "home" in the share list for your other NAS, then you are accessing that NAS using its admin credentials (and the admin account is not using the default password). In that specific situation, you will see the full data volume in the share list, as well as "home".
Note that in that case, data\home\admin, \home\admin, and admin are just different paths to the same folder. That's also true for data\sharename and sharename.
Thank you for your reply, and I think I understand what you say, but I'm not sure I expressed my issue correctly?
The one NAS works exactly as expected.
The other NAS shows a home folder on the admin page, but does not show any subfolder for "admin". In other words, it doesn't seem to have been created the first time I accessed the NAS using SMB with my account credentials? Said another way, I have a 'data\home directory, but do not have a data\home\admin directory?
Is their a way to force its creation now that the NAS is in full use with other shares and data?
Ray2 wrote:
The other NAS shows a home folder on the admin page, but does not show any subfolder for "admin". In other words, it doesn't seem to have been created the first time I accessed the NAS using SMB with my account credentials? Said another way, I have a 'data\home directory, but do not have a data\home\admin directory?
Is their a way to force its creation now that the NAS is in full use with other shares and data?
Did you ever access the NAS from a PC using the admin credentials? (using windows explorer, not your browser)?
Perhaps a bigger question - do you actually need that private folder?
Stephen B:
..........Did you ever access the NAS from a PC using the admin credentials? (using windows explorer, not your browser)?
Yes, I can view both NAS's very well from File Explorer which is what I assume you mean.
............Perhaps a bigger question - do you actually need that private folder?
Your question implies will do I have an absolute need? No.
But I do have a need/use for it which is why I noticed my inability to do so in the first place.
Ray2 wrote:..........Did you ever access the NAS from a PC using the admin credentials? (using windows explorer, not your browser)?
Yes, I can view both NAS's very well from File Explorer which is what I assume you mean.
No, the ask was focused on "using the admin credentials" bit.
Try entering this from CMD:
net use * /del /y net use t: \\nas-ip-address\data /user:admin nas-admin-passwordof course using the real NAS IP address and admin password. See if that triggers the creation of the folder.
Be careful on the typing:
- each command needs to be on its own line,
- spaces matter.
- the two different slash directions also matter.
Note the first command terminates any open SMB sessions (it doesn't actually delete anything). The second attempts to mount the full data volume as drive letter T.
And you are logged on both as "admin"?
If so, are you comfortable with the Linux command line via SSH? I ask because we need to see if the share really doesn't exist of if the GUI just doesn't know about it. The solution is different for each case and both solutions are from SSH.
By way of how you got here: Did you at any time have two volumes and destroy or export one? If so, and the one you destroyed was the primary volume, that may have been the cause. I ran some experiments some time ago (so under an older version of the OS), and found that destroying or exporting, while it's clearly intended to create a new home folder, sometimes does not do it properly.
Sandshark:
.....And you are logged on both as "admin"?
Yes
......If so, are you comfortable with the Linux command line via SSH? I ask because we need to see if the share really doesn't exist of if the GUI just doesn't know about it. The solution is different for each case and both solutions are from SSH.
I have not used Linux commands via SSH. But I am a quick study if you will share with me how to access? I am comfortable with the old DOS C: prompt and old dos commands.
......By way of how you got here: Did you at any time have two volumes and destroy or export one? If so, and the one you destroyed was the primary volume, that may have been the cause. I ran some experiments some time ago (so under an older version of the OS), and found that destroying or exporting, while it's clearly intended to create a new home folder, sometimes does not do it properly.
I do not recall doing either a destroy or export on this NAS (single volume-RAID 60; however in the past year these disks were moved from a failed NAS to this one--seemingly without incident---I simply moved them, keeping them in order and they fired right up on this replacement NAS as if nothing had happened. Of course, prior to doing that, I have no recollection if the home\admin folder existed because I didn't have a need/use for it at the time.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
