Service manual

Page 8-6
Section 8. Troubleshooting
Rev. A
SATO M-8485Se Standard Print Engine
Service Manual
The LAN Ethernet Interface (Cont)
3. If you have a bridge or router located between the print server and the host computer,
make sure that the device is set up to allow the print server to send and receive data from
the host. For example, a bridge can be set up to only allow certain types of Ethernet
addresses to pass through (a process known as filtering); therefore, such a bridge must be
configured to allow print server addresses. Likewise, a router can be set up to pass only
certain protocols, so be sure that the desired protocol can be passed through to the print
server. In the case of routers, also make sure that the protocol is routable (LAT, NetBEUI,
and DLC/LLC are not routable).
4. Make sure that you are not trying to perform an illegal operation, such as attempting to
print a label larger than the printer can handle.
5. Check the individual protocol troubleshooting sections in this chapter for additional causes
of intermittent printer problems.
Intermittent Problems
If the print server and the printer start up OK, but you intermittently have problems printing,
check the following:
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
have V3.21 or earlier firmware, make sure that NetWare polling is disabled by using the
console command SET NETWARE RANGE 0. If you are not using NetWare, you can
disable NetWare entirely with the command SET NETWARE DISABLED.
2. Check the individual protocol troubleshooting sections in this chapter for additional causes
of intermittent printer problems.
TCP/IP Troubleshooting
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 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 XCD 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 NCP, XCONFIG, or ccr to enter the IP address, make sure that you exited the
remote console properly with a CTRL-D or EXIT command.
3. If you used rarp, make sure that you started the rarp daemon using the rarpd, rarped -a,
in.rarpd -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.
4. If you used bootp, make sure that bootp is enabled (i.e., the "#" is removed from the bootp
entry) in the /etc/inetd.conf file. Verify that /etc/bootptab file is correctly configured.