similar to: Problems starting smbd as a daemon

I just downloaded samba-1.9.18p3.tar.gz and compiled it on a DEC 3000/300 running OSF/1 v3.0 (uname -mrsv gives: "OSF1 V3.0 347 alpha") using the built-in cc compiler. The compiler gives the following warning: Compiling nmbd_incomingdgrams.c /usr/lib/cmplrs/cc/cfe: Warning: nmbd_incomingdgrams.c, line 452: Unknown character \ ignored ((DEBUGLEVEL>=(5))?(Debug1

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

>From time to time someone will comment in this list that their Samba server has disappeared from the list of hosts in Network Neighborhood. Browsing the list archive has yet to turn up any good explanation of this phenomenon. I think I have a clue. This morning my server disappeared again. When I checked the process list on the server I noticed that nmbd had been swapped out to disk. The

Hi, I was wondering how a linux box configured as a firewall stacked up against some of the commercial products like checkpoint-1 and gauntlet. Can someone direct me to a good book or online doc that compares linux to some other firewall methods? Mind you, I''m not talking about a firewall in the classical sense, ie ip forwarding turned off and used as a proxy, but the typical Linux box

Michel, One approach that hasn't been suggested is to block access to the netbios nameservice port on the samba host with a firewalling rule. That way the other computers on the subnet can't register themselves with nmbd. Suppose that your internal network is all within the 192.168.15.0/24 network. Each Windows workstation will automatically announce itself with a udp packet broadcast

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)

Hi, i have a annoying problem that drives me crazy. We have set up a Digital/Unix box with samba and the clients (W95) can mount the shares from this box. On the Unix side we create a textfile which will be periodically (or not) appended with new data. A Application on the W95 side reads this file. The Problem is, that the textfile has new lines, the Application don't see them !!! To

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)

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

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

Samba digest 1966, Jeremy Allison wrote: > For people who are looking for some objective > numbers to help recommend Samba to their employers (I > know there are some of you on this list :-) you might > want to look at the following couple of articles. > > The first one is in Smart Reseller (a USA trade press > magazine) at : > >

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

-----BEGIN PGP SIGNED MESSAGE----- Hi everyone - Someone I''m working with has a requirement to map ethernet card addresses to unique IP addresses, and then have a Linux IP masquerade server know of this mapping list and not allow any data to pass from any ethernet card that a) it doesn''t know about, or b) isn''t assigned the right IP. Ideally it would also log 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

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

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 =

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]