[CLUE-Cert] Samba and slaved printer

Sun Jul 15 10:44:57 MDT 2001

Maybe you are subscribed with digest mode to this list...in any case, I sent
another msg this morning saying to nix that last complaint of mine. I'm cc'ing
this direct to you in case you are. 

To answer some of your questions, though: yes, dmesg shows the detection you speak of.
I understand winprinter to mean just what you describe...it makes producing
them cheaper than if the logic was built into printer/modem. I didn't
know that the software was created by MS, however. Re: kudzu, I see it
when it boots up, but I let it time out, as I'm not really sure how it works.
When was kudzu added as part of default startup? 

I have not run 7.1 before
this (box in question is 7.1, BTW). Is it me, or did some of the other changes
in RH 7.1 seem rather arbitrary, esp. in the /etc dir? Is xinetd something
that is RH-specific, or other distros adding this too? Also, the 
"service fooservicename start|stop|restart" mechanism, has that always been 
there, or did I just stumble onto it for the first time? And is it RH-specific, 
or do other distros (or is it distroxen? districes?) use this mechanism, too? 
There doesn't seem to be a man page on "service". Or an info entry.

BTW, I saw some posting(s) mentioning that HP released some drivers for
some of their winprinters. I'm not sure how old the posting(s) was/were. 
Just an FYI.

To raise another spectre: are you printing from any Linux box(s) to the 
Samba share? I mean besides the box that slaves the printer? And how hard
was that? I'm thinking of maybe printing from a RH 6.x box to the other 
RH7.1 box (which has the printer shared)...I might just charge ahead and see how
I make out, but I thought I'd ask ahead in case I run into trouble...

Cheers, and once again, thanks for all the help on this rather off-topic
issue. But anything that is samba- or printer-related on the test should be
a breeze, now, huh? Well, depending on what they ask. :)

On Sun, 15 Jul 2001 10:05:24 -0600
"Darrell L. Ford" <darrellford at uswest.net> wrote:

> Hello Sean,
> 
> I did experience this exact problem before I had installed RH 7.0 (now
> running 7.1) ... I beleive the problem lies with the HP722C printer and the
> lpd dameon...  The HP722C printer is a "winprinter" in line with the same
> logic as a "win modem".  What this means (the way I understand it) is that a
> "winprinter" does not contain the necessary chipsets to handle print jobs,
> and instead relies on software (developed by MS) to communicate with the
> processor to handle the functionality that these missing chipsets normally
> handle in "non winprinters".  (exactly like winmodems).  In anycase, prior
> to the lpd dameon that comes with RH 7.0 and later, support for alot of win
> printers has been incorporated.
> 
> Clarification, although I refer to the lpd dameon as providing the
> functionallity for win printers, this may not be true... It may be handled
> by the new printer drivers incorporated in the RH7.1 distribution.  The
> reason I say the lpd adds this functionallity is this.... When my RH 7.1
> machine boots, immediately after the lpd dameon fires up (it may also be the
> driver and lpd that provides the functionality) , I get the following
> report:
> 
> Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
> Winbond chip at EFER=0x3f0 key=0x87 devid=97 devrev=73 oldid=ff
> Winbond chip type 83977TF / SMSC 97w33x/97w34x
> Winbond LPT Config: cr_30=01 60,61=0378 70=07 74=03, f0=03
> Winbond LPT Config: active=yes, io=0x0378 irq=7, dma=3
> Winbond LPT Config: irqtype=pulsed low, high-Z, ECP fifo threshold=0
> Winbond LPT Config: Port mode=ECP and EPP-1.9
> SMSC Super-IO detection, now testing Ports 2F0, 370 ...
> 0x378: FIFO is 16 bytes
> 0x378: writeIntrThreshold is 16
> 0x378: readIntrThreshold is 16
> 0x378: PWord is 8 bits
> 0x378: Interrupts are ISA-Pulses
> 0x378: ECP port cfgA=0x10 cfgB=0x48
> 0x378: ECP settings irq=7 dma=<none or set by other means>
> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,EPP,ECP]
> parport0: irq 7 detected
> parport0: cpp_daisy: aa5500ff(98)
> parport0: assign_addrs: aa5500ff(98)
> parport0: No more nibble data (0 bytes)
> parport0: faking semi-colon
> parport0: Printer, HEWLETT-PACKARD DESKJET 720C
> lp0: using parport0 (polling).
> 
> If this report does not come up, then your RH Linux box is not recognizing
> your HP722C.  When you try to print, you will get exactly what you have
> reported down below (a hung print job).....
> 
> My parallel port is set to ECP+EPP mode in the computer bios.  I use the
> standard lpt0: 0x378 irq 7 (standard first parallel port) for my HP722C.
> 
> Check dmesg to see if you have the above lines.  Check your parallel port
> mode in bios and set it as above, reboot.... We'll get this worked out for
> ya...
> 
> Darrell
> 
> BTW are you running kudzu at boot to find  new hardware?
> *** I will post Samba problems in another post...
> 
> ----- Original Message -----
> From: Sean LeBlanc <seanleblanc at home.com>
> To: <clue-cert at clue.denver.co.us>
> Sent: Saturday, July 14, 2001 4:54 PM
> Subject: Re: [CLUE-Cert] Samba and slaved printer
> 
> 
> > 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 file://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
> >
> > _______________________________________________
> > CLUE-Cert mailing list
> > CLUE-Cert at clue.denver.co.us
> > http://clue.denver.co.us/mailman/listinfo/clue-cert
> >
> 
> _______________________________________________
> 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