Orange Pi Zero 3: SMB shares inaccessible from Windows/macOS in 44-dev-36f85209a6 (worked in v43)

[asleugim]

Batocera build version

44-dev-36f85209a6 2026/07/19 12:00

Your architecture

Orange Pi Zero 3 (Allwinner H618, 1 GB RAM)

Your Graphic Processor Unit(s) (GPU)

Integrated Mali-G31 MP2 GPU (Allwinner H618)

Issue description

After upgrading from Batocera v43 to development build 44-dev-36f85209a6, SMB shares are no longer accessible from Windows or macOS.

The same clients worked correctly with Batocera v43. The only change was replacing the Batocera image.

The Samba server is running and Linux clients using smbclient can browse and access the share successfully, but Windows Explorer and macOS Finder cannot connect.

Detailed reproduction steps

1. Flash Batocera 44-dev-36f85209a6 to an Orange Pi Zero 3.

2. Boot the system with the default Samba configuration.

3. Ensure networking is working.

4. From a Windows PC, try to open:

   \192.168.0.141\share

   or from macOS:

   smb://192.168.0.141/share

Expected result:
The shared folder opens normally.

Actual result:
Windows reports "System error 53" (Network path not found) and Finder also cannot connect.

From another Linux machine, however:

smbclient -L 192.168.0.141 -N

and

smbclient //192.168.0.141/share -N

both work correctly.

Details of any attempts to fix this yourself

• Verified smbd and nmbd are running.
• Verified ports 139 and 445 are listening.
• Removed cached Windows credentials.
• Recreated smb.conf.
• Verified configuration using testparm.
• Tested guest access.
• Enabled Samba debug logging.
• Confirmed Linux smbclient works correctly.
• Tested from both Windows and macOS with identical results.

Details of any modifications you have made to Batocera.

No third-party packages were installed.

The only modification was enabling Samba debug logging (log level 10) while troubleshooting.

The SMB share configuration is:

[share]
path = /userdata
writeable = yes
guest ok = yes
guest only = yes
force user = root

Logs and data

Issue is reproducible on a clean installation of Batocera 44-dev-36f85209a6.

Batocera v43 does not exhibit this problem on the same hardware and with the same Windows/macOS clients.

testparm confirms:

• map to guest = Bad User
• guest account = nobody
• guest ok = Yes
• guest only = Yes

However, the Samba debug log shows Windows authentication being rejected instead of being mapped to the guest account:

Got user=[root]
domain=[MicrosoftAccount]

Couldn't find user 'root' in passdb.

NT_STATUS_NO_SUCH_USER

exit_server_common:
NT_STATUS_CONNECTION_RESET

This suggests that "map to guest = Bad User" is not being applied, despite testparm reporting the configuration correctly.

I have attached the complete Samba debug log and Batocera support file.

[dmanlfc]

you will need to remove pre-established connections to shares and then recreate them.
effectively the minimum security changed for smb server on Batocera v44 (upstream change).
therefore once the connections are re-established for Windows & Linux you will be prompted for a username & password.
for MacOS you don't get the prompt. i just tested the image I gave you here and it works fine for both Linux, MacOS & Windows.