Monarch Instrument 9460 - Manual (Page 28)

3-2 System Administrator’s Guide
A d d i t i o n a l W i n d o w s C o n f i g u r a t i o n M e t h o d s
The print server is also compatible with other methods of printing from
Windows. These include the Standard TCP/IP port option in Windows
2000/XP, and the LPR port option in Windows NT that are built into the
operating system.
U N I X N e t w o r k C o n f i g u r a t i o n
The print server appears to the network as a UNIX host computer with a
unique IP address running the line printer daemon (LPD) protocol. As a
result, any host computer that supports the Berkeley remote-lpr command
can spool jobs to the print server without the need for any special software
on the host computer.
Note: Before configuring a UNIX print queue, the print server must have a
valid IP address.
B e r k e l e y U N I X H o s t C o n f i g u r a t i o n
Berkeley UNIX host computers include Linux, Digital Equipment Corporation
Digital UNIX, OSF/1, and ULTRIX; Compaq Tru64 UNIX; SunOS (not
Solaris), SCO UNIX; and many others. Sun Solaris, HP/UX, IBM AIX users
should skip to the appropriate sections later in this manual.
♦ Do not use the Linux X-Windows graphical user interface printer
configuration utility, because it does not work with Paxar print servers.
Instead, Linux users should follow the configuration steps listed in this
section.
♦ SCO UNIX users should use the rlpconf command to create a printer and
automatically configure the /etc/printcap file (you will still need to edit the
/etc/hosts file). Enter the print server's service name (PXRxxxxxx_P1) as
the name of the printer and enter the name of the print server that you
assigned in the /etc/hosts file as the remote host name; note that
because this name must be unique for each printer, we recommend using
the PXRxxxxxx_P1 service instead of the normal BINARY_P1 service.