similar to: Smbd not running

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:

Hi, I am trying to install samba on the RHEL. The installation completes but after that I get the smbd dead message upon checking the status: [root@usps-dc1-pc12 share]# [root@usps-dc1-pc12 share]# service smb status smbd dead but pid file exists nmbd (pid 8078) is running... [root@usps-dc1-pc12 share]# The version of RHEL and samba are as follows:

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

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

Well I tried #freebsdhelp and got confirmation that this is just not happening to me but we couldn't figure it out there either... with: FreeBSD 4.5 Samba 2.2.2 | 100Base T Crossover link | Window XP Pro Upload win to unix speeds are around ~400k/sec Download unix to win speeds are around ~5000k/sec checked for net collisons (there are none) anyone find a fix for this?

I need help. For over a year I have been running SAMBA 2.05a under RedHat 6.1 (kernel 2.2.x) without problem. Then a couple days ago a power glitch crashed my system (UPS not powerful enough any more). Now SAMBA is not running. Here are the symptoms: As RedHat is starting up, both smbd and nmbd are listed as successful. /var/log/messages indicates: Dec 30 13:19:45 we-24-126-201-41 smb: smbd

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. Today I upgraded samba from 3.0.34 to 3.4.4 without changing anything in smb.conf but with changing local and domain sid: old samba 1) net getdomainsid and getlocalsid new samba 2) net setdomainsid and setlocalsid to ones (both the same) from 1) after restarting samba I can't log into domain: XP says : domain controller unavailable ... I tried to rejoin domain - and I can ;) however

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

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

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

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

On Fri, 16 Dec 2016 12:36:33 +0100 Artur Moor via samba <samba at lists.samba.org> wrote: > If I remove 'nmbd bind explicit broadcast = no' then 'smbd' can't > start because samba is running i jailed einvironment. You should still be able to start 'smbd', are any Samba deamons running when you try the join? Which Samba daemons are you starting ? >

Hello! I have cross-compiled Samba 2.2.3a for my Dreambox(PPC DVB receiver with Linux). smbd runs without any problems but when I start nmbd I get the following error message: -------------------------------------------- standard input is not a socket, assuming -D option open_socket_in(): setsockopt: SO_REUSEADDR = True on port 137 failed with error = Protocol not available Failed to set socket

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

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