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!feed1.news.erols.com!news.maxwell.syr.edu!news.mathworks.com!newsfeed.internetmci.com!news.easystreet.com!not-for-mail From: tedm@agora.rdrop.com (Ted Mittelstaedt) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Question RE: Samba ? Date: 6 Mar 1997 04:25:20 GMT Organization: Cool Dudes Inc. Lines: 61 Message-ID: <5flgvg$dpo$1@easystreet03> References: <01bbef88$2a23ca80$664c1bcc@tony.gcr1.com> NNTP-Posting-Host: sunnet.portsoft.com X-Newsreader: WinVN 0.92.6+ Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36614 In article <01bbef88$2a23ca80$664c1bcc@tony.gcr1.com>, "Tony" <tony@gcr1.com> says: > >Anyone know enough about samba to tell me where to get some docs on it >and how to start the service up on my maching .. it is installed but not >running >and with the lack of docs I don't know what the startup name even is ?? > > Unfortunately, the installation program gives the idea that it is setting up samba, when it really isin't. There are a couple of things you need to do to enable all this: 1) You need to add the manual pages for installed software into your MANPATH environmental variable, so that the man program knows where to find the samba documentation. Add /usr/local/man into the search path defined by MANPATH. 2) You need to run the makewhatis program to add the user program manpages into the index. (so that a man -k samba command will actually reveal something) 3) Samba configuration is controlled by the smb.conf file. Unfortunately, the /stand/install program when it asks you if you want to add samba filesharing creates and modifies a smb.conf file in /usr/local/etc. The actual pre-compiled samba executables by default checks for a smb.conf file at /usr/local/samba/lib/smb.conf The easiest way to fix this post installation is to move the file into the appropriate directory. (or, recompile samba) 4) The locks directory needs to be created in /usr/local/samba 5) The netbios naming daemon needs to be run at startup in /etc/rc.local, for example my /etc/rc.local contains the line: /usr/local/samba/bin/nmbd -D -l/var/log/nmbd -G WORKGROUP 6) The samba startup executable needs to be added to /etc/inetd.conf, for example my line is: netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd -l/var/log/smblog 7) Last but not least, all your Winblows clients need to be running the Microsoft Networking client and using NetBIOS-over-TCP/IP , NOT NetBEUI. This has to be explicitly set, if you have either the IPX or NetBEUI protocol installed on your clients then Microsoft Networking will use those protocols before using NBT. This is actually a more serious matter than it seems, because if your running a Windows NT domain, and the domain controller does not have TCP/IP installed, and only uses either IPX or NetBEUI, then it forces all the clients to use those protocols. Currently, only OS/2, Windows NT, WIndows 95, WFW3.11+MS-TCP and Unix can access unix machines via Samba. Also, one last thing is that many of the clients, such as WFW, upcase the passwords when they send them to the netbios server. NT doesen't care about case sensitivity, but Unix does. So, you will need to put the line "password level = 1" in the [global] section of smb.conf or those clients won't connect. Ted