similar to: Help need unable to start smbd deamon

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)

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)

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

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

Hi. We have had SAMBA running successfully at work here for a while, it's on a Sun Sparc Solaris 2.6. The version of samba is 2.0.0. Unfortunately our sysadmin has left the company, and I have to try and fix a problem with Samba. When I try and start samba, "nmbd" starts ok, but "smbd" doesn't start. When I check the log files, I get these errors: [2001/09/24

Hi Folks, I am looking to try and find a solution to the following problem and hope someone can help. I have just installed Samba on an HP Proliant Microserver at home to share disk with my Windows 7 PC and Vista laptop. I have managed to get everything set up but I have an issue where on a reboot the Windows 7 PC looses the share. If I restart samba (using /etc/ini.d/samba restart) then

Help please. I am in the process of configuring Samba 3.0.14a onto 4 AIX 5.3 systems. It seems to be working OK on 3 of the 4, but on the last one, I cannot start smbd. nmbd seems to start fine. The smb.conf file matches the other servers except that the server name is changed. Here's the error showing up on the log.smbd file. [2007/05/02 15:19:47, 0] smbd/server.c:main(835) standard

I have a Solaris box and Windows 2K box connecte through a hub, along with a DSL modem. I cannot get the two boxes to work via Samba, here is the relevant details. The status report from SWAT # Samba config file created using SWAT # from localhost (127.0.0.1) # Date: 2001/03/02 12:54:01 # Global parameters [global] netbios name = MARISOL server string =

Hi folks, I'm trying to help a fellow sysadmin configure Samba on his DG/UX server. He's installed 2.0.5a, and everything seemed to go well in the configure and make stages. However, when he tries to start 'smbd' by hand he gets the errors below. Our machine is binary compatible with his, and I sent him my copy of smbd (from version 2.0.3), but it made no difference. I had

HI, I am running Red Hat 7.2 on a PC. Until today I have been able to start smb. Now I am no longer able to start smb. When I start it with /etc/rc.d/init.d/smb start it say OK. However, when I execute /etc/rc.d/init.d/smb status it says that smbd is stopped, but nmbd is running. If I execute smbstatus it says "Failed to open byte range locking database, Can't initialize locking module -

On Fri, 16 Dec 2016 13:46:24 +0100 Artur Moor via samba <samba at lists.samba.org> wrote: > If I remove 'nmbd bind explicit broadcast = no' in 'smb4.conf', then > nmbd wan't start and I get following in the log: > > [2016/12/16 12:37:35.075428, 0] > ../source3/lib/util_sock.c:396(open_socket_in) > bind failed on port 137 socket_addr = 10.0.140.255.

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

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

I get the following log when trying to run nmbd -D Netbios nameserver version 2.2.3a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/05/20 15:02:44, 0] lib/util_sock.c:open_socket_in(789) bind failed on port 137 socket_addr = 10.10.50.4. Error = Cannot assign requested address [2003/05/20 15:02:44, 0] nmbd/nmbd_subnetdb.c:make_subnet(140) nmbd_subnetdb:make_subnet()

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]

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:

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

Hi, debian etch + samba 3.0.24-6 on 2.6.18-4-amd64. Today I got a panic email from samba. [2007/08/14 08:46:55, 0] smbd/nttrans.c:call_nt_transact_ioctl(2338) call_nt_transact_ioctl(0x9005c): Currently not implemented. [2007/08/14 09:25:05, 1] smbd/service.c:make_connection_snum(950) c601356 (...) connect to service FD_Systeme initially as user theckne (uid=5053, gid=1068) (pid 16275)

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]

Hello I'm a biginner on samba and mailinglists. But I desperate need same help. After updating my samba 2.2.1a to 2.2.2 I can't logon to the domain again. The log.nmdb gives out this information: [2001/11/02 01:22:28, 0] nmbd/asyncdns.c:start_async_dns(150) started asyncdns process 184 [2001/11/02 01:22:28, 0] lib/util_sock.c:open_socket_in(820) bind failed on port 137