samba - Sep 2001 - smbd won't start!! Please help!!

Hi.

We have had SAMBA running successfully at work here for a while, it's on a
Sun Sparc Solaris 2.6. The version of samba is 2.0.0.

Unfortunately our sysadmin has left the company, and I have to try and fix a
problem with Samba. When I try and start samba, "nmbd" starts ok, but
"smbd"
doesn't start.
When I check the log files, I get these errors:
[2001/09/24 13:50:41, 1] smbd/files.c:file_init(219)
  file_init: Information only: requested 10000 open files, 1014 are
available.
[2001/09/24 13:50:41, 0] lib/util_sock.c:open_socket_in(663)
  bind failed on port 139 socket_addr=192.168.XXX.YYY (Address already in
use)

I've replaced our IP address with XXX and YYY.

Can anyone please help me with this, or at least point me in the right
direction of where to start!!

Much appreciated. Thanks

Mike Salway
Technical Manager, Core Solutions
SchlumbergerSema
Phone: +61-2-99294111
Fax: +61-2-99294199
Email: Mike.Salway@sema.com.au <mailto:Mike.Salway@sema.com.au> 
Web: www.slb.com <http://www.slb.com/> 
----------------------------------------------------------------------------
--------
This correspondence is for the named person's use only. It may contain
confidential or legally privileged information or both.
No confidentiality or privilege is waived or lost by any mistransmission. If
you receive this correspondence in error, please immediately delete it from
your system and notify the sender. You must not disclose, copy or rely on
any part of this correspondence if you are not the intended recipient.
Any views expressed in this message are those of the individual sender,
except where the sender expressly, and with authority, states them to be the
views of Sema Australasia Pty Ltd, trading as SchlumbergerSema
 
 
-------------- next part --------------
HTML attachment scrubbed and removed

On Mon, 24 Sep 2001, Mike Salway wrote:

The magic line is this:
>   bind failed on port 139 socket_addr=192.168.XXX.YYY (Address already in
use)
Something is already listening on port 139; check the output of netstat
- you might want to look for existing smbd processes (or inetd listening
on that port). If you can't find the process, get and install lsof and
go looking for it.


-- 
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk
...You're visualising the _duck_ taped over my _mouth_..?