samba - Oct 1999 - bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)

I can't figure out what is causing the error message of 

[1999/10/13 11:39:42, 0] lib/util_sock.c:open_socket_in(671)
  bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)

in my logs and thus preventing smbd from serving up connections.

How can I track down what is causing this?  Samba has been working great
and now I must have done something but I don't know what.  The only
network service that I have added and since removed is squid.

Samba 2.0.3
Linux w/ kernel 2.2.12

Thanks,

Brian Servis
-- 
------------------------------------------------------------------------
Mechanical Engineering              |  Never criticize anybody until you  
Purdue University                   |  have walked a mile in their shoes,
servis@purdue.edu                   |  because by that time you will be a
http://www.ecn.purdue.edu/~servis   |  mile away and have their shoes.

On Thu, Oct 14, 1999 at 02:55:35AM +1000, Brian Servis wrote:
> I can't figure out what is causing the error message of 
> [1999/10/13 11:39:42, 0] lib/util_sock.c:open_socket_in(671)
>   bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
> in my logs and thus preventing smbd from serving up connections.
	It means that something else (possibly inetd or another copy of
smbd) is sitting on port 139 and preventing smbd from binding to it.
> How can I track down what is causing this?  Samba has been working great
> and now I must have done something but I don't know what.  The only
> network service that I have added and since removed is squid.
	Get a copy of "lsof" and run the command "lsof -i tcp" and
look
for what process is bound to port 139.
> Samba 2.0.3
> Linux w/ kernel 2.2.12
> Thanks,
> Brian Servis
> -- 
> ------------------------------------------------------------------------
> Mechanical Engineering              |  Never criticize anybody until you  
> Purdue University                   |  have walked a mile in their shoes,
> servis@purdue.edu                   |  because by that time you will be a
> http://www.ecn.purdue.edu/~servis   |  mile away and have their shoes.
	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (770) 331-2437   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!

Samba was working fine and "suddenly" stop to work.
When I check using "ps -ef | grep mbd" is not daemon running
When I use "netstat -a" I have tcp port 139 listen.
I checked inside "/etc/inetd.conf" I do not have reference to that
port
neither samba command. ALso 139 is not inside "etc/services"
if I use "testparm" I get "loaded services file OK"
I run samba with:
/usr/local/samba/bin/smbd -D -a
and
/usr/local/samba/bin/nmbd -D -a

Inside
/usr/local/samba/var/log.users I have this message error:
bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)

In /usr/local/samba/var/log.nmb I have this message error:
bind failed on port 137 socket_addr=0.0.0.0 (Address already in use)

Any help will be apreciate ....Not Unix expert....Thanks
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.