> From [EMAIL PROTECTED] Tue Oct 10 21:36:26 2000
> To: [EMAIL PROTECTED]
> cc: [EMAIL PROTECTED]
> Subject: Re: LPRng: Socket API Printing is S L O W
> Date: Tue, 10 Oct 2000 20:35:37 -0700
> From: Timothy Demarest <[EMAIL PROTECTED]>
>
> On Tue, 10 Oct 2000 16:12:38 -0700 (PDT) [EMAIL PROTECTED] wrote:
>
> >
> >I am suprised at the transfer rate - this is VERY slow.
> >Something is wrong here. I had an HP4000 and it was NEVER
> >this slow. Mind you, it took a while for it to PRINT.
> >
> >Do me a favor - instead of appsocket use RFC1179.
> >
> >lp:
> >:[EMAIL PROTECTED] <- no IP.Printer.Address%9100
> >
> >See what the speed is like...
> >
> >By the way, the Solaris lp uses this method, I recall...
> >
>
> Patrick:
>
> I've switched to LPD (as stated in my original message) and the same
> 1MB+ file prints in *seconds* rather than the 15+ minutes that it takes
> with Socket API printing. This is true for other printers as well as
> other files. the other printers are: HP 5siMX, HP 4000, HP 4050N, and
> an HP 6MP.
>
> I'd like to add that my original message said I was using "AppSocket"
> but I really meant "Socket API".
Oh... Hmmm... that does make a difference...
>
> I've upgraded the firmware on the JetDirect cards on the HP printers, and
> this didn't help. I've checked the JetDirect interfaces for errors, and
> there are very low instance of any TCP/Ip (or other errors). Network
> connectivity looks good. The printers are all 10Mb switched ethernet,
> connected to a Cisco Catalyst 5500. We don't have any networking
> problems that I am aware of.
>
> The print server is a Sparc 10 (dual processors) running Solaris
> 2.5.1. It is essentially doing nothing else, and our printing
> requirements are fairly modest -- the server doesn't break a sweat.
>
> Obviously, I'd like to use Socket API printing rather than LPD. Let
> me know if a snoop trace would be helpful.
> --
> Timothy Demarest ArrayComm, Inc.
> [EMAIL PROTECTED] 2480 N. 1st Street, Suite 200
> http://www.arraycomm.com San Jose, CA 95131
>
The problem is with the HP printers, with HP firmware.
Contact HP ASAP and report this, and then start pounding
away at their support folks, elevate the request, (say hello
to Janet on your way up the ladder). Post this to BugTraq,
all the mailing lists, and so forth.
Now, as the developer of the LPRng software, I want to play nice
with HP, but as end users, you, of course, do not need to
be as courteous in getting their attention.
Patrick Powell
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
