User`s guide

Appendix C:Accessing Network Printers
PShop User’s Guide - 49
http://www.cis.ohio-state.edu/htbin/rfc/rfc1179.html
Printers with the built-in TCP/IP protocol capability vary somewhat in the name
each uses for its logical printer - each is named as if it were a print queue on the
“local host”. Please consult the support area of Vividata’s website for details.
Whatever kind of network printer is to be supported, the idea is the same: the
bytes of data that would normally be sent to the parallel port for the printer are
instead spooled into another UNIX print queue. These print queues are in turn
serviced by either JetAdmin for JetDirect devices or by UNIX's lp for the TCP/IP
printers.
Print Servers:
A number of print servers are supported. Makes and representative models that
we and customers have tested include:
Hewlett Packard (e.g. JetDirect EX Plus, EX Plus3)
Lantronix (EPS2)
These devices do not support TCP/IP printing robustly. They require special
network drivers, available from their respective manufacturers. HP JetDirect
requires JetAdmin, and Lantronix requires RTEL - see the HP and Lantronix
sections below.
Epson Ethernet/EtherTalk interface card #C823572
(for Color Stylus 800 series, 1520, 3000, etc.)
(“remote printer” must be “lpb”)
Extended Systems (ExtendNet DX, ESI-2812)
These devices support a TCP/IP capability as per RFC-1179. Such printers
emulate Berkeley-style print queues on remote host. These devices vary in the
name each uses for its port or ports - each is named as if it were a print queue on
the “local host”. Please consult the support area of Vividata’s website for details.
How PShop is Configured for Network Printing
In order to RIP locally and print remotely, PShop’s ps_install makes the two print
queues on the local system: one for applications to print to and a second for actual
transport of the data (in-protocol) to the network printer. In the case of printers
with built in TCP/IP capability, the “host” is the printer listening on its IP
address.