samba - Dec 2002 - error message in smbd.log file: bind failed on port 139 socket_addr = 0.0.0.0.

I can run nmbd successfully, but smbd dies almost immediately when I run 
it, the smbd.log file has the message "bind failed on port 139 
socket_addr = 0.0.0.0.".  When I do a netstat -an | grep 139, it shows 
that tcp is listening on port 139.  How do I resolve this conflict 
between tcp and smbd?

tcp is a transport protocol. It isn't a daemon. You have not understood the
output.
Post the output of netstat -anp | grep 139.
Is xinetd or inetd or smbd listening to this port?
Joel


On Sun, Dec 29, 2002 at 09:03:16PM +0000, phil brogan
wrote:
> I can run nmbd successfully, but smbd dies almost immediately when I run 
> it, the smbd.log file has the message "bind failed on port 139 
> socket_addr = 0.0.0.0.".  When I do a netstat -an | grep 139, it shows
> that tcp is listening on port 139.  How do I resolve this conflict 
> between tcp and smbd?
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

> tcp is a transport protocol. It isn't a daemon. You have not
 > understood the
 > output.
 > Post the output of netstat -anp | grep 139.
 > Is xinetd or inetd or smbd listening to this port?


I tried netstat -anp | grep 139 and I see that it is indeed xinetd which 
is listening on that port.  How do I resolve this conflict?

> > tcp is a transport protocol. It isn't a daemon. You have not
 > > understood the
 > > output.
 > > Post the output of netstat -anp | grep 139.
 > > Is xinetd or inetd or smbd listening to this port?
 >
 >
 > I tried netstat -anp | grep 139 and I see that it is indeed xinetd
 > which
 > is listening on that port.  How do I resolve this conflict?

I removed xinetd's files for netbios-ns and netbios-ssn, started nmbd 
and smbd and they are running.  Oddly enough, I created the netbios-ns 
and netbios-ssn files for xinetd as per instructions from Jerry Carter's 
book "Teach Yourself Samba in 24 Hours".  Why would that book tell me
to
do something that breaks Samba?

Anyway...

I did an smbstatus, got error message "Failed to open byte range locking 
database", fixed it by using command "smbclient -L localhost".

I went to a Win98 machine, did a "net view \\linux-computer-name" and 
received an Error 53 message from Windows "The computer name in the 
network path cannot be located."  Yet I can ping linux-computer-name by 
name from the Win98 box.

Any help would be appreciated, thank you.

Thanks!  I found that DIAGNOSIS.txt is also delivered with the binaries,
I found it in /usr/share/doc/samba-2.2.7a/docs/textdocs.

> I would walk through DIAGNOSIS.txt, which comes with the samba
sources.
>
> Joel
On Mon, Dec 30, 2002 at 02:26:15AM +0000, phil brogan
wrote:
>  > > tcp is a transport protocol. It isn't a daemon. You have not
>  > > understood the
>  > > output.
>  > > Post the output of netstat -anp | grep 139.
>  > > Is xinetd or inetd or smbd listening to this port?
>  >
>  >
>  > I tried netstat -anp | grep 139 and I see that it is indeed xinetd
>  > which
>  > is listening on that port.  How do I resolve this conflict?
>
> I removed xinetd's files for netbios-ns and netbios-ssn, started nmbd
> and smbd and they are running.  Oddly enough, I created the netbios-ns
> and netbios-ssn files for xinetd as per instructions from Jerry
Carter's
> book "Teach Yourself Samba in 24 Hours".  Why would that book
tell me
to
> do something that breaks Samba?
>
> Anyway...
>
> I did an smbstatus, got error message "Failed to open byte range
locking
> database", fixed it by using command "smbclient -L
localhost".
>
> I went to a Win98 machine, did a "net view \\linux-computer-name"
and
> received an Error 53 message from Windows "The computer name in the
> network path cannot be located."  Yet I can ping linux-computer-name
by
> name from the Win98 box.
>
> Any help would be appreciated, thank you.
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba