similar to: smdb bind error

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?

I have upgraded samba to 2.2.7a and cannot print to my printer attached to my BSD machine. I can use the share dirs, etc, but cannot print. My log file contains: [2003/03/17 16:17:19, 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 [2003/03/17 16:18:02, 0] smbd/service.c:make_connection(252) 50163099sp (204.250.145.147)

I am install Samba on a New RS/6000 M 80. I am installing Samba 2.0.7. I have the services and inedt.conf files with the needed entries and have add a program check my entry. I get the following error in the log file and can not figure out what is wrong. [2001/01/17 12:31:59, 0] lib/util_sock.c:open_socket_in(863) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)

Help me ! I cannot start smbd, it immediatly stops, I've got in my log.smb [1999/05/19 14:53:43, 0] lib/util_sock.c:open_socket_in(709) bind failed on port 139 socket_addr=0.0.0.0 (Adresse déja utilisée.) And then It stops, I cannot launch smbd. I my /etc/services, I've got the two lines : netbios-ssn 139/tcp netbios-ns 137/upd and in /etc/inetd.conf netbios-ssn stream tcp

I can't figure out what is causing the error message of [1999/10/13 11:39:42, 0] lib/util_sock.c:open_socket_in(671) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) in my logs and thus preventing smbd from serving up connections. How can I track down what is causing this? Samba has been working great and now I must have done something but I don't know what. The

SAMBA newbie here........New 2.2.8 install on 5.1 AIX, nmbd will not start. Here is my error: [2004/06/29 14:05:29, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 0.0.0.0. Error = Address already in use Any ideas? Thanks !!! Larry S. Singleton lars@thornwood.com Systems Analyst E-Mail Administrator/Webmaster/"Guru in Training" Thornwood Furniture

When I try and load smbd I get this error in the log :- bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) Closing connections 04/02/1998 14:02:01 Server exit (caught signal) I am using Slackware 3 with Linux kernel 2.0.33, and Samba-1.9.18p4. there is no problem with Netbios naming as I can see th Linux machine in Network Neighbourhood and my samba client seems to be

Greetings All: I'm a newbie at Samba and have been attempting to get Samba to run on a BSD box with little success. Looking at hte /var/log/log.smbd file I get some wierd error message: [2003/07/28 13:18:36, 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 Also, in the nmbd: [2003/07/28 13:18:41, 0]

Dear all, I regret that I am very new to this tool from the install side. I have so far altered shares on a running machine only. I have (thanks to Joss for some help already) installed version 3.4.3 under AIX 6.1 giving it our preferred base directory of /opt/freeware/samba/3.4.3 I have copied over the smb.conf file from the source machine (AIX 5.2 / Samba 2.0.7) and tweaked the content of

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

Dear all, I regret that I am very new to this tool from the install side. I have so far altered shares on a running machine only. I have (thanks to Joss for some help already) installed version 3.4.3 under AIX 6.1 giving it our preferred base directory of /opt/freeware/samba/3.4.3 I have copied over the smb.conf file from the source machine (AIX 5.2 / Samba 2.0.7) and tweaked the content of

I did a complete installation of Red Hat 7.2 on my Dell Inspiron 5000 laptop from RH6.2. I had SAMBA running on it fine until I wiped my hard drive and installed RH 7.2. So now I have to learn how to set up SAMBA with xinetd. I saw a newer version of SAMBA on the SAMBA.org web site so I downloaded it. After reading the INSTAll file and following the instructions it created an RPM in:

I moved an entire RH 6.2 server from one CPU to a new one using a tape backup/restore. Everything from the old server is working on the new server, but when SysV starts up smb, the nmbd daemon (2.0.6) exits with an error: create_subnets: No local interfaces! eth0 has already started according to the logs and console. Any ideas? Thanks. ______________________ Greg Kelley, IT Director SSA, EAA,

Hello Everyone, I have installed samba-1.9.17p4 on a linux 2.0.29 box, but the server work correctly only as a client. Testparm runs ok, but when i try to list the shares available on my server, this is the output: Added interface ip = 195.32.68.131 bcast = 195.32.68.191 nmask = 255.255.255.192 Session request failed (0,0) with myname = DNS2 destname = DNS2 Unspecified error 0x0 Your server

I'm trying to setup Samba for the first time. I have followed documentation, gotten password files setup, joined a domain, and now I'm trying to start the daemons. I start the nmbd fine, and can see it in Netowrk Neighborhood. However, when I try to start smbd with /usr/local/samba/bin/smbd -D, it fails immediately. The log.smb shows: [DATE] smbd/server.c:main(641) smbd version 2.0.7

Hi, I've just upgraded an old samba 3.0.23 on an old Fedora Core 5 to samba 3.5.4 using an rpm built from the source. Everything works fine, but when i start the server i get some error messages(see below). Before i start the server there is no connection (tested with lsof and fuser) on the 139 and 445 ports, smbd or nmbd aren't running. With the old version i never had this

As soon as I start up the daemons using the following commands, nmbd dies. /usr/local/samba/bin/smbd -D /usr/local/samba/bin/nmbd -D When I view the nmbd.log it gives the following. We're trying to set up Samba to work over 2 subnets. Smbd is ok and we can still mount our shares. Does anyone have any suggestions? Thanks for any help. [2002/10/22 10:37:55, 0]

Hi. I'm getting messages to the effect: Inetd: /usr/local/samba/lib/nmbd: Hangup Last messages repeat 319 times I start samba from inetd. Should I be starting it as a daemon or starting it in init.d? If starting it as a daemon in in init.d, does someone have a script that can let me use? I'm running samba on an a Sun E450, with Solaris 2.7. Thanks. grant

Samba was working well but I changed the host allow section of smb.conf and it stopped. I changed it back and restarted and got this error message in log.smbd [2003/08/17 12:15:26, 0] lib/util_sock.c:open_socket_in(789) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use I have a really simple smb.conf: # Samba config file created using SWAT # from localhost

I get this error in log.smb :-) bind failed on port 139 socket_addr=0 (Address already in use) Bye Charles -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/ms-tnef Size: 1880 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/19980122/dc045be7/attachment.bin