As with all Windows boxes, the old Lenovo Q150 (dual booted with Win 7 Home Premium) became slow and cranky, despite not being used for anything other than monthly science and annual taxes. Various fixes and tweaks being unavailing, I swapped in an Optiplex 780 (dual booted with Win 7 Pro), replaced the IBM L191p monitor with the recapped Dell 2005FPW, reinstalled all the programs, and discovered that Samba was intermittent.
For future reference…
Win 7 Pro includes the Remote Desktop Protocol server that’s missing from Win 7 Home Premium. Oddly, RDP works better than UltraVNC, using Remmina as a client.
The file server in the basement runs Xubuntu 14.04 with Samba 4.1.6 and works perfectly with
smbclient, showing no glitches at all. Even when the Win 7 box doesn’t show the server shares at all, it’s rock solid to my desktop Xubuntu box.
sudo service samba restart doesn’t actually do that any more, so get used to the two-step dance:
sudo service nmbd restart sudo service smbd restart
However, that sometimes seems to start a spurious third copy of
smbd (there should be two, for unknown reasons), so it’s better to use a four-step dance:
sudo service nmbd stop sudo service nmbd start sudo service smbd stop sudo service smbd start
The old SysV init system wasn’t good enough, so they invented the run-all-the-things upstart, then systemd Borged upstart, all while Samba, one of the most critical Windows interfaces, still hasn’t emerged from the original init scripts. They call this progress, but I’m not sure.
Telling the Samba server to not be the domain controller, which should resolve intermittent pissing matches over who’s on first, had no effect.
When the Win 7 box does show the shared files, everything works fine: files read & write with the proper permissions, the owners & groups are fine, all is right with the world. In between those moments, however, nothing works, because the share simply doesn’t appear.
Then, seconds or minutes or tens of minutes later, it’s back!
map to guest = bad password, as found in the usual random blog comment, had no effect.
The most recent Samba update replaced the
/etc/samba/smb.conf file, so we’ll restart from scratch and see what happens next.
My general approach to Samba has been to futz around until it mysteriously starts working. That seems not to be of any avail this time around; we may put the tax data on a USB stick and move on.