[Samba] OS X 10.4.11 Tiger cannot write to Samba 4.5.12 file server with vfs_fruit enabled

[Keith Kaisershot]

Thanks for the response, Ralph. Unfortunately the Tiger systems are PPC
machines which can’t run 10.6. Is there a way to get SMB1 and Netatalk to
play nice together without relying on vfs_fruit? Failing that, is there a
way for Samba to enable vfs_fruit selectively, such as only if I’m
connecting using SMB2, and leaving it disabled if older clients are using
SMB1?

K

On Nov 5, 2017, at 5:09 AM, Ralph Böhme <slow at samba.org> wrote:

On Mon, Oct 30, 2017 at 11:11:55PM -0700, Keith Kaisershot via samba wrote:

Hello, thought I’d post here before opening up an issue on Bugzilla, just
in case…

I’m setting up a combination Samba 4.5.12/Netatalk 3.1.11 file server on
Debian Stretch (kernel version 4.9.0-4-amd64), servicing a network
containing Windows, macOS, and OS X Tiger 10.4.11 systems. As I understand
it, vfs_fruit is necessary for proper interoperation with Netatalk 3, so I
have that enabled on my server.


vfs_fruit leverages Apple's SMB2 protocol extensions, but OS X 10.4 doesn't
support SMB2, you need at least 10.6 (iirc).

-slow

-- 
Ralph Boehme, Samba Team       https://samba.org/
Samba Developer, SerNet GmbH   https://sernet.de/en/samba/