[95214] in RedHat Linux List
Re: network printing
daemon@ATHENA.MIT.EDU (Jose M. Sanchez)
Thu Oct 15 23:31:04 1998
Reply-To: "Jose M. Sanchez" <opjose@ex-pressnet.com>
From: "Jose M. Sanchez" <opjose@ex-pressnet.com>
To: <redhat-list@redhat.com>
Cc: <jan@wotan.opt-sci.Arizona.EDU>
Date: Thu, 15 Oct 1998 23:42:51 -0400
Resent-From: redhat-list@redhat.com
The "N" designation normally means that you have a Jetdirect card in the
printer.
All you have to do is assign a VALID IP number to the printer via the front
panel controls.
Once done, you should be able to telnet into it for further adjustments if
required...
Anyway, then add an entry for it in /etc/hosts or better yet if you are
running DNS add it to your hosts, and your reverse lookup tables. The latter
is useful to return printer status messages...
Finally follow the directions included with the jetdirect card to set up BSD
printing MANUALLY.
All you need to do is modify the printcap to reflect what they show you.
Note you really DO NOT nead the "TEXT" printer queue since the print filter
is pretty intelligent about this...
Once done, go into your control-panel and configure the "printer filter" by
assigning a "type of printer" to the associated queue... If you've modified
your printcap correctly (and created the spool directories) then the
associated printer queue will appear in the control-panel. Tell Linux it is
an HP4 printer... and away you go...
If you then install Samba or Mars both will recognize the printer as a
"local" resource and allow others to "attach" to the respective shares...
Samba is nicer since even if you do not have the postscript modules, Samba
treats it as a Postscript printer, by processing all postscript output via
ghostscript... this is a very neat feature as it DOES improve greyscale
output...
Once caveat. Your clients MAY go ahead and use the HPLaserJet drivers, but
the print filters for Postscript will NOT know how to deal with the PJL
commands sent by the Winblows drivers... and you get no postscript output.
(PCL works fine though).
To overcome this you'll need to change the Postscript Output Format to
"Archive Format". This supresses the PJL headers that mess up ghostscript.
Mars will only allow you to use the inherent capabilities of the printer...
If you are attempting to share the printer directly connected to the linux
box, things are even simpler.
Get it to print from Linux, then install Samba or Mars... (Mars requires the
MS Novell drivers) and your Winblows boxes can print.
You can also get other Linux boxes to print to it by using the same
technique used for the JetDirect card, except you'll point the queues on the
OTHER linux machines to YOUR PRINT SERVER machine instead.
You can play a lot of games with this, redirecting print queues from one
machine to another for processing...
-JMS
-----Original Message-----
From: Jan Heurich <jan@wotan.opt-sci.Arizona.EDU>
To: redhat-list@redhat.com <redhat-list@redhat.com>
Date: Thursday, October 15, 1998 9:51 PM
Subject: network printing
>Hi,
>
>I need to use a linux machine as a network print server for a HP Lj4000n
>network printer. Does anybody know how to address these printers?
>
>Somehow I can't get these things to work ;-(
>
>Thanks
>
>Ciao Jan
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
