I thought that for once a distro upgrade had gone entirely seamlessly and I was settling in nicely to Ubuntu 18.04... until I discovered...
Ubuntu 18.04 cannot discover samba hosts.
It can still connect to them, if you know their names, but it can't see them, so you have to either, in the words of the dude above, edit the configuration file back to an old protocol or "connect to it explicitly by that name .. as in ... smb://hostname or use Connect to Server in Nautilus."
The problem only appears when connecting to Windows boxes or older versions of Ubuntu: if all the machines on the LAN were running 18.04 it would work seamlessly, I hear. (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
waxjism hasn't got around to upgrading, and our media server is also still on 16.04.) (And I did the fix, but having to manually edit conf files before you can see your file shares no longer qualifies as 'seamless', obviously.)
Ubuntu 18.04 cannot discover samba hosts.
"@Morbius1: Bionic Beaver can not discover samba hosts - netbios.
[...]Ubuntu 18.04 contains version 4.7.4 of the samba client libraries which brings with it a lot of improvements but it changes one parameter that will cause this forum nothing but grief. It changes the upper default smb dialect that the samba client uses to SMBv3.11 from the earlier default of NT1 (Samba speak for SMBv1).
Conceptually it should not make any difference to host browsing but what that does is disable host browsing (netbios host discovery). If you go to Files>Other Locations>Windows Network this will be the result:smb3-bug.png
The only way out of this is to edit /etc/samba/smb.conf and override the default by adding a line in the [global] section setting it back to the old default[...]."
It can still connect to them, if you know their names, but it can't see them, so you have to either, in the words of the dude above, edit the configuration file back to an old protocol or "connect to it explicitly by that name .. as in ... smb://hostname or use Connect to Server in Nautilus."
The problem only appears when connecting to Windows boxes or older versions of Ubuntu: if all the machines on the LAN were running 18.04 it would work seamlessly, I hear. (
waxjism hasn't got around to upgrading, and our media server is also still on 16.04.) (And I did the fix, but having to manually edit conf files before you can see your file shares no longer qualifies as 'seamless', obviously.)
