Need help with new installation of Samba 3.5.8

Aaron Albertson albertaa at us.ibm.com
Mon Apr 11 13:54:06 MDT 2011



Hi all,

We have had an installation of samba 3.0.4 running for a long while, but
recently our auditing software flagged this as too old, so we needed to
download and install a more modern version.  I downloaded version 3.5.8 of
samba, and I was able to use my notes from the last time that I built samba
to get the new version built successfully.  We are running the software on
the AIX platform.  I am having two issues with the new installation of
samba:

1) I am unable to start the nmbd server unless I use the '-d 10' option
(lesser debug options do not allow the server to start).  The nmbd server
puts the following messages to the log file when it fails (IP addresses
obfuscated manually):

[2011/04/11 14:02:56.095282,  0] lib/util_sock.c:880(open_socket_in)
  bind failed on port 137 socket_addr = x.x.xxx.xxx
  Error = The socket name is not available on this system.
[2011/04/11 14:02:56.096543,  0] nmbd/nmbd_subnetdb.c:118(make_subnet)
  nmbd_subnetdb:make_subnet()
    Failed to open nmb bcast scoket on interface x.x.xxx.xxx for port 137.
      Error was The socket name is not available on this system.
[2011/04/11 14:02:56.097545,  0] nmbd/nmbd.c:963(main)
  ERROR: Failed when creating subnet lists. Exiting.

As mentioned earlier, for some reason I do not get this message when '-d
10' is specified.

2) When the nmbd server does start, my attempts to mount the drives have
failed.  I began working on the samba checklist, and encountered these
messages when running the 'smbclient -L' command:

.../samba/lib> smbclient -L xxxxxx
Enter xxxxx's password:
Receiving SMB: Server stopped responding
session setup failed: Call returned zero bytes (EOF)

The log.smbd file contains some errors about ISO8859-1 being unsupported
and/or not being loaded, but other comments lead me to believe that these
errors are just noise.

I have checked my smb.conf settings (which are the same as before) and the
tool reports no errors in the smb.conf file.  I would appreciate any
insights you might have.

Thanks!


More information about the samba-technical mailing list