similar to: smbd and nmbd

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

hey I am running Samba 2.2.8 on FreeBSD4.8, and all is working well, except: I have set up a virtual printer using Samba to take a print job, turn it into a pdf and then email it back to an address, using a perl script and the Samba print command. I have tested the script logging in as the Samba guest user and it works fine, but when i try to print to the printer it never works: the script is

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)

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: Blank Bkgrd.gif Type: image/gif Size: 145 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20020911/a89e1b74/BlankBkgrd.gif

I moved an entire RH 6.2 server from one CPU to a new one using a tape backup/restore. Everything from the old server is working on the new server, but when SysV starts up smb, the nmbd daemon (2.0.6) exits with an error: create_subnets: No local interfaces! eth0 has already started according to the logs and console. Any ideas? Thanks. ______________________ Greg Kelley, IT Director SSA, EAA,

I've noticed that my W2K clients connect to Samba much more quickly if I run it on port 445 instead of 139. However, my WNT clients then won't connect at all. I read somewhere that it was possible to forward the requests on port 139 to port 445. Anyone know how to do this or how to listen to both ports simultaneously? Thanks, Jason Joines Open Source = Open Mind

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?

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]

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

SAMBA newbie here........New 2.2.8 install on 5.1 AIX, nmbd will not start. Here is my error: [2004/06/29 14:05:29, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 0.0.0.0. Error = Address already in use Any ideas? Thanks !!! Larry S. Singleton lars@thornwood.com Systems Analyst E-Mail Administrator/Webmaster/"Guru in Training" Thornwood Furniture

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]

While the Samba server is running, does it ever refresh the contents of the smb.conf file, or do you have to restart the server for it to see changes to the smb.conf file? Thanks in advance. Jeff Rasnick Software Technologies, Inc. www.softtechks.com -------------- next part -------------- HTML attachment scrubbed and removed

Hi, Samba world: It is my first time to use samba to share a folder from a solaris 7 to our windows 2000 clients. After I have the following, I could not see the unix share point. Your help is highly appreciated! 1) Install samba 2.0.5. 2) done the following: Edit /etc/services and make the following changes. Immediately after the line which reads: sunrpc 111/tcp rpcbind

hi all, I noticed that when I upgraded from Samba 2.0.7 (redhat 7.0) to samba 2.2.1a I lost this nice little script that came with redhat to start and stop the samba server. I would type in /usr/sbin/samba start and get a response like... /usr/sbin/smbd start (OK) /usr/sbin/nmbd start (OK) I liked that...does any one have a substitute that I could use for 2.2.1a? Thanks Carl

I'm trying to connect to swat but can't. Just installed Samba 2.2.2-5 and edited /etc/services, even though I'm running Redhat 7.3 and use xinetd. /etc/xinetd/swat exists.... but I still cannot connect to http://localhost:901. Why??? Thanks for assist.

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

does anyone know how to hide a samba server in SMB terms? on an NT machine the command "net config server /hidden:yes" will make the machine vanish from the network neighbourhood but i cant figure out how to do this for a samba server many thanks sincerely, bob reven

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

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