similar to: Bind failed on Port xxx Socket error

Displaying 20 results from an estimated 10000 matches similar to: "Bind failed on Port xxx Socket error"

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 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
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)
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?
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)
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
2019 Oct 21
1
ERROR: Failed to open nmb broadcast socket
Freebsd 12.0-RELEASE-p10 samba 4.8.12 Recently, my machine has started going into an endless loop with the following message rolling off the screen continuously: nmbd_subnetdb:make_subnet() Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address
1999 May 19
1
bind failed
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
2000 May 04
1
smdb bind error
Hello List, I am working with COL 2.3 and samba-2.0.5. When I /etc/rc.d/init.d samba start I get an error message in the smbd log file that says "bind failed on port 139 socket_addr=0.0.0.0 (Address already in use). What is causing this? What do I need to do to fix it. Charles Olds (Chaz)
2000 Jun 14
1
port 139 problems
I'm trying to setup Samba for the first time. I have followed documentation, gotten password files setup, joined a domain, and now I'm trying to start the daemons. I start the nmbd fine, and can see it in Netowrk Neighborhood. However, when I try to start smbd with /usr/local/samba/bin/smbd -D, it fails immediately. The log.smb shows: [DATE] smbd/server.c:main(641) smbd version 2.0.7
2001 Mar 05
1
Socket addr error in the smbd start - HPUX
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 :
1999 Feb 01
5
Bind Failed on Port 139
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
2008 Jun 02
2
Need advise in grab the line number of sorted list in R
Hi, I have a data frame which format is like below:- X Y Z 131 22.2 3.4 4.4 150 20.0 12.2 4.5 etc... And I have sorted the data frame. However, I would like to grab one of these elements in the data frame. Also, i would like to number these rows so that when i grab a particular line let say 150, it is able to return me the position of the row rather than the "150".
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:
1998 Oct 02
0
bind failed on port 139 error in log.smb???
I just install samba.1.9.18p10 version on my Solaris 2.6. Our network setup: the SAMBA server is on the same network with my NT Server PDC and NT workstation within PDC domain. I also have another subnet that have WinNT and Win95. We also use NIS domain server for our UNIX home user account. smb.conf: workgroup = NTPDC_NAME server string = SMBSERVER_NAME host allow = .... load
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
1999 Mar 22
4
Bind failed on port 137
Has anyone had this one? My log.nmb file gives: 1999/03/22 11:29:48 netbios nameserver version 1.9.18p10 started Copyright Andrew Tridgell 1994-1997 1999/03/22 11:29:49 becoming a daemon Added interface ip=10.1.7.1 bcast=10.1.255.255 nmask=255.255.0.0 bind failed on port 137 socket_addr=10.1.7.1 (Address already in use) make_subnet: Failed to open nmb socket on interface 10.1.7.1 for port 137.
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
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]
2006 Nov 10
2
SAMBA don't start
Hello, I can't connect to my SAMBA server. Testparm not report 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 =