I’m not sure I understand you…
in my case whitelisting the folder containing the shares like in the example above, did the trick.
the old config for example is working again without changing anything.
smbclient -L localhost -U%
not showing shares is normal I think under these circumstances,
as is not being able to directly access smb://hostname/ since a couple of major updates ago
but being ignorant, I leave this up to the more experts here to shed some light on this matter.
by specifying hostname and share name explicitly I’m able to access all configured shares
this works for me on the Linux box and from any other windows10/11 machines on our lan.
Disabling AppArmor did the trick for me. My Samba shares are including symlinks, mounted directories from veracrypt and other specialties and I just for the love of god could not make AppArmor accept these shares as exception in usr.sbin.smbd. Not the ideal solution, but at least a workaround for now.
I installed a fresh copy of Manjaro (manjaro-kde-21.3.7-220816-linux515.iso), which doesn’t come with apparmor by default (not in /etc/default/grub or systemctl), and I’m getting the same issue when adding users to shares within Dolphin:
net usershare add: cannont convert name “my_username” to a SID. The transport connection is now disconnected.
I’m having the same problem, and whitelisting the paths didn’t seem to solve it. Had to temporarily disable apparmor. Is apparmor useful anyway? I’ve been using Manjaro for years and never know its existence