Checking for spam from NM, I instead found this nonsense:
Jun 6 00:01:19 zooty nmbd[2999]: [2021/06/06 00:01:19.675514, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jun 6 00:01:19 zooty nmbd[2999]: Packet send failed to 192.168.2.255(137) ERRNO=Operation not permitted
That 192.168.2 network isn't really there, it is a bridge setup that has nothing connected except for some special virtual machines that sometimes use it but are almost never running.
So I found the interfaces config options for smb.conf and made those messages stop, but the web is full of info telling me I no longer need netbios on Windows 10, yet when I stop the nmb service, my Windows 10 virtual machine cannot mount the shares it normally mounts from my fedora box.
Anyone know if it is really possible to get rid of nmb? (The only systems mounting shares are windows 10.)
On Mon, 7 Jun 2021 09:50:52 -0400 Tom Horsley wrote:
Anyone know if it is really possible to get rid of nmb? (The only systems mounting shares are windows 10.)
Found it! If I re-enable the avahi stuff I had turned off, Windows can apparently use that for "discovery" instead of nmb, so I can get rid of nmb by enabling avahi, and the Windows 10 systems still mount shares OK.
On Mon, 7 Jun 2021 10:55:12 -0400 Tom Horsley wrote:
so I can get rid of nmb by enabling avahi, and the Windows 10 systems still mount shares OK
Better and better! I can turn avahi back off and install wsdd from the repos, and with a bit of configuration not only do shares still work, but my fedora system shows up in the network browser in windows 10 for the first time ever.
-
Tom Horsley