search for: giguashvili

On 22/11/2020 12:50, Gregory Giguashvili via samba wrote: > After upgrading Samba server from 4.9 to 4.10 version running on RHEL 7.7 > OS, something changed in how Windows clients see the file ownership on the > exported shares. Instead of SID owners, it now shows "Unix User\username" > and "Unix group\groupnam...

On 22/11/2020 13:51, Gregory Giguashvili wrote: > > No, you only thought it worked using sssd on 4.8.x & 4.9.x, but it > didn't work correctly. > > Maybe, but it "worked". Can we speculate what change in 4.10.x > prompted Samba to export "Unix user\username" type of ownership to >...

> > There is no one supporting the use of sssd with Samba, not even Red Hat. > > Now that I know what to look for (thank you, Roland!), I found https://access.redhat.com/solutions/3802321 page explaining how to properly bridge between SSSD and winbind. In essence, the following configuration is in place (copy-pasting main parts of the document for the benefit of those who has no RHEL

> > No, you only thought it worked using sssd on 4.8.x & 4.9.x, but it > didn't work correctly. > Maybe, but it "worked". Can we speculate what change in 4.10.x prompted Samba to export "Unix user\username" type of ownership to Windows clients instead of SID? Is there any option to revert to previous "wrong" behavior as a temporary workaround?

After upgrading Samba server from 4.9 to 4.10 version running on RHEL 7.7 OS, something changed in how Windows clients see the file ownership on the exported shares. Instead of SID owners, it now shows "Unix User\username" and "Unix group\groupname" users. This works fine in all the cases except when Samba share is used for storing Windows user profiles. The workaround

Hello, Samba seems to simulate NTFS like filesystem, but when we tried to create hard link on UNIX partition, which is supported by NTFS, we failed. Of course, both files resided on the same partition... Can anybody explain me wheither I am wrong? Thank you in advance. Giga.