Displaying 20 results from an estimated 2000 matches similar to: "cannot start smbd on AIX 5.3"
2007 Apr 27
5
Option valid user not expanded for groups
Hi,
I have a AIX 5.3 machine with Samba 3.0.24c joined into one Windows 2003 ADS server OK.
I can request basic information, user lookup, domain lookup(wbinfo, id, net groupmap).
When I want to acces the share \\node05\brom from one Windows station I receive a popup window password.
In the log of the samba for that machine I found:
[2007/04/27 10:48:27, 2] auth/auth.c:check_ntlm_password(319)
2004 May 04
3
Smbd not running
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
2003 Aug 17
2
smbd won't run - Error message says port 139 in use
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
2001 Jan 18
5
New Samba Install - Error Bind Failed
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)
2003 Mar 18
5
still can't print to samba printer from winxp
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)
2001 Sep 23
1
smbd won't start!! Please help!!
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
2000 Feb 28
4
Multiple smbd processes generated
We have an occasional problem which manifests with multiple processes
being created for a particular user. For example, for a user "xy004":
xy004 8463 0.0 0.0 6.02M 0K ?? IW 11:48:59 0:02.02 smbd
xy004 9426 0.0 0.0 5.99M 0K ?? IW 11:52:18 0:03.68 smbd
xy004 10433 0.0 0.0 5.81M 0K ?? IW 12:17:20 0:00.85 smbd
xy004
2010 Sep 07
1
bind failed on port 445 socket_addr = 0.0.0.0.
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
1999 Oct 13
2
bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
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
2010 Aug 20
1
smbd version 3.5.4-62.fc13 can NOT bind to IPv4 endpoint( 0.0.0.0:445 ), but it bind to IPv6 endpoint ( :::445 )
# smbd -Fi -d 2
smbd version 3.5.4-62.fc13 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
uid=0 gid=0 euid=0 egid=0
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Processing section "[homes]"
Processing section
2010 Apr 26
3
openbsd-compat regression tests
The snprintftest.c regression test in openbsd-compat/regress has a
buffer overflow error, and an argument error in the calls to snprintf(),
and vsnprintf().
On line 49 of snprintftest.c, the character buffer, b, is allocated at
5 bytes. However, in the calls to snprintf and vsnprintf, on lines 68
and 77 respectively, it is expected to place 11 bytes of data into the
buffer. Which will result
2002 Feb 17
2
samba -i prints some strange stuff
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:
2002 Mar 13
2
smbd service won't start
I have been looking at samba for about 3 days and on Unix to provide shares
for our NT system.
My problem is that I can't seem to start the smbd process. There are some
started but by the guest user and I'm sure I need one started by the root
user.
If I simply type the command it returns no errors to the screen, but there
are errors in the log.smb file. The error is: -
standard
1998 Apr 03
3
smbd not loading
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
2002 Oct 22
1
nmbd dies as soon as it's started
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]
2009 Jul 13
7
Samba on RHEL issue
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:
2003 Jul 28
1
(no subject)
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]
1997 Nov 05
2
Problems starting smbd as a daemon
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
2005 Aug 16
0
FW: Error:The semaphore timeout period has expired
UPDATE:
We found out that there was still an entry in /etc/rc.local to start up
the old SAMBA after upgrading and setting up to run from inetd.conf.
Once the /etc/rc.local entry was removed, we no longer receive the
"semaphore timeout period has expired" messages and we are able to
connect to the shares.
Ben Burruel
Sr. Systems Manager
Metrics & Mainframe Capacity Planning
San
2001 Nov 01
2
Stupid beginner
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