On 07/09/2019 02:03 PM, Mathias Homann wrote:
Oh, before I forget, I can access all other samba shares in the way they are intended to be used.
Here's the [global] and [homes] part of smb.conf:
The only things that stand out are:
[global] catia:mappings = 0x22:0xa8,0x2a:0xa4,0x2f:0xf8,0x3a:0xf7,0x3c:0xab,0x3e:0xbb,0x3f:0xbf,0x5c:0xff,0x7c:0xa6
[homes] inherit acls = Yes vfs objects = catia
Those could be correct for your setup, I am unfamiliar with the mappings and vfs objects. The inherit acls can also be tricky. Within the past week there was a discussion on the samba list about acls and denied access. The crux was that for access, the acls should be set by Windows. That is a likely place to look. I have no problems with home access using: [homes] browseable = No comment = Home Directories read only = No
behold:
lemmy@akari:~> df -h . Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf /dev/mapper/system-users 252G 150G 91G 63% /users/lemmy lemmy@akari:~> smbclient -U lemmy //akari/lemmy Enter EREGION\lemmy's password: Try "help" to get a list of possible commands. smb: \> ls NT_STATUS_ACCESS_DENIED listing \* smb: \>
in other words, I can not access my own home via samba anymore.
And here are the two dreaded sentences: "It used to just work" and "I didn't do anything".
The discussion on the samba list centered around changes in the latest Win10 19H03 feature update that caused problems. You may google or look at the samba list archive for details. I would comment out the acls and restart samba to test. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org