> I've been setting up a Linux machine in my office, and I'd like to set
> it to print to our ethernetted printers. They all have valid IPs and
> entries in our print server, which is running NT Server. I have no
> idea how to configure the printcap file, and all of the man pages I
> read completely baffle me. I also cant seem to find a decent how-to
> on the subject.
The man pages are a bit cryptic, but the Printing HOWTO does have a
large section on this. The most relevant parts are below. The whole
thing is at http://www.picante.com/~gtaylor/pht/
Feel free to pester me if you can't get it going from the HOWTO...
11. How to print to a printer over the network
One of the features of lpd is that it supports printing over the
network to printers physically connected to a different machine. With
the careful combination of filter scripts and assorted utilities, you
can make lpr print transparently to printers on all sorts of networks.
11.1. To a Unix/lpd host
To allow remote machines to print to your printer, you must list the
machines in /etc/hosts.equiv or /etc/hosts.lpd. (Note that
hosts.equiv has a host of other effects; be sure you know what you are
doing if you list any machine there). You can allow only certain
users on the other machines to print to your printer by usign the rs
attribute; read the lpd man page for information on this.
11.1.1. With lpd
To print to another machine, you make an /etc/printcap entry like
# REMOTE djet500
Note that there is still a spool directory on the local machine man-
aged by lpd. If the remote machine is busy or offline, print jobs
from the local machine wait in the spool area until they can be sent.
11.5. To an HP or other ethernet printer
HPs and some other printers come with an ethernet interface which you
can print to directly using lpd. You should follow the instructions
that came with your printer or its network adaptor, but in general,
such printers are "running" lpd, and provide one or more queues which
you can print to. An HP, for example, might work with a printcap
HP Laserjet printers with Jet Direct interfaces generally support two
built in lpd queues - "raw" which accepts PCL (and possibly
Postscript) and "text" which accepts straight ascii (and copes
automatically with the staircase effect). If you've got a JetDirect
Plus3 three-port box, the queues are named "raw1", "text2", and so
In a large scale environment, especially a large environment where
some printers do not support PostScript, it may be useful to establish
a dedicated print server to which all machines print and on which all
ghostscript jobs are run.
This also allows your Linux box to act as a spool server for the
printer so that your network users can complete their print jobs
quickly and get on with things without waiting for the printer to
print any other job that someone else has sent.
To do this, set up a queue on your linux box that points at the
ethernet equipped HP LJ (as above). Now set up all the clients on your
LAN to point at the Linux queue (eg lj-5 in the example above).
Some HP network printers apparently don't heed the banner page setting
sent by clients; you can turn off their internally generated banner
page by telnetting to the printer, hitting return twice, typing
"banner: 0" followed by "quit". There are other settings you can
change this way, as well; type "?" to see a list.
Where do these people come from? Finger for PGP public key.