Paxar 9800 Series User Manual
Page 63
Troubleshooting 10-3
1. Excessive NetWare polling can be a big cause of intermittent problems. Make
sure that you have only enabled the NetWare file servers that you need for
printing (do a SHOW NETWARE command from the print server console to see
the enabled file servers). If you are not using NetWare, you can disable
NetWare entirely with the command SET NETWARE DISABLED.
2. If you can print small jobs OK but large graphics jobs are distorted or
incomplete, make sure that you have adequate memory in your printer.
3. Check the individual protocol troubleshooting sections in this chapter for
additional causes of intermittent printer problems.
T C P / I P T r o u b l e s h o o t i n g
If you are using TCP/IP and cannot print to the print server and you have checked
the hardware and network as described in the previous steps, then check the
following (note that it is always a good idea to try creating a another print queue to
eliminate the possibility of setup errors):
1. The problem may be the result of mismatched or duplicate IP addresses.
Verify that the IP address is correctly loaded into the print server (via the self-
test page or through the remote console) and make sure that no other nodes on
the network have this address (DUPLICATE IP ADDRESSES ARE THE
BIGGEST CAUSE OF TCP/IP PRINTING PROBLEMS). If the address is not
correct, then check whether the loading procedure was properly executed.
2. If you used rarp, make sure that you started the rarp daemon using the
r a r p d ,
r a r p d - a , i n . r a r p d - a
, or equivalent command. Verify that the
/etc/ethers
file contains the correct Ethernet address and that the print
server name matches the name in the /etc/hosts file.
3. If you used bootp, make sure that bootp is enabled (the “#” is removed from the
bootp entry) in the /etc/inetd.conf file. Verify that /etc/bootptab file is
correctly configured.
4. Also verify that the host computer and the print server are either on the same
subnet (for example, if the print server has a subnet mask of 255.255.255.0,
the host must have the same subnet mask) or that the router is properly
configured to pass data between the two devices.
5. Make sure that the /etc/printcap file (if applicable) is typed in correctly. In
particular, look for missing ":" and "\" characters, because a small error
anywhere in the file can have major consequences. Also check the