similar to: Help needed?

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

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

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

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]

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 =

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

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]

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

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

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?

Hello, i have installed samba on a linux 1.3.45 box and i have a problem. This is the output of the smbclient -L dns: Added interface ip=195.32.68.130 bcast=195.32.68.191 nmask=255.255.255.192 Server time is Mon Nov 10 09:25:37 1997 Timezone is UTC+1.0 Domain=[EOS] OS=[Unix] Server=[Samba 1.9.17p4] connected as guest security=share SMBtconX failed. ERRSRV - ERRbadpw (Bad password - name/password

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

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

HI, I am running Red Hat 7.2 on a PC. Until today I have been able to start smb. Now I am no longer able to start smb. When I start it with /etc/rc.d/init.d/smb start it say OK. However, when I execute /etc/rc.d/init.d/smb status it says that smbd is stopped, but nmbd is running. If I execute smbstatus it says "Failed to open byte range locking database, Can't initialize locking module -

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

OS = AIX 4.3.3 Samba 2.2.8a smb.conf: [global] workgroup = METRAN [test] comment = For testing only, please path = /usr/local/samba/tmp read only = no guest ok = yes smbd fails to start but did log a pid in smbd.pid. The process is not in the process table. I ran smbd -i to display the messages: smbd version 2.2.8a started. Copyright Andrew Tridgell and the Samba Team