Displaying 20 results from an estimated 93 matches for "socket_addr".
2001 Jan 18
5
New Samba Install - Error Bind Failed
...m 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)
[2001/01/17 12:50:46, 0] lib/util_sock.c:open_socket_in(863)
bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
[2001/01/17 12:54:43, 0] lib/util_sock.c:open_socket_in(863)
bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
[2...
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) couldn't find service c
[2003/03/17 16:20:46, 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...
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 only
network service that I have added and since removed is...
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
2010 Sep 07
1
bind failed on port 445 socket_addr = 0.0.0.0.
...#39;t running.
With the old version i never had this message.
I suppose it means nmbd ans smbd won't connect to the "all addresses"
interface (0.0.0.0).
What can i check to fix this ?
[2010/09/07 00:44:57.390890, 2] lib/util_sock.c:875(open_socket_in)
bind failed on port 445 socket_addr = 0.0.0.0.
Error = Address already in use
[2010/09/07 00:44:57.391590, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use.
[2010/09/07 00:44:57.391754, 2] lib/util_sock.c:875(open_socket_in)
bind failed on port 139 socket_addr = 0.0.0...
2002 Dec 30
4
error message in smbd.log file: bind failed on port 139 socket_addr = 0.0.0.0.
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?
2005 Mar 24
0
Need Help for Samba on Solaris bind failed on port 139 socket_addr = 0.0.0.0.
Not sure what port is using,
Need help on the same urgently.
Thanks,
Manish Jain
______________________________
2005 Mar 24
1
Samba Starting Problem on Solaris Error : bind failed on port 139 socket_addr = 0.0.0.0.
Need help in resolving above mentione error message, unable to start smbd on Solaris.
Thanks,
2002 Feb 17
2
samba -i prints some strange stuff
...of smbd running when I do a ps -aux. When I type nmbd -D it
starts and I can see it with ps -aux. What happened to smbd -D? After
a "man smbd" I saw the -i switch. Here is what I get when I type
smbd -i:
Copyright Andrew Tridgell and the Samba Team 1992-2002
bind failed on port 139 socket_addr = 0.0.0.0.
Error = Address already in use
What does this mean? Is this because I forced the rpm over the top of
an already installed samba? I tried to install the rpm using the -U
switch but it wouldn't install either so I forced it with --force.
If I do a "cat /var/log/samba/smbd.log&qu...
2002 Mar 13
2
smbd service won't start
...ere 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 input is not a socket, assuming -D option
bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
Can anyone suggest anything??
Any help will be much appreciated.
Cheers
Carl
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 b...
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]
nmbd/nmbd_responserecordsdb.c:find_response_record(235)
find_response_record: response packet id 893 received with no matching
record.
When I try to browse to my BSD box i get a access denied error from W...
2006 Nov 10
2
SAMBA don't start
...eport error.
I test the IP settings,
I can Ping the server from any PC,
I can Ping the PC from the SAMBA server,
I can Ping Localhost or servername on the SAMBA server,
But when I do a 'ps -ef' only the smbd is started.
The 'log.nmb' report that :
'bind failed on port 137 socket_addr = 0.0.0.0.
Error = Adress already used.'
I work on a SAMBA 3.0.20a server on a SCO OpenServer 5.07 box with
maintenance pack 5.
Why the nmbd daemon don't start ?
I verify my configuration, but I don't find anything.
What can I do to fix the problem ?
Many thanks for your help....
1997 Nov 05
2
Problems starting smbd as a daemon
...NS2 destname = DNS2
Unspecified error 0x0
Your server software is being unfriendly
I try to start smbd and nmbd as a daemon, but only the nmbd runs. This is
the error message in the log file:
Added interface ip = 195.32.68.131 bcast = 195.32.68.191 nmask =
255.255.255.192 bind failed on port 139 socket_addr = 0 (Address already in
use)
I looked at my /etc/services what is defined at port 139 and i think
everything is correct.
No problems for me whith my network in all other cases.
What i'm doing wrong?
Can anyone help me?
Thanks. Laura
2002 Oct 22
1
nmbd dies as soon as it's started
...en 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] lib/util_sock.c:open_socket_in(830)
bind failed on port 137 socket_addr = xxx.xx.x.xxx(gateway)
Error = Can't assign requested address
[2002/10/22 10:37:55, 0] nmbd/nmbd_subnetdb.c:make_subnet(142)
nmbd_subnetdb:make_subnet()
Failed to open nmb socket on interface xxx.xx.x.xxx(gateway) for port
137. Error was can't assign requested address
[2002/10/22 1...
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 (127.0.0.1)
# Date: 2003/08/17 11:50:06
# Global parameters
[global]
workgroup = JMPURSER.NET
interfaces = eth0 192.168.1.40/24
encrypt passwords = Yes
os leve...
2001 Nov 01
2
Stupid beginner
...r 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 socket_addr=194.95.7.229 (Cannot assign
requested address)
[2001/11/02 01:22:28, 0] nmbd/nmbd_subnetdb.c:make_subnet(142)
nmbd_subnetdb:make_subnet()
Failed to open nmb socket on interface 194.95.7.229 for port 137.
Error was Cannot assign requested address
[2001/11/02 01:22:28, 0] nmbd/nmbd.c:main(835)...
2000 Feb 28
7
smbd and nmbd
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
2019 Oct 21
1
ERROR: Failed to open nmb broadcast socket
...Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address
[2019/10/21 05:46:50.980728, 0] ../source3/lib/util_sock.c:396(open_socket_in)
bind failed on port 137 socket_addr = 0.255.255.255.
Error = Can't assign requested address
[2019/10/21 05:46:50.980841, 0] ../source3/nmbd/nmbd_subnetdb.c:127(make_subnet)
I am unable to regain control of the PC and am forced to do a manual
shutdown and reboot...