|
|
|
|
|
|
by legal_penguin
1394 days ago
|
|
|
I took the time to debug all the Samba issues between my Pis and Linux + Windows desktop computers. Most of the time there are two separate problems: 1. Samba share is not discovered in the network. All my problems were gone after installing wsdd2. 2. Permissions. Especially Windows clients implicitly try to login with an empty password to check if the share can accessed without one. This can lead to problems with the "map to guest" directive in the Samba configuration. Also the Windows credential storage sometimes saves passwords that did not work and implicitly tries to login. But don't get me started on the Gnome/gvfs client implementation of Samba. I have given up on that. - https://bugs.launchpad.net/gvfs/+bug/1828107 - https://gitlab.gnome.org/GNOME/gvfs/-/issues/307 I put together a small writeup in case someone wants to take a deep-dive: https://blog.hiebl.cc/posts/why-your-samba-config-does-not-w... |
|
|
- gvfs might not support ws-discovery for smb discovery, but neither does macos. They both support dns-sd/bonjour/zeroconf for that; so getting up avahi up and running with advertising the smb service is the easiest way to handle both. Synology does this OOB, for example.
- gvfs is not an implementation of samba. It is a frontend to libsmbclient library from the samba package. Unfortunately, libsmbclient does read smb.conf and adjusts itself accordingly, without the consumers of the library having a say in it. The best way to debug gvfs problems is to start with empty smb.conf.