----- Original Message -----
From: "Yao Weiyin (??????)" <yaoweiyin@online.sh.cn>
To: <samba@samba.org>
Sent: Tuesday, October 31, 2000 7:44 PM
Subject: I can't make nmbd started
> File log.nmb say:
Can't bind to socket usually means something else is using the socket. You
probably have nmbd running already. Do a netstat -an
netstat -an | more
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
udp 0 0 x.55.134.y:138 0.0.0.0:*
udp 0 0 x.55.y.173:137 0.0.0.0:*
udp 0 0 0.0.0.0:138 0.0.0.0:*
udp 0 0 0.0.0.0:137 0.0.0.0:*
> ------------------------------------------------------------------------
>
> [2000/10/31 14:09:42, 1] nmbd/nmbd.c:main(757)
> Netbios nameserver version 2.0.7 started.
> Copyright Andrew Tridgell 1994-1998
> [2000/10/31 14:09:42, 0] nmbd/asyncdns.c:start_async_dns(150)
> started asyncdns process 1269
> [2000/10/31 14:09:42, 0] lib/util_sock.c:open_socket_in(863)
> bind failed on port 137 socket_addr=0.0.0.0 (Address already in use)
> ------------------------------------------------------------------------
>
> So I changed the socket_addr in the advanced view. Unfortunately this
> action affected nothing to the nmbd.
> The file log.nmb displayed the same information.
> What can I deal with it?
>
>
> Larry Yale
>