[Bug 286821] net/samba420: fails to work with macOS clients

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 15 May 2025 14:29:52 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286821

            Bug ID: 286821
           Summary: net/samba420: fails to work with macOS clients
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: samba@FreeBSD.org
          Reporter: dim@FreeBSD.org
             Flags: maintainer-feedback?(samba@FreeBSD.org)
          Assignee: samba@FreeBSD.org

I've been running net/samba419 for a long time now, successfully accessing it
with both Windows 10-11 and macOS 13-15 clients.

However, with net/samba420 this no longer works. With a fairly basic
configuration, e.g.:

[global]
        bind interfaces only = Yes
        interfaces = hn0
        security = USER
        server string =
        fruit:aapl = yes
        fruit:zero_file_id = yes
        idmap config * : backend = tdb
        server smb encrypt = desired
        vfs objects = catia fruit streams_xattr zfsacl
        log level = 4


[homes]
        browseable = No
        comment = Home Directories
        read only = No


[root]
        comment = Root of All Evil
        path = /
        write list = @root

I can connect this Samba server just fine from a macOS client, but as soon as I
attempt to actually access a share, macOS pops up an error box "There was a
problem connecting to the server", with "The share does not exist on the
server. Please check the share name and then try again".

After much debugging and trying various things, I ended up at a strange
conclusion: whenever I start nmbd, smbd etc via the rc.d script, they do _NOT_
work correctly, but if I simply login as root and run /usr/local/sbin/nmbd and
/usr/local/sbin/smbd directly, they work.

Any ideas as to what might be going on? I heard from other people that they
also had troubles with 4.20, but these may be different.

-- 
You are receiving this mail because:
You are the assignee for the bug.