dstiles - 11:19 pm on Nov 16, 2012 (gmt 0)

I seem to have stumbled onto a solution.

It seems fstab is a red fishy thing; although it's possible to use it from terminal via mount.cifs (mount -a) it seem to have no effect on smb4k.

The solution I found was to set Custom Options for the COMPUTERNAME - not the sharename - in the network neighbourhood pane of smb4k. By default it's set to Automatic. I set it FOR THIS ONE COMPUTER ONLY to RPC - all other machines seem to obey Automatic, no idea why. Nor do I really know why smb4k suddenly began to do as it was told for the other computers/shares.

Odd that the older Ubuntu machine starts up all smb4k shares with no problem, and they are all set to Automatic. :(

There is a difference between the Windows computers (obviously!):

One is a Windows 2000 set up as a Web Server - that's the one that failed to connect. Working through possible differences I discovered that kerberus would not start on this machine - no idea if that has anything to do with anything. There may be something odd in the general usage of the machine - all hosts files on the network define the machine's IP for several local domains for testing local web sites that I build/maintain.

A second machine is another Windows 2000 server but set up as a domain controller - that works with smb4k.

A third machine is Windows 2000 Pro (ie desktop only, not a server) and that connects fine.

Hell! It's Friday night, it's suppertime, and there's a DVD I want to watch! :)