October 5, 20178 yr I wanted to grant a user Write access on a Secure Share. So I granted the user Read/Write permission on the share and applied the changes. The user was still unable to create files/folders on the share. I then looked in the smb-shares.conf file and noticed that the "writeable" property was set to no. When I tried to turn this on for the share I notices it was no where to be found on the UI. Was this removed on purpose?
October 5, 20178 yr I would suggest to start by reading this post and the following dozen or so. They provide a lot of insight into SMB issues and problems that folks often encounter.
October 5, 20178 yr Author The user and password match on both the unRaid server and the PC. I turned the writable option off, and even though the user is listed as having write access the user cannot write to the drive. I have also reboot the user computer and restarted the samba server on unRaid. So if when using a Secure share granting user write access is suppose to work, all I can say is it is not working. There are two user with write access on this share, myself and 1 other user. I have write access the second user does not. I did discover that turning the writable option on, enables all user to write to the drive. I do not desire that so I turned that back off. The share in bold is the one not working. [flash] path = /boot comment = unRAID Server OS boot device browseable = yes # Public public = yes writeable = yes vfs objects = map archive = no map system = no map hidden = no map readonly = yes create mask = 0777 directory mask = 0777 [Apps] path = /mnt/user/Apps comment = Applications browseable = yes # Secure public = yes writeable = no write list = csmccarron,mccarronac vfs objects = [Dockers] path = /mnt/user/Dockers comment = browseable = no # Secure public = yes writeable = no write list = csmccarron vfs objects = [Games] path = /mnt/user/Games comment = Game Files browseable = yes # Secure public = yes writeable = no write list = csmccarron,mccarronac vfs objects = [ISO] path = /mnt/user/ISO comment = browseable = yes # Public public = yes writeable = yes vfs objects = [Movies] path = /mnt/user/Movies comment = Movies browseable = yes # Secure public = yes writeable = no write list = csmccarron vfs objects =[Music] path = /mnt/user/Music comment = Music browseable = yes # Secure public = yes writeable = no write list = csmccarron,mccarronac vfs objects = [Pictures] path = /mnt/user/Pictures comment = Pictures browseable = yes # Secure public = yes writeable = no write list = csmccarron vfs objects = [Quicken] path = /mnt/user/Quicken comment = Quicken Files browseable = yes # Private writeable = no read list = write list = csmccarron,mccarroncs,esmccarron valid users = csmccarron,mccarroncs,esmccarron vfs objects = [Shared] path = /mnt/user/Shared comment = Shared browseable = yes # Private writeable = no read list = write list = csmccarron,mccarroncs valid users = csmccarron,mccarroncs vfs objects = [Users] path = /mnt/user/Users comment = browseable = yes # Private writeable = no read list = write list = csmccarron,mccarronac,mccarronec,mccarroncs,mccarronca,esmccarron,mccarronmp valid users = csmccarron,mccarronac,mccarronec,mccarroncs,mccarronca,esmccarron,mccarronmp vfs objects = [VM] path = /mnt/user/VM comment = Virtual Disks browseable = yes # Secure public = yes writeable = no write list = csmccarron vfs objects =
October 6, 20178 yr You may have fallen victim to this 'bug'/feature of SMB: " Now, after above, you click on a Private share where the only unRaid user with access is "curly". Samba will see the request to the share as user "larry" and tell Windows that the connection is unauthorized (because larry is not in the list of users for the Private share). Windows sees this and presents you with a username/password dialog box. So you enter "curly" as the user. But now Windows sees that you already have a connection to the server as user "larry" and it DOES NOT ALLOW multiple connections to the same server via different user names. This is a well-known limitation/bug in Windows. Some people get around it, e.g., by connecting to the sever using the IP address in order to fool windows into thinking it's a different server. " (Quote from here: ) https://forums.lime-technology.com/topic/25064-user-share-problem/?tab=comments#comment-228392 Note that it says "computer" NOT "user"! You actually have to change the computer name (as I understand it) and not just log out as one user and log back in as a new user. I have often pointed out that SMB started out back in the Windows for Workgroups 3.1 (1992) days as a way to tie a very small number of computers together without requiring a dedicated server. It grew from there into the kludge that it has become today. I have no doubt that a computer running Windows for Workgroups could still access an SMB network today...
October 7, 20178 yr So I tested this on a rc9g release. Here was my experience: I created a new share and set it to Secure via SMB. I gave read/write user access to a user I created called "test" I opened a connection to the server via Windows File Explorer I saw the share I created and double-clicked it. Once in the share, I tried to create a file and Windows just straight up denied me access (like it should). I was NOT prompted to authenticate to the server. I then went back to browsing the shares in File explorer and right-clicked on the share I created and selected Map Network Drive. When given the option, I opted to provide alternate login credentials for connecting to the share. I entered the username / password for the user I created in unRAID. I completed the mapping. I then had file explorer open to my new Z:\ drive which was mapped to my secure share. I was able to create new files / folders and write files. I then renavigated my file explorer to the server address (to browse all the shares again OUTSIDE of the mapped network drive). I opened my secure share and created new files without issue. I then when back to my other file explorer window and disconnected the mapped network drive. I was still able to create new files in the secure share after doing this (figuring that Windows still has the credentials cached on the machine from the mapped network drive).
October 8, 20178 yr Author Shit, I know what the problem is, and it is not the unRaid OS, sorry. The user name on the PC is mccarronacx01 instead of mccarronac. My script uses the USERNAME environment variable to connect the drive. I feel dumb, DAMIT I hate when that happens!
October 8, 20178 yr Shit, I know what the problem is, and it is not the unRaid OS, sorry. The user name on the PC is mccarronacx01 instead of mccarronac. My script uses the USERNAME environment variable to connect the drive. I feel dumb, DAMIT I hate when that happens! Thank you for confirming!!Sent from my SM-G930P using Tapatalk
Archived
This topic is now archived and is closed to further replies.