[KLUG Members] linux as print server

[Adam Williams]

>>Is the workgroup set the same?
>Yup.  I used grc.com to test it and it finds port 139 and the appropriate workgroup
>name via the internet.  I figure I'll close that down somehow once I figure out how
>to get it working on the internal network (I'm using two different ethernet cards for
>external [internet] and internal [local] networking).

Use the bind interfaces parameter to set it to listen on the internal
ether specifically.  That will both solve the security issue (at least
in part) and make sure it is listening in the right place.

>>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?

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.

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

>>What is the security mode on your Samba box?
>Tried User for a bit, now it's set to Share.

Ok.  If the box is also a firewall and only doing print serving this
makes the most sense.

>>>Seems like it should be simple, but haven't seen it yet.
>>Optimism?  Wow, I haven't seen that in awhile.  I'll delist it from the
>>"things endangered" class. :)
>Optimism is the only way to keep working when it doesn't work.  There's 
>always a reason, it's just a matter of figuring it out. ;-)

Sorry, I spend too much time with users who hold "figuring it out" as an
unattainable goal, genetically beyond their capacity.   And I'm talking
about word processors.......