A bit of a Samba nightmare
By tdw on Dec 22, 2004
It's been working well for quite some time now as:
A few weeks ago, it also got pressed into service as a caching DNS server, although I'm not entirely convinced that it is any faster than lookups of our ISP's DNS servers.
Anyway, back to the point of the story....
Last week, the PC stopped seeing the Samba file-system on the Linux box. It had previously been listing two entries for it in the Network Neighbourhood, but this dropped to one, and that didn't actually contain a correct view of the shared file-system. I rebooted the PC a couple of times in the hope that this would clear it, but to no avail. The wierdest thing was that one of the PC applications claimed that it was backing up to the shared filesystem on the Linux host, yet no file update was taking place actually on the host!!!!
Yesterday, I decided it was time to investigate further. So, having manually removed the 'NetHood' folder from my 'Documents and Settings' tree on the PC, I found that the PC couldn't actually see the shared file-system at all. In fact, any attempt to reference the Linux box by its WinNS name failed. I then spent a couple of fruitless hours investigating the settings in /etc/sambas/smb.conf, DNS and other wierd and wonderful stuff, only to discover that the Samba name-service daemon (nmd) was not running. D'oh!!! Once this was restarted, the PC immediately 'found' the shared filesystem and I was back in business. nmd did subsequently die another time, but it appears to be stable now, and everything is working okay. The PC only reports one copy of the system too, so that's a good improvement.
I must say that I like Samba, although I can't claim to be that knowledgeable in it. It would be nice if there was an smbfs module for Solaris to make it easier for me to access file-systems on the PC too, but that's a nice-to-have and I can just about manage by copying files to the Linux server.