Use that always, except when performing admin duties.Hi everyone! Yep it’s a permission issue thread again Maybe they don't have contents yet? The users must add that. When I browse the network from a client workstation I can currently see "home" and "homes" but cannot drill down into them to see their contents. There is seldom a need to muck around there. If you don't know what it's for, then stay away from that (stay far away). That's covered automatically by the homes service.ĭo I want to enable "Advanced Share Permissions" on the share? What does this actually do? I assume I don't want to start going down the track where I create top-level shares like \\mysyn\fred or \\mysyn\susan unless you made them all admins (admins can see everything), or you screwed with /homes (or /home) permission Users should never see /homes, only their own stuff. Will synology user permissions protect the individual user subfolders under home on a per-user basis even if all users have access to \\mysn\homes? Never much with permissions on these folders. If you change permissions on /homes (or /home) you will make unrecoverable changes that cannot be fixed simply by reverting permissions. To make this happen should i grant read/write to all of these users on the common share "home"? Users should store their personal stuff under their /home/username/. Should users generally access and store their own stuff with network paths such as \\mysyn\homes\susan\documents or \\mysyn\homes\fred\music? With a user login you will only see your personal /home/username folder, not /homes/. Use that login only for NAS admin duties, not for storing your personal files, streaming, downloading, etc. You're apparently logged in as an administrator. I no longer remember whether I created this or if it was automatically created for me. It appears that I have a share "homes" that currently isn't granted to most users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |