[Samba] bind failed on port 137 socket_addr=0.0.0.0 (Address already in u se)

[Joel Hammer]

This may be happening because there is already a version of nmbd running.
You may inetd or xinetd watching that port. Does anything show up with:
netstat -apn | grep 137  ?
Joel

On Tue, Apr 09, 2002 at 04:28:20PM -0700, Jon Houg wrote:

> Hi,
> 
> I am attempting to setup a Samba server on a Linux RH 7.1 machine and I am
> getting the following error in the "/var/log/samba/log.nmb" file:
> 
> [2002/04/09 15:59:44, 1] nmbd/nmbd.c:main(758)
> Netbios nameserver version 2.0.10 started.
> Copyright Andrew Tridgell 1994-1998
> [2002/04/09 15:59:44, 0] lib/util_sock.c:open_socket_in(867)
> bind failed on port 137 socket_addr=0.0.0.0 (Address already in use)
> 
> Here is the contents of the [global] section of my "smb.conf" file:
> 
> [global]
> 
>    workgroup = PS_SD
>    guest account = nobody
>    keep alive = 30
>    printing = bsd
>    printcap name = /etc/printcap
>    load printers = yes
>    print command = /usr/bin/lpr -r -P%p %s
>    lpq command = /usr/bin/lpq -P%p
>    lprm command = /usr/bin/lprm -P%p %j
>    preserve case = yes
>    short preserve case = yes
>    case sensitive = no
>    interfaces = 10.3.132.13 127.0.0.1
>    encrypt passwords = yes
>    smbpasswd file = /etc/samba/smbpasswd
>    bind interfaces only = true
>    socket address = 10.3.132.13
> 
> I've modified this file include "bind interfaces only = true" and "bind
> interfaces only = false", with and without the "127.0.0.1" entry in the
> "interfaces" stanza and with and without the "socket address" entry.  I've
> checked to see if port 137 is in the listening state using "netstat -l -n"
> (it is not) and if it's being started in the /etc/inetd.conf file (it is
> not).  I am still getting the above error.  When I do a "netstat -l -n |
> grep 137", I get this:
> 
> netstat -l -n | grep 137
> tcp        0      0 0.0.0.0:13782           0.0.0.0:*               LISTEN
> 
> tcp        0      0 0.0.0.0:13722           0.0.0.0:*               LISTEN
> 
> udp        0      0 0.0.0.0:137             0.0.0.0:* 
> 
> Could the first 2 entries be causing the problem?  If that isn't it, I'm not
> sure what to look for next.  Any help will be greatly appreciated.
> 
> Thanks,
> 
> ============================================================================
> =============
> Jon Houg
> Peregrine Systems
> jon.houg at peregrine.com
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba