Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Bloat]

Hi,

Am I correct in thinking that I can set 'share' permissions through the web interface of the DNS-320 (fw 2.0), but I cannot set Folder/File permissions?

e.g.

My DNS-320 is configured with IP 192.168.0.10
The root 'Volume_1' is shared (by default) and both my user accounts, user1 and user2, have read/write permissions
I create a folder called Test in 'Volume_1', share it, and configure user1 to have read/write, but deny access to user2
If user2 tries to connect to \\192.168.0.10\Test he is unable to access it, but
If user2 tries to connect to \\192.168.0.10\Volume_1, he is able to and then able to browse to the Test subfolder

The only way I have found to configure the device in a way that is usable for me is to remove access to the 'Volume_1' share and then share each subfolder separately and configure appropriate permissions, being mindful that any subfolders of any shares will be accessible in accordance with the parent's share permissions.

Being a Windows man, and knowing very very little about Linux, I am unsure if this is correct.  In Windows usually share permissions are set so everyone has write access, and permissions are set on files/folders.

Can anyone shed any light??

Thanks

Bloat

[ivan]

If you share the root volume to everyone then all can see everything in it.  Just stop sharing the root volume and just share the folders as you want.

[levi4884]

I'm trying to do an identical setup.  When your User2 browses to your \\192.168.0.10\Volume_1\ can he then browse a level deeper into the "Test" folder without issue, even though you have Test configured to not allow User2 access?  That's the issue I'm having and confused about.  User2 is denied access when hitting the \\192...\test\ share directly, but if they browse to the main volume_1 share they can then browse into to the Test folder without issue.  That doesn't seem correct to me...still trying to figure out how to fix that.

[Bloat]

Ivan - Yup, thought so... thank you

Levi - Yes, user2 can browse subfolders if he can access the 'Volume_X' share.  The permissions are share permissions and not file/folder permissions.  As I thought/Ivan says, you need to remove access for everyone to the 'Volume_X' share(s) and then share each child folder contained within and assign permissions as you require

This way a user can't connect to the 'Volume_X' share and browse all the subfolders to 'bypass' the other permissions you have configured