>I'm running bo, and I've installed samba. When, from the command line >I type > > smbd -D > >and then > ps -aux | grep smbd > >I do not see the smbd running. When I look in /var/log I get > > Added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0 > bind failed on port 139 socket_addr=0 (Address already in use) > >When I type > > nmbd -D > >and do > > ps -aux | grep nmbd > >I see the demon running. Also, I am able to see sharred directories >on other machines.
Im not an expert, but it seems to be an already binded port. Ok, less technically: every service/daemon/program using TCP/IP (or UDP) on a machine needs a connection point called "port", where clients can connect to. smbd uses port 139 and nmbd uses port 137 (see /etc/services for protocols and there correspondent ports, smbd uses netbios-ssn, nmbd uses netbios-ns). Another famous examples is the http-protocol used by web-servers and -browsers on port 80. So in our case some service/program has port 139 already in use and 137 was still free. The question is now how to find out which daemon blocks 139. I would suggest a glance to /etc/inetd.conf. Search for netbios, maybe another daemon has an entry using the port. Second, you can use "lsof" as root and search for TYPE inet. There you can find the daemon locking port 139, I hope. HIH, Juergen
