similar to: smbd service won't start

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 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 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 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)

Hi, I installed Samba on Solaris to enable me print from the solaris workstation to a windows print server. When I start smbd and nmbd , smbd does not run but nmbd runs

Hello! I set debug level 10 to samba 2.2.0 and now see in log: [2001/05/10 08:31:48, 10] smbd/uid.c:gid_to_sid(409) gid_to_sid: winbind lookup for gid 5284 failed - trying local. How can I say to samba to not try use winbind? -- Wire connection and Windows reinstallation senior engineer Dmitry Melekhov http://www.belkam.com/~dm 2:5050/11.23@fidonet

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

Mrs, I´m a Brazilian and i don´t speak english very well, but i need try , ok . I need your help. Well, i want install the samba 2.0.7 in HP-UX 10.20. The install process is not completely ok, but install. This is the message in the install process : _______________________________________ /var/tmp/AAAa23547/catalog/samba/samba-ROOT/configure[101]: Syntax error at line 129 :

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

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()

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

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 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

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 there, samba drives me crasy :) following problem: 1 Sambaserver (V2.2.1) running on RedHat 7.0 -------------------------------------------- smb.conf: [global] workgroup = RIGL server string = Samba Server riglEDV load printers = yes printcap name = /etc/printcap printing = bsd ;guest account = pcguest log file = /usr/local/samba/var/log.%m max log size = 50

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?

Hi there, when I try to start the nmbd -D daemon on my OpenServer5.0.5 box, I'll get the errormessage in log.nmbd: [...] [2002/03/12 19:30:18, 0] nmbd/nmbd.c:(783) Netbios nameserver version 2.2.3a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2002/03/12 19:30:18, 0] lib/util_sock.c:(789) bind failed on port 137 socket_addr = 0.0.0.0. Error = Address already in use

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