bind failed on port 139 socket_addr= (Address already in use)

Michael H. Warfield mhw at
Wed Oct 13 17:03:30 GMT 1999

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= (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 at                   |  because by that time you will be a
>   |  mile away and have their shoes.

 Michael H. Warfield    |  (770) 985-6132   |  mhw at
  (The Mad Wizard)      |  (770) 331-2437   |
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!

More information about the samba mailing list