[KLUG Members] linux as print server

[Adam Williams]

>>ether specifically.  That will both solve the security issue (at least
>>in part) and make sure it is listening in the right place.
>There's two parameters, apparently. "Bind interfaces only" (can be yes or no) which I'm
>not using or "interfaces" which is set to the internal eth0 ("interfaces=eth0")

That should work.  What does "netstat -ap | grep smb" say?

>>>>Can you poll the Win9x boxes from the Linux box with "smbclient -L
>>>>{win9xname}"?
>>>Nope.  It adds an interface line about the ethernet card and says
>>>"connection to (win9xname) failed".
>What does "smbclient -L localhost" say?
>It adds the local interface and asks for a password.  That kept failing 
>(I kept trying the command) until I put in a password from a user on the 
>Linux box.  That worked.  It displayed a table of info that looked 
>correct (shares, server, workgroup) but "Master" had no value.

You have browse master = yes and local master = yes

>So, do users (and passwords) need to be set up on the Linux box for 
>the win9x machines?

In user mode yes,  in share mode no.  Although in user mode one can still 
make shares available to anonymoususers (public = yes),  Be sure to define 
a valid guest account.

>>Are your win9x boxes in DNS or /etc/hosts?  Or do you have a WINS server
>>floating about?  To circumnavigate name-space mire it is probably
>>easiest to enable WINS support on the Samba process and set the Win9x
>>boxes to use it as the WINS host if you don't already have one.
>Not using DNS, don't know what  /etc/hosts is.  

A flat file in both Windows and Linux used to realted names to IP 
addresses when no name service is available.

>No WINS server exhibiting levitation.  

Is the local shaman on vacation?

>The win9x machines are set to share peer-to-peer between themselves 
>w/Netbeui.  They also have tcp/ip bound on the same ethernet card as a 
>means of going on the internet.  All win9x machines can share files & 
>printers as well as surf the web.

Ah ha!  Welcome to the joys of CIFS,  which shares much in common with 
it's name-alike the venereal disease.  "Protocol Priority" is the term of 
the day.  Samba provides CIFS over UDP/IP as does Win2000 and XP (and late 
service pack NT boxes).  Your Win9x boxes are processing all sharing 
related information and namespace management over NetBeui.  As long as 
NetBeui is installed they won't see the Samba box and the Samba box won't 
see them.  Just as if you were installing a 2000/XP box you need to remove 
netbeui and tell them to use the Samba box as the WINS server.  File 
sharing will then work between the Win9x boxes via TCP/IP,  with no 
difference in operation, peer-to-peer and everything.  But with Win9x 
NetBeiu is the highest priority protocol, so if installed that one gets 
picked for doing everything.

Just set "wins support = yes" in your samba config and the win9x boxes 
will automatically register their names/ips.  And samba will create a 
browse list. 

>>On a Win box what does "nbtstat -a" show?  Or maybe nbtstat only exists
>>on >WinNT, I can't remember.
>No nbstat on win9x machines.

Right!  Because they don't have a real name service provider.

-- 
-----------------------------------------------------------
Ximian GNOME, Evolution, LTSP, and RedHat Linux + LVM & XFS
-----------------------------------------------------------