From owner-freebsd-questions Tue Feb 26 3:23: 9 2002 Delivered-To: freebsd-questions@freebsd.org Received: from corten2.billschoolcraft.com (adsl-63-193-247-201.dsl.snfc21.pacbell.net [63.193.247.201]) by hub.freebsd.org (Postfix) with ESMTP id 76E1237B402 for ; Tue, 26 Feb 2002 03:23:02 -0800 (PST) Received: from corten8.billschoolcraft.com ([192.168.7.8]) by corten2.billschoolcraft.com with esmtp (Exim 3.22 #1 (Debian)) id 16fCfq-0005GR-00 for ; Sun, 24 Feb 2002 20:23:38 -0800 Date: Sun, 24 Feb 2002 20:21:41 -0800 (PST) From: Bill Schoolcraft X-Sender: bill@corten8 To: questions@FreeBSD.ORG Subject: Re: Samba Question In-Reply-To: <1014594385.34439.101.camel@osiris.sigterm.com> Message-ID: System-ID: [en] (I; Linux i86pc) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 25 Feb 2002 it looks like Stuart Tanner composed: > On Mon, 2002-02-25 at 10:10, Jason Halbert wrote: > > Hi All: > > > > I have been trying to get Samba working with no luck. I installed it from > > ports. I edited the smb.conf.sample and changed the values to what I think > > match my network. I am trying to get my FreeBSD box on my simple > > peer-to-peer Win2k and WinXP network. I changed the "workgroup" and > > "server string" to my workgroup name and what I wanted the FreeBSD box to > > be called. I'm not able to connect to the other Windows boxes and they > > can't see the UNIX box. The UNIX box has two NICs in it; one public and > > one private. All the boxes are on the public network and nothing is on the > > private (it's there for future NAT). > > > > Does any one know of a good straight forward method for getting Samba > > working with a simple peer-to-peer network? > > Have you run /usr/local/bin/testparm? > Have you checked the samba logs: /var/log/log.smbd & > /var/log/log. (may not exist)? > > testparm will check your smb.conf file and report any errors. It only > checks that smbd will load the file and not that the settings will work > with your network. > The following steps may not make it to the cover of "Samba_Magazine" but they work each and every time I go to setup basic filesharing with Samba. I would like to suggest that you have compared what your explicitly setting in the smb.conf file "then" see what's left in the results of testparm. The stuff in the results of testparm are exactly what Samba's going to do also, and where Samba's going to look for directions in conjunction with stuff in smb.conf. READ EACH AND EVERY LINE OF THE OUTPUT OF "testparm" AND CHECK YOUR SYSTEM TO SEE IF EVERYTHING MATCHES. testparm | less You need to have the "same" workgroup name on your smb.conf file as your windows network for basic setup. You need to have the same username and passwords on the BSD box and the windows box. Did you see any errors when using "testparm?" like the missing "smbpasswd" file or when you ran: "smbpasswd -a username" "smbpasswd username" That's some of the basics in my own simple words. -- Bill Schoolcraft PO Box 210076 -o) San Francisco CA 94121 /\ "UNIX, A Way Of Life." _\_v http://forwardslashunix.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message