General Tcp/Ip Unix Host Configuration - Brother HL-4200CN Network User's Manual

General TCP/IP UNIX Host Configuration

The configuration process for most UNIX systems is described in the following steps. As this process
varies, we recommend that you refer to your system documentation (or man pages) for additional
information.
1
Configure the /etc/hosts file on each UNIX host that needs to communicate with the print server.
Use your favorite editor to add an entry to the /etc/hosts file containing the IP address and node
name of the device. For example:
192.189.207.3
The actual format of the entry may vary depending on your system, check your system documentation
and also note the format of other entries in the /etc/hosts file.
The node name in this file does not necessarily need to be the same as the one that is actually
configured into the Brother print server (the name that appears on the printer settings page),
however, it is good practice to make the names the same. Some operating systems, such as HP/UX,
do not accept the "_" character in the default name, for these systems you must use a different
name).
In any case, the node name in the /etc/hosts file must match the node name in the /etc/printcap
file.
Some systems such as HP/UX and AIX allow you to enter the IP address as the host name when setting
up the print queue. If this is the case, you do not need to configure the hosts file.
2
Configure the /etc/printcap file on each host computer to specify the local print queue, the print
server name (also called remote machine or rm), and the print server service name (also called
remote printer, remote queue, or rp), and the spool directory.
This step applies to the majority of UNIX systems, including Linux, Sun OS (but not Solaris 2.xx),
Silicon Graphics (lpr/lpd option required), DEC ULTRIX, DEC OSF/1, and Digital UNIX. SCO UNIX
users should follow these steps, but should also refer to the SCO UNIX Configuration section. Users
of RS/6000 AIX, HP/UX, Sun Solaris 2.xx, and other systems that do not use the printcap file should
skip to section 3-a. SCO user's should also skip to section 3a (SCO uses the printcap file, but this file
is automatically configured via the rlpconf command).
An example of a typical printcap file:
laser1|Printer on Floor 1:\
:lp=:\
:rm=BRN_310107:\
:rp=TEXT_P1:\
:sd=/usr/spool/lpd/laser1:
BRN_310107
UNIX PRINTING 1 - 2