(2017-05-22, 19:34)raptorjr Wrote: I'm also having some Samba problems, but can't really tell when they started. My current media sources use Samba and work fine, but when I try to browse for a new source the list comes up empty. Previous my server was found, it's using Ubuntu, but now nothing. And that's the reason why I don't really know when the problem started, only browsing for new things that don't work. And not often I need to do that.
My Windows computer finds the Ubuntu server when I browse the network. So I guess the server configuration is good.
I recently installed #521 since I saw some Samba thins was changed, but it didn't help.
This kind of problem may well depend on your server configuration, and specifically which Samba server (you may have several on your network) is your "master browser". If your master browser doesn't support NT1 then you may find you can no longer browse the network for servers from other Samba clients (eg. LibreELEC).
Try running the following:
If you have no results, then you have no servers on your network capable of browsing.
To discover which server is your current master browser, run:
Code:
NUC:~ # systemctl stop nmbd
NUC:~ # nmbd -iFd3 | grep master_browser
check_for_master_browser_success: Local master browser for workgroup WORKGROUP exists at IP 192.168.0.3 (just checking).
In the above example, 192.168.0.3 is my master browser (it's my FreeNAS server, which doesn't support NT1 so "smbtree -N" returns nothing.
Now check if your master browser server is configured with "min procotol = SMB2" (or similar) - if it is, this would explain your inability to browse.
ctrl-c to terminate nmbd, then:
Code:
NUC:~ # systemctl start nmbd
But hold on you say, it was working last week.
Well, yes, it may well have been - that's the "wonder" of Samba, as different servers on your network can become your master browser based on an election process. It can be as simple as depending on the order in which you turn your kit on. If you have some servers supporting NT1 and others not then you might be able to browse the network while one of your NT1 servers is your master browser, but not when it's one of your other non-NT1 supporting servers.
The Samba server in your LibreELEC client can become a master browser (if the wind is blowing in the right direction) and now that it no longer limits the min protocol (as of #0521) it should permit network browsing (assuming it is your master browser).