wow,
you definetely earned your t-shirt...
take care
~christoph
On Wed, 9 Jan 2002, David L. R. Houston wrote:
> Well, I managed to figure it all out.
>
> The problem: version 3.8.4 of LPRng.
>
> After running tcpdump and tcptrace, and getting absolutely zilch, I
> decided to install an older version, 3.8.1. Presto: all tests work fine,
> OSX and OS9 clients can do a direct print using LPR! I had scarecely to
> breath and it worked.
>
> Moral: Never think that the latest release is the best!
>
> Many thanks to all who responded with positive affirmations. Special
> thanks to Alan Sundell who suggested trying 3.8.1.
>
> And, a sincere wish that whatever the problem is in 3.8.4, that it be
> fixed and that others not hit the same wall!
>
> David Houston
> CIT Client Services Coordinator
> University of Vermont
>
>
> On Tue, 8 Jan 2002, David L. R. Houston wrote:
>
> > I got a considerable number of replies to this posting. Alas, nothing,
> > but nothing, has helped.
> >
> > Short and sweet question: has anyone gotten LPRng to function for a
> > Macintosh client (running OS9 or OSX) that sets up its printers with the
> > Desktop Printer Utility, LPR Printing using IP? (i.e. NOT using Appletalk)
> >
> > Here is what I know:
> >
> > - Netatalk is now installed on the same test machine.
> >
> > - However, a simple test on the other (primary) server reveals that in
> > fact netatalk is *not* required to get LPR printing using IP to work.
> > Netatalk *would* be needed _if_ printer selection and processing happened
> > over _Appletalk_. Since one of my chief goals is to do away with this
> > hideous protocol, I need to be sure I can print without it.
> >
> > - Setting up a printer on either an OSX or OS9 Mac client involves use of
> > the Desktop Printer Utility, LPR type printing, and then entry of the
> > hostname, and then the named print queue. No combination of hostname
> > (which for testing is gecko.uvm.edu) or named printers found in the
> > /usr/local/etc/printcap gives any output.
> >
> > - All tests yield the identical result: (from /usr/local/bin/lpq -Pall)
> > Printer: lp@gecko (holdall)
> > Queue: no printable jobs in queue
> > Status: lp: Check_for_missing files: missing data file
> > 'dfA569ip103038.uvm.edu' at 11:16:27.567
> > Printer: laserq@gecko
> > Queue: no printable jobs in queue
> > Server: no server active
> > Status: job 'cfA674gecko' saved at 11:12:29.321
> > Rank Owner/ID Class Job Files Size Time
> > done root A 674 /usr/local/src_lprng 63363 11:12:26
> >
> > The problem seems to be very consistent: the *data* portion of the file
> > never gets there. I have tried printcap with and without send_data_first
> > and send_block_format - no change at all.
> >
> > Printcap entries:
> > .common:
> > :sd=/var/spool/lpd/%P
> > :sh:mx=0:mc=0
> >
> > # Jetdirect Box number 1
> > lp:tc=.common:lp=saturnp1.uvm.edu%9100\
> > :send_data_first:
> >
> > # Jetdirect box number 2 (different model)
> > laserq:tc=.common:lp=132.198.103.204%9100
> > :send_data_first
> > :send_block_format
> >
> > It is seemingly impossible to determine if the control file or header
> > file ever makes it to the system. Setting a debug level to network does
> > seem to confirm that the connection itself is being made just fine.
> >
> > The conclusion I am rapidly approaching is that LPRng and/or the Mac OS
> > (9.2.2 or X) are not capable of working together without Appletalk, that
> > either LPRng requires pure Appletalk printing (in which case CAP or
> > Netatalk is mandated) or simply cannot handle the print request the way it
> > is set up at the client end when using LPR printing using IP on the
> > workstation.
> >
> > If *anyone* has managed to use Desktop Printer Utility, LPR printing using
> > IP on a Mac with LPRng (and NO Appletalk), I would _LOVE_ to hear from
> > you.
> >
> > This seems, if true, unfortunate, given the poor (and that's charitable!)
> > state of the Appletalk protocol. To my knowledge, most installations are
> > moving away from Appletalk. To have a product that requires it's use
> > seems most unfortunate.
> >
> > David Houston
> > CIT Client Services Coordinator
> > University of Vermont
> >
> >
> >
> > -----------------------------------------------------------------------------
> > 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.
> -----------------------------------------------------------------------------
>
>
> -----------------------------------------------------------------------------
> 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.
-----------------------------------------------------------------------------
