SAMBA stopped working

[Tillman, Brian (AGRE)]

A few months ago, SAMBA V2.2.8 on my three VMS system (two OpenVMS VAX V7.2 and one OpenVMS Alpha V7.3-1) stopped working.  Since I'm the only one actually using SAMBA connections to the VMS systems, I didn't bother to investigate.  Today I decided to, but before I did, I updated the Alpha only to the most recent V2.2.8.  On the Alpha, I noticed that the SMBD service in TCP/IP was disabled, even though TCPIP SHOW CONFIG SERVICE showed it as enabled (i.e., should start on demand).  I enabled the service and restarted NMBD.  The NMBD processes on the VAXes were already running.

Despite that, the Windows "My Network Places" didn't show the systems.  I stopped the NMBD processes and cleaned out all logs and then restarted NMBD.  The workgroup and machines then appeared in My Network Places.  However, when I tried to open any of them, I was prompted for a username/password over and over.  I get no errors in any log, except for this showing in NMBD_STARTUP.LOG:

$ define SOCKETSHR UCX
$!
$set ver
$ arch = f$getsyi("ARCH_NAME")
$ nmbd :== $samba_exe:nmbd
$ opt = f$trnlnm("SAMBA_NMBD_OPTIONS")
$ nmbd "-d1" "-i"
Netbios nameserver version 2.2.8 started.
Copyright Andrew Tridgell and the Samba Team 1994-2002
standard input is not a socket, assuming -D option

I don't know if that last line is normal.

If I check the modification times of the files in the SAMBA tree, besides the Alpha executables, the following changed today:

Directory SAMBA_ROOT:[PRIVATE]

SECRETS.TDB;1         1-NOV-2004 10:43:54.83
SMBPASSWD.DAT;2       1-NOV-2004 10:43:54.60

Directory SAMBA_ROOT:[VAR]

LOG.SMBD;1            1-NOV-2004 10:43:50.12
NMBD_STARTUP.LOG;103
                      1-NOV-2004 10:27:17.74
NMBD_STARTUP.LOG;102
                      1-NOV-2004 10:26:51.32
NMBD_STARTUP.LOG;101
                      1-NOV-2004 09:36:52.01

Directory SAMBA_ROOT:[VAR.LOCKS]

BRLOCK.TDB;1          1-NOV-2004 10:43:54.74
BROWSE.DAT;1          1-NOV-2004 10:53:23.53
CONNECTIONS.TDB;1     1-NOV-2004 10:43:54.88
LOCKING.TDB;1         1-NOV-2004 10:43:54.78
MESSAGES.TDB;1        1-NOV-2004 10:43:54.86
NMBD.PID;1            1-NOV-2004 10:27:19.27
NTDRIVERS.TDB;1       1-NOV-2004 10:43:54.92
NTFORMS.TDB;1         1-NOV-2004 10:43:54.97
NTPRINTERS.TDB;1      1-NOV-2004 10:43:54.95
PRINTING.TDB;1        1-NOV-2004 10:43:54.90
SHARE_INFO.TDB;1      1-NOV-2004 10:43:54.99
UNEXPECTED.TDB;1      1-NOV-2004 09:35:46.78

Here's my SMB.CONF file.  This was working before and I haven't changed anything on the VAXes except for stopping and restarting the NMBDs:

[global]
   workgroup = Swdev
   dead time = 10
   map archive = no
   load printers = no
   security = user
   default service = default
   create mode = 0777
   server string = %h running Samba V%v (SWDEV)
   username map = /samba_root/lib/users.map

   guest account = UCX$NOBODY
   log file = /samba_log/log.%m
   lock directory = /samba_root/var/locks
   share modes = no
   encrypt passwords = yes
   oplocks = no
   level2 oplocks = no

[homes]
   comment = Home Directories
   browseable = no
   read only = no
   create mode = 0750

[Tillman]
   comment = Brian's login directory
   path = /a305_disk/tillman
   valid users = tillman tillmabg
   public = yes
   writable = yes
   printable = no
   create mask = 0765
--
Brian Tillman

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************