T r o u b l e s h o o t i n g
11-14
❖
X N I C - E N E T / T R I N G C o n f i g u r a t i o n G u i d e
UNIX TCP/IP
Problems
Table 11.3
UNIX TCP/IP problems
(page 11-16) lists common
UNIX TCP/IP problems, their possible causes, and recommended
corrective actions. Before you take any action, however, first
check for the following:
On a TCP/IP network host computer, enter the command:
p i n g
d d d . d d d . d d d . d d d
where
d d d . d d d . d d d . d d d
is the printers IP address. If you
do not succeed, the problem is most likely with the network
facility or configuration parameters.
Attempt a remote login to the RCF port as described in the
section
Logging into the XNIC
(page 5-35).
If you do not succeed, the problem is most likely with the
network facility or configuration parameters.
If you can perform a remote login, the problem is most
likely with the print queue definitions.
Have you changed the IP address, server name, or service
name in the XNIC? Be sure the correct information is also
found in your host configuration files.
On TCP hosts, ensure that the server name (XNE
xxxxxx
or
XNT
xxxxxx
), IP address, and Ethernet hardware address are
entered in the
/etc
files, such as
/etc/ethers
,
/etc/hosts
, and
/etc/printcap.
(Only some of these files might be used.) If you
are using NIS (Yellow Pages), this information must be
entered in the NIS master hosts file.
If you encounter trouble printing from a TCP host using
lpd
:
Examine the
/etc/printcap
file to ensure the correct printer
name, queue name, and node (server) names are entered.
Verify that you used the correct queue for the type of file:
rp=PASSTHRU
for Postscript, PCL, or binary files;
rp=TEXT
for ASCII files.
If you are printing from a TCP host using
rprint
, error events
are written to a default log file named
/tmp/rpn[pid].log
,
where
[pid]
is a process number.
ETR-CH11 Page 14 Thursday, October 24, 1996 7:14 AM
