Subject: | |
From: | |
Reply To: | |
Date: | Mon, 5 Oct 1998 19:10:44 -0400 |
Content-Type: | Text/Plain |
Parts/Attachments: |
|
|
In <[log in to unmask]> [log in to unmask] writes:
> I'd like to get network printing working from our HP3000
> to a HP2654B line printer(with serial interface).
>
> As a practice run I'm starting with network printing to
> a RuggedWriter as this may be a simpler task.
FWIW: I just went through this excercise with an Epson dot-matrix printer,
trying to get it to print (similar setup; jetdirect ex, pjl and jam recovery
disabled in npconfig). After seeing results similar to what you were
reporting (and confirming that the Jetdirect utility on a PC printed to the
same printer/jetdirect combo just fine) I called the HPRC.
I had verified that we could ping it, telnet to port 9000 on the box, and
print to it from the pc. Whenever we sent something from the 3000, it went
into the bit-bucket. Not a trace-ola.
The engineer (forget his name, but I have the PICS# written down) told me in
no uncertain terms that; "not only is it unsupported (which I knew), it WILL
NOT work". He went on to elaborate that to function with the MPE/iX (network)
spooler, the printer needs *some* level of PJL support (even though PJL is
specifically disabled in npconfig). He went on to tell me that not even all
HP printers would work, (I think he did say some of the 256x printers did
work?) and he gave me a list of product numbers for HP printers that actually
*do* work and are actually currently sold (the contract required new equipment
).
This seemed contrary to some of the reports I'd heard of odd printer types
working with network printing, but he was very sure of himself (and claimed
to have discussed it directly with the folks that developed the spooler code).
So we ordered some new printers... :-(
-Chris Bartram
|
|
|