[crunkezoid]

Version info:

OS:  Ubuntu 22.04
Installation method:   Flatpak beta
$ flatpak run tv.kodi.Kodi --version
Kodi Media Center 20.0-RC2 (19.90.905) Git:20221219-a184a3a-dirty
Copyright © 2005-2021 Team Kodi - http://kodi.tv

I have two samba shares on "orangered", running Ubuntu and Kodi (see version info above), and "werner", running on a synology NAS:

$ nmblookup orangered
192.168.178.35 orangered<00>

$ nmblookup werner
192.168.178.80 werner<00>

I created a source pointing at zeroconf:// so I can view everything on the network.

(Mostly) successfully browsing to local laptop (orangered) samba via zeroconf:
DEBUG LOG:  https://paste.kodi.tv/ikerokixuz.kodi

Opened the file manager
Open the zeroconf source: it is empty 
Open the parent directory
Open the zeroconf source:  I can see both samba servers -orangered (SAMBA), and werner (SAMBA).
Open orangered server: I can see the Downloads folder.

Unsuccessfully attempting to browse to synology share (werner) via zeroconf
DEBUG LOG:  https://paste.kodi.tv/ovelategon.kodi

Opened the file manager
Open the zeroconf source: it is empty 
Open the parent directory
Open the zeroconf source:  I can see both samba servers -orangered (SAMBA), and werner (SAMBA).
Attempt to open synology server "werner": Kodi displays "couldn't connect to network server"


 I have the a share on werner available as a source and can navigate to it manually (see previous thread https://forum.kodi.tv/showthread.php?tid=371171)

[crunkezoid]

It looks like zeroconf lists IPV6 addresses for the samba shares and these don't actually work (to varying extents).

The laptop share is shown, but entering it isn't working.

The synlogy hub can't be accessed [1]


[1]  relevant part of of log (full versions above)
2023-01-09 13:48:46.855 T:11      debug <general>: CZeroconfBrowserAvahi::resolveCallback resolved service 'werner' of type '_smb._tcp' in domain 'local':
                                                   
2023-01-09 13:48:46.855 T:11      debug <general>: CZeroconfBrowser: dump txt-records
2023-01-09 13:48:46.855 T:78      error <general>: Unable to lookup host: 'fe80::9209:d0ff:fe0e:97f1'
2023-01-09 13:48:46.855 T:78      debug <general>: OpenDir: Using authentication url smb://fe80%3a%3a9209%3ad0ff%3afe0e%3a97f1:445/
2023-01-09 13:48:46.855 T:78      error <general>: SMBDirectory->GetDirectory: Unable to open directory : 'smb://fe80%3a%3a9209%3ad0ff%3afe0e%3a97f1:445/'
                                                   unix_err:'16' error : 'Invalid argument'
2023-01-09 13:48:46.855 T:78      error <general>: GetDirectory - Error getting smb://[fe80::9209:d0ff:fe0e:97f1]:445/
2023-01-09 13:48:46.855 T:78      error <general>: GetDirectory - Error getting zeroconf://_smb._tcp.%40local%40werner/
2023-01-09 13:4

[crunkezoid]

smbclient can view shares using the ipv6 host and port, with:

smbclient -L 'fd00::9209:d0ff:fe0e:97f1' -p 445


It does prompt me for a password, if I suppress it with -N, I get:

session setup failed: NT_STATUS_LOGON_FAILURE