I'm running samba from inetd and it's working pretty well. Are you certain your inetd entries are correct? you can check the running processes and see if nmbd is running (smbd won't run until someone tries to connect to the linux box from win) via "ps -aux |grep nmbd" If that doesn't show nmbd running, then it's possible your daemons aren't starting correctly via inetd--double check your entries and restart inetd. If nmbd IS running, then it's probably something else. Is smbd complaining anywhere in your log files? BTW, when you say samba doesn't work, are you just trying to connect through what's visible in the network neighborhood, and your samba machine isn't showing up? Or have you been trying to connect by typing in an explicit path to your samba machine on a win machine (you know, the \\machinename\sharename thing)? If you can connect through that, there's probably a problem with nmbd (or it's not started). Also, are you using SWAT to administer/start/stop everything? It can make things a little easier and the help system with it is pretty nice. You should be able to start everything by hand either via SWAT or by starting smbd & nmbd. If you start them running by hand and still can't connect, you've probably got a configuration problem (if you think this is the case, you can send me the smb.conf and I'll take a peek at it). Good luck. J -----Original Message----- From: Urban Widmark [mailto:urban@svenskatest.se] Sent: Monday, July 31, 2000 5:06 AM To: Toby Russell Cc: linux-net@vger.rutgers.edu Subject: Re: Samba and nmbd On Mon, 31 Jul 2000, Toby Russell wrote: > next day my Samba network worked not, straight away after boot, and I had > changed not a thing. Pinging is cool, my workgroup is visible but You changed the not having spent X hours to get it to work part. Run testparm, that will try to tell you if the config error is in the smb.conf. Check the DIAGNOSIS.txt, check the online docs at www.samba.org (pick a mirror). Verify your entries in /etc/services and /etc/inetd.conf. The UNIX_INSTALL.txt describes this (It's in the samba sources, have no idea what Corel includes). If everything fails you can probably find more people that know samba on the samba@samba.org mailinglist (http://lists.samba.org/) than you can here. I have never run samba from inetd, always as standalone daemons. It may be easier to debug the problem if you do that (eliminates the posibility of inetd misconfig). /Urban - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu
