Add source, SMB comes back with 2 workgroups seen. My home workgroup and the default WORKGROUP. Both Pis show up in WORKGROUP even though the config screen shows my home workgroup. The presence of WORKGROUP is intermittent, sometimes it appears, sometimes not.
Add source, zeroconf can see the SMB shares on the other Pi and is a LOT faster then browsing SMB.
I have managed to add the sources then play media from the other Pi.
Do I need to SSH and modify a config file somewhere to edit the workgroup name?
I did find the following which appears to have the wrong protocol but no workgroup name.
lock directory = /home/osmc/.kodi/.smb/
client max protocol = SMB3
name resolve order = bcast host
include = /home/osmc/.kodi/.smb/user.conf
I think its a case of the MyOsmc affects the SMB client settings, but when you install the SMB server from the app store you have to configure that yourself where it doesn’t behave as you wish. There used to be an extra file in /etc/samba to add local settings, and that is where I set my workgroup for the server and some other site preferences (overriding the /etc/samba/smb.conf)
From what I have learnt during this. A copy of /etc/samba/smb.conf needs to be mace called /etc/samba/smb-local.conf with the ‘source’ first line removed or commented out. Changes made here are permanent and not overwritten by upgrades.