![]() ![]() The main problem is that user3-4-5 cannot modifie theirs private folder, because the whole HDD is read-only for them. Valid users = user1 user2 user3 user4 user5 I modified /etc/samba/smb.conf like this: To make this idea more understandable, I created a directory map, where green dir = read/write and red dir = read-only: theirs private dirs) which are readable/writeable for them too. NOTE: You can use the force user parameter in smb.conf to map access to this folder to this single user. You should then be able to connect to the new shared folder with the newly-created user and permissions should work. The rest (user3-4-5) can acces the whole content also, but with read-only permissions. Share the folder in SMBUp if you haven’t already done so. Two of them (user 1, user2) can access the whole HDD (all directory with Read/Write permissions). There are 5 different user (client) who would like to use this server. It works perfectly (i can reach the shared folder). It runs Ubuntu 20.04 LTS Server and use SAMBA to share the content of disk. They may be displayed as nobody4 or nogroup.I would like to configure a homemade NAS. Some Windows NT users and groups cannot be mapped to equivalent UNIX users or groups. Delete the original file in Windows NT and rename the file to its original name. On the UNIX NFS client, copy the file to a different name (you must do it as a user, not as root). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |