[CLUE-Cert] Samba and slaved printer

[Sean LeBlanc]

Well, I'm close enough to figuring this out that I can almost touch it,
thanks to the help you guys have given. I also had some struggles I can attribute
to the new differences that RH7.1 has - apparently there is a new thing called xinetd
(like inetd), and my "workstation" install did not put it (or inetd) there, and 
that was causing no end of fun to get telnet on that box. Also sshd service I had not put on there
during install.
Ah well, it was a freshly installed box with nothing really important on it
anyway, so I had the luxury of being
able to wipe that install, and start over, this time selecting the "Everything"
check box.

I can send a "test print" from Windows printer setup, and it comes out
fine. I can send a simple text of my own, from say, Notepad. However,
let's say I go to userfriendly.org, and try to print off a cartoon.
It prints, or it starts to. It then dies - HP720C sits, there, blinking.
lpq shows the job as stalled. I lprm the job, and then hit the power
button on the printer. The paper kicks out, and it looks as if the top
edge of cartoon panels were starting to print correctly. It just didn't
finish. If I try to print a Word document, let's say my resume, it seems
to be nearly the same deal. It gets about half way through first page,
and stops. Text looks fine, and exactly where I would expect it, but
again the job just doesn't finish. Now, if I print the same cartoon
from the Linux box that has the share on it, it prints out. I don't
have StarOffice on the Linux box in question, so I can't try out the
resume. 

But I think it's safe to assume that  printing from Windows to that share
that seems to be what is munging things up. Problem
is, I'm not sure if it's Samba or the driver config at Windoze end. Anyone
else ever run into anything similar?

On Thu, 12 Jul 2001 15:39:17 -0600
Lynn Danielson <lynn.danielson at clue.denver.co.us> wrote:

> Sean LeBlanc wrote:
> > 
> > I was still unable to see the machine on the network. I have another
> > samba box that has (disk)shares out there, and I think it's using
> > non-encrypted passwords, so I need to keep with that. I'll try to
> > take a look at it tonight or this weekend.
> 
> I brought some Samba (and Kermit) materials to the meeting last 
> night.  If you want I can bring them again next time (July 25th).  
> 
> If you can't see your Samba server on the net, I'd question what 
> your "lm announce" settings are, whether your global browseable 
> parameter is set to yes and if your global "guest ok" parameter 
> is set to yes.
> 
> Use smbclient, testparm and your samba logs for troubleshooting.
> 'smbclient -L hostname' should give you a browse list if one is 
> available.  'smbclient //hostname/sharename -U username' should
> connect you to any available smb share.  The smb logs (there may
> be only one depending upon your configuration parameters) are
> your best resource for troubleshooting connection problems.  The
> testparm command will parse your smb.conf file and, if there are
> no problems with it, list out all of your configuration parameters.
> 
> SWAT can be particularly helpful when you're getting started with
> Samba.  You must configure it into your services and inetd.conf
> files.  After which it makes it very easy to set up basic Samba
> shares through a CGI.
> 
> If you're using encrypted passwords, which is recommend and the
> default for some time now, you must either: A) set up an smbpasswd
> file with an entry for every user who will connect to your samba 
> server, or B) use another server for password authentication.  If
> you're participating in a domain, option B can be a lot simpler 
> than building and maintaining your own Samba passwd file.  Simply
> add "password server = BDCname PDCname" to your smb.conf file.
> 
> Hope this helps,
> 
> Lynn
> _______________________________________________
> CLUE-Cert mailing list
> CLUE-Cert at clue.denver.co.us
> http://clue.denver.co.us/mailman/listinfo/clue-cert


-- 
============================================================
Sean LeBlanc - seanleblanc at bigfoot.com