Looks like IFHP is whooping its cookies on this, and is baffled by the files. Remove IFHP and see what happens...
> From [EMAIL PROTECTED] Fri Dec 7 16:03:16 2001 > Date: Fri, 07 Dec 2001 15:42:57 -0700 (MST) > From: David Bear <[EMAIL PROTECTED]> > Subject: LPRng: win2k print wierdness > To: [EMAIL PROTECTED] > > > This is the strangest error I have run across. > > We've been using lprng for 3 years? with NT4 clients, printing through > samba to linux servers running lprng. I dont use ifhp as I never needed > any kind of translation. The nt print drivers produced the postscript, > when lprng happily send to the hp and phaser printers via appsocket. > > Enter win2000. As soon as we loaded up win2k box with all our apps, and > attempt to print, we get continually postscript errors out the printers. > Sometimes its a timeout error, sometimes its a stack error, sometimes its > and undefined symbol. The point is, the error is NOT consistent for the > same machine same print job, same application. (using wordperfect, word, > and excel, and occasional pdf) We thought we had bad hardware. No, we > reproduced it on a second box. > > so, we attempt different printing methods from the win2k box: > > 1) print direct to hp8100 via lpt1. works > 2) print to file, the lpr the file to hp8100. BAD > 3) print to file, copy file to lpt1. works > 4) print to file, then netcat the file to hp8100. WORKS > > Now, I don't know what difference there is between netcating the > postscript file to the printer and lpr'ing the file as passthrough to the > printer. But, there's the rub. LPRng is doing something, and only to > postscript generated by win2k clients!!!! > > Let me emphasize that we have had our samba server and lpr spooler setup > for almost 3 years printing from NT 4 clients WITHOUT problem!! > > So, for the brave guru who would like to tell me what I've done wrong, I'm > attaching the relevant portion of the printcap file. Also, a graphic to > explain what I enumerated above. > > Can anyone tell me why win2k produced postscript would choke on my setup? > > > # /etc/printcap > .common: \ > :force_localhost@:sh:mx=0 \ > :filter=/usr/local/libexec/filters/ifhp > > .srvr: \ > :sd=/var/spool/lpd/%P \ > :lpd_bounce > > hp8100|PAC HP8100 DGM 1: \ > :tc=.common \ > :client \ > :[EMAIL PROTECTED] > > hp8100: \ > :server \ > :tc=.srvr \ > :rw:[EMAIL PROTECTED] > > pachp8100: \ > :server \ > :tc=.srvr \ > :rw:lp=pachp8100.pp.asu.edu%9100 \ > :oh=ppsrv3.pp.asu.edu > > -- > David Bear > College of Public Programs/ASU > 480-965-8257 > ...the way is like water, going where nobody wants it to go > > > ----------------------------------------------------------------------------- > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST > The address you post from MUST be your subscription address > > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests > or lprng-digest-requests) with the word 'help' in the body. For the impatient, > to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] > with: | example: > subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] > unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] > > If you have major problems, send email to [EMAIL PROTECTED] with the word > LPRNGLIST in the SUBJECT line. > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
