Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.eng.convex.com!newshost.convex.com!newsgate.duke.edu!news.mathworks.com!newsfeed.internetmci.com!in3.uu.net!news.winc.com!usenet From: "Matthew A. Gessner" <mgessner@aristar.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: SAMBA Date: Mon, 05 Aug 1996 09:16:56 -0400 Organization: Aristar, Inc. Lines: 30 Message-ID: <3205F448.446B9B3D@aristar.com> NNTP-Posting-Host: slip125.winc.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0b5aGold (X11; I; FreeBSD 2.1.0-RELEASE i386) I posted a message here a while back about running SAMBA and I did get some replies. However, further attempts to contact these folks have failed, and I' really like to get it up and running. I'm looking for general information about setting it up for a specific case: I have a bunch of Windows 95 machines which are on my network that use SLIP to dial in to our ISP and I need local access via the Ethernet to these machines and printers. I've had a little success with this: nmbd starts up when machines on the network go out and try to find names on the network. And so the Windows 95 explorer does show that the system is out there, but when I try to connect to it via Explorer it tells me it can't find the machine. What I need to know is how do I set up the Windows 95 machines to work with Samba? What protocols do I need and do I need to enable WINS? If needed, I can post or e-mail my configuration files and other info about my Windows machine(s). Thanks in advance, guys, -- Matthew Gessner <mgessner@aristar.com> Computer Scientist Aristar, Inc. 302 N. Cleveland-Massillon Rd. Akron, OH 44333 (330) 668-2267 (330) 668-2961 FAX