[Samba] Difference between share access from Windows and Linux

[Ingo Asche]

Hi Rowland,

thanks for the answer...

I'm totally with you, the problem lies with Synology. Just wanted to be 
sure.

As you may have read in my other mail today directed more to Travis, I 
could create a workaround through changing a library to an older one.

The name libidmap-samba4.so indicates it has something to with the id 
mapping. Any thoughts from your knowledge and experience why there is 
something different between Windows and Linux workstations? Maybe you 
have a helpful hint.

I'm just hoping for some munition against Synology, as I'm no developer 
myself. They test every time from Linux and say there's no problem. Of 
course there's no problem, because it happens only from Windows.

Regards
Ingo
https://github.com/WAdama

Rowland Penny via samba schrieb am 24.05.2023 um 09:50:
>
>
> On 24/05/2023 08:36, Ingo Asche via samba wrote:
>> Hi All,
>>
>> I have a - maybe dumb - question:
>>
>> What is the difference between an access to a Samba share from Linux 
>> and from Windows?
>>
>> Is there a difference in protocol or getting share rights or anything 
>> else? I think I remember that there is.
>>
>> Maybe someone can push into the direction of a documentation.
>>
>> Base for this question is a ticket I have open with Synology. There 
>> is in newer versions of the SMBService (their version of Samba) a 
>> problem with getting access rights to shares through groups. Only 
>> with Windows workstations, not from Linux workstations.
>>
>> I found out with changing a Library from an older Version it works 
>> again, but they couldn't second it, because they still test from Linux.
>>
>
> Samba is the Linux attempt to emulate the SMB protocol and as such, it 
> shouldn't matter what you access a Samba share from, they should all 
> work the same.
>
> However, as you seem to be aware, synology samba != Samba. They take 
> Samba (an older version at that) and mangle it for their own uses. So 
> if you can connect to a Samba share correctly from Linux, Windows or 
> anything but synology, then that looks very like a synology problem 
> and they will be the only people who will be able to fix it.
>
> Rowland
>
>