nmbd

[Joel Hammer]

I am not sure why nmbd is not binding that socket. The usual reason (linux)
is that some other program is already binding it (usually another copy of
nmbd).
This isn't permissions. nmbd is not suid but I can bind 137 as a regular user.
Maybe 
netstat -an | grep 137 
might show a process binding this port.
udp        0      0 0.0.0.0:137             0.0.0.0:* 
(This is my nmbd process, at the local port listening to all ips.
If your version of netstat supports -p, try
netstat -anp | grep 137
It also shows the process ID binding that port.
Joel


> 
> [2001/10/07 23:49:13, 1] nmbd/nmbd.c:main(684)
>   Netbios nameserver version 2.0.5a started.
>   Copyright Andrew Tridgell 1994-1998
> [2001/10/07 23:49:13, 0] lib/util_sock.c:open_socket_in(886)
>   bind failed on port 137 socket_addr=192.0.0.168 (Can't assign requested
> addres
> s)
> [2001/10/07 23:49:13, 0] nmbd/nmbd_subnetdb.c:make_subnet(135)
> nmbd_subnetdb:make_subnet()
>   Failed to open nmb socket on interface 192.0.0.168 for port 137.  Error was
> Ca
> n't assign requested address
> [2001/10/07 23:49:13, 0] nmbd/nmbd.c:main(742)
>   ERROR: Failed when creating subnet lists. Exiting.
> 
> > 4. What you see with ps ax | grep nmbd
> 
> Nothing