I installed Samba 2.0.0 on a P100 running SlackWare Linux 96 (Kernel 2.0.0). After running configure, make, make install, and testparm, I thought I was all ready to start up the smbd daemon. So I typed in smbd -D -d 50 Got back a failure listing in the error log. [1999/02/01 16:27:06, 0] lib/util_sock.c:open_socket_in(663 Brian Lee Bowers | Division of Government Research Computer Aide I | University of New Mexico dgr0bb@unm.edu |
Also sprach Brian Bowers --- 10:39 AM 2/2/99 +1100> >I installed Samba 2.0.0 on a P100 running SlackWare Linux 96 (Kernel >2.0.0). After running configure, make, make install, and testparm, I >thought I was all ready to start up the smbd daemon. So I typed in > smbd -D -d 50 > >Got back a failure listing in the error log. >[1999/02/01 16:27:06, 0] lib/util_sock.c:open_socket_in(663I am currently struggling with an SMP Slakware 3.5 machine that was happily running kernel 2.0.36 and samba 1.9.18p8. I can't say for sure but i think your system is a bit "old" for samba 2.0. I would suggest that your easiest action would be to find a later 1.9.? version of samba and install that. Or, get Linux 2.0.36 and install that. Hopefully most of your support packages will be current with that. If you go with Linux 2.2 you will need about 6 new packages (/usr/src/linux/Documentation/Changes) _,--" `-._ ________-_______ "---- _----'--'--------------------------------'--'----_ //_| | \ Dick Balaska / | | _\\ (_____|_|__= Waterbury CT +1.203.757.6994 =__|_|_____) _\_____=___ http://www.buckosoft.com/ ___=_____/_ \/-(o)-~~-(o)-~~-(o)-`------'-(o)-~~-(o)-~~-(o)-\/ mail successfully read: Please reboot and reinstall Windows.
Hello My /var/log/samba/log.smb shows the following error bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) Can anyone tell me how I can determine what is using the port? Thanks in advance. Jim H Mailed with Netscape 4.5 on RedHat Linux 5.2 2000 years ago the Egyptians treated cats as Gods. They never got over it.
I've searched the archives for an answer on this and found the problem mentioned, but never found the answer. I've been working on this for two days with no luck so need the help of someone smarter than I. Here's the problem: smb doesn't start. When starting smb (by running /etc/rc.d/init.d/smb start) everything seems to go smoothly, but if I then check the status, I get the following: smbd is stopped nmbd (pid xxxx) is running.... The log.smb file shows the following error: bind failed on port 139 socket_address=0.0.0.0 (Address already in use) I found one reference in the latest samba HOWTO that indicated a message about a bind problem on port 139 indicated that another samba process was probably running and suggested executing: ps auxww |grep mbd The result was the nmbd process which automatically restarts, even when I stop smb--which I suppose is not the problem. This server has been up for months--I'm not sure what happened that introduced the problem. Here's my environment info: --RedHat Linux 6.0 (Linux i386 kernel that shipped) --Samba 2.0.5a (although I've tried two earlier 2.x versions trying to solve the problem) Help please! TIA, Bruce.... -------------- next part -------------- HTML attachment scrubbed and removed
> "Bruce W. Miller" wrote: > > The log.smb file shows the following error: > bind failed on port 139 socket_address=0.0.0.0 (Address already in > use)grep the /etc/inetd.conf file and make sure that smbd/nmbd are not being started from there. jerry ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have recently installed SuSE 8.1. Previously this workstation ran SuSE 7.2 with Samba server without problems. Since the latest installation inet.d loads nmbd on boot but smbd fails. testparm /etc/samba/smb.conf returns "Loaded sevices file is OK" Log files /var/log/samba/log.smbd shows: [2003/04/09 20:48:41, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use nmblookup query to server results in following: The only service listed in /etc/services to bind to port 139 is as follows: netbios-ssn 139/tcp # NETBIOS Session Service netbios-ssn 139/udp # NETBIOS Session Service /etc/inet.d shows: entry in the inet.d file shows as follows netbios-ssn stream tcp nowait root /usr/sbin/smbd smbd netbios-ns dgram udp wait root /usr/sbin/nmbd nmbd Smbclient confirms the server setup is correct as follows: Ariel:/home/meyrick # smbclient '\\Ariel\TMP' added interface ip=62.190.243.241 bcast=62.190.243.255 nmask=255.255.255.0 Password: Domain=[FAMILY] OS=[Unix] Server=[Samba 2.2.5] smb: \> Network - - - I can successfully ping localhost, my own fully qualified host.domain.name (Ariel.Hedge-analytics.co.uk) & IP address (62.190.243.241). - - - From the client I can ping the server on IP address (62.190.243.241) but CANNOT ping using the fully qualified domain name (Ariel.hedge-analytics.co.uk) I have changed nothing on the client PC since installation of SuSE 8.1, so settings on the newly installed SuSE 8.1 probably at fault. Hostname & domain name are correctly set in the client PC running Windows 98. Thanks for your help. - - -- Meyrick Chapman -----BEGIN PGP SIGNATURE----- Comment: trusted mail iD8DBQE+lzTJKNEcTU/K/ggRAmIgAJ4/eiI+gY0PFeNybT3quLKK1tfWpACeMG+3 p5psqvuYaA/CFs8XT9F5bWA=LHOu -----END PGP SIGNATURE-----