Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Running FW 1.05 and even though there is no such user created within the Admin UI, this user on XP can still map to Volume_1. Tried creating a user + group and attaching a specific folder on Volume_1\folder and user is still able to map to Volume_1. Does network access management not work with XP?
Offline
ok, noticed that after upgrading from FW1.04 to 1.05, permission were set to ALL. Now that I have created a new user ID + PW, no matter what I try, I can't seem to log in to a specified folder within Volume_1. Even tried mapping using the "Connect using a different user name" and XP still cannot connect. The user on the NAS has the same password for logging into XP. Any ideas?
Offline
What user created the folder you are trying to access? Could this be a question of what user / group has rights on that folder? If the new user you created does not match either of those, you may not be able to access it. You may want to consider telnetting in and checking who owns it.
Offline
THe admin (who has global access) created the folder. But if network access works properly, wouldn't the NAS be able to let other users use it based on the users & groups read & write permissions? If not, the only way to have the user create the folder is to give ALL permission, have the user create the folder, then pull ALL permission and then create new permissions. THis doesn't sound like a good way to manage network access for multiple users. Any ideas on how to deal with this?
Offline
No, it does not work that way. The directory or file gets the permissions from who creates it (the owner). In this case user 'admin'. Now, you need to look at what permissions were actually given the the directory or file. For example drw-rw-r-- shows that the file is a directory, the owner can read and write to the file, the group that the owner belongs to can read and write to it, and finally all other users can only read from it.
Unless your other users are in the same group as the owner, then they will only be able to use the anyone rights. In the example above that would be read.
What you are confusing here are the Samba rights assigned to users and the filesystem access rights. An example would be a user that you set-up with read only access. If that user tries to write to a file that has write access to everyone, the user will still not be able to write because it is being blocked at the Samba share level.
To write to files, the user first has to have write access for the Samba share, then the user must have write access to the file, also.
This device is designed for very basic file sharing out of the box. It is a Linux machine and the D-Link interface to it is limited -- after all, it is a low cost device. If you want to set-up more advanced user / group permissions, then you will need to do it manually from the shell prompt. There are several people here that have done this by puting a script in the /ffp/start directory (of course running ffp fun_plug) to copy their config files over to the NAS on start-up.
Offline
I have read your reply a few times and I think it's beginning to set in. So it looks like the simple UI won't allow 1 user to only have access to a folder inside volume_1. Is that correct?
Offline
Not neccesarily. You can use the UI to set the share to a specific folder for a specific user. When this is the case, that specific user needs to map to the share specifically set-up. Here is an example:
user = jim
share = HOME
path = \Volume_1\home\jim
access = R/W
user = john
share = Volume_1
path = \Volume_1
access = RW
Now, john would map to \\<dns>\Volume_1 and would have access to everything on drive (to the extent of the filesystem permissions).
User jim needs to map to \\<dns>\HOME and he would have access \Volume_1\home\jim, and anything below that level (to the extent of the filesystem permissions).
That being said, user jim CANNOT map to \\<dns>\Volume_1\home\jim. When trying to do that, he is actually trying to map the to the share "Volume_1" and the subdirectory of "\home\jim" within that share. User jim does not have permission to access share "Volume_1"; he only has access to share "HOME", and that is why he cannot access it.
So, in a nutshell, yes, you can assign a specific folder to a specific user, but it needs to be mapped correctly.
Try not to confuse the Drive "Volume_1" with the Samba share "Volume_1". Thay are two different things that just happen to correspond in name and that share "Volume_1" maps directly to "Volume_1". You can actually name the share any name you want and still map it to the Drive Volume_1.
Last edited by bq041 (2008-08-14 06:00:48)
Offline
ok, a big kudos goes out to bq041. You did it. You helped us sort out the network access issue. So instead of trying to map to \\<dns>\Volume_1\home\jim, we had to map to the SHARE name. Doh! So everything works now. This should be a sticky given all the network access issues on this board!
You can actually name the share any name you want and still map it to the Drive Volume_1.
Is it possible to rename the SHARE name using the default UI? If so, where is that function hidden?
Offline
No, it has to be done via fun_plug. I only said that to make clear the point of how Samba works, not neccessarily how the web UI on the DNS works.
Last edited by bq041 (2008-08-14 17:06:21)
Offline