Satellite MacOS Finder and Samba

[Burroughs70]

Good morning, guys and happy isolation Sunday to all of you!
I've almost finished setting my Zgemma H7S (OpenATV 6.4) up and everything seems to be working fine so far (waiting for some freezes, though!) but there's a strange thing I cannot explain yet.
On my MacBook Pro (Catalina on) I can access all the hosts belonging to my network and the decoder, of course, is one of them.
Finder (MacOS file manager) can access the Samba server, the folder that I've shared and so on, but... the network icon of the decoder is not represented by a monitor (as it should be) but by a question mark.


My configuration file, about Samba, has these settings:

root@satty:~# cat /etc/samba/distro/smb-global.conf
[global]
        # CVE-1999-0519 and CVE-2000-1200
        access based share enum = yes
        restrict anonymous = 2
        server signing = mandatory

disable netbios = No
          min protocol = SMB2         
    ea support = yes   
    smb ports = 445
    wins support = yes
    wins server = satty

    workgroup = AJA
        security = USER
        guest account = nobody
        map to guest = Bad User
        username map = /etc/samba/private/users.map
        min receivefile size = 16384
        use sendfile = Yes
        aio read size = 16384
        aio write behind = true
        aio write size = 16384
        smb passwd file = /etc/samba/private/smbpasswd
        passdb backend = smbpasswd
        idmap config * : backend = tdb
        obey pam restrictions = Yes
        max stat cache size = 64
        unix password sync = Yes
        pam password change = Yes
        server multi channel support = Yes
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    
    fruit:metadata = stream
    fruit:model = MacSamba
    
    #Disable printer support for now
        disable spoolss = Yes
        load printers = No
        printcap name = /dev/null

        unix extensions = No
        allow insecure wide links = Yes

        oplocks = yes
        kernel oplocks = yes

        include = /etc/samba/distro/smb-branding.conf
        include = /etc/samba/distro/smb-shares.conf
        include = /etc/samba/distro/smb-vmc.conf

        include = /etc/samba/smb-user.conf

I know it's not a real problem, but it's quite annoying as it seems that MacOS is not aware of the kind of network resource is dealing with...
Any ideas???