SATO CL608e, Руководство по обслуживанию

Страница: 160 / 245

Page 8-6
Section 8. Troubleshooting
SATO CL608e/CL612e Service Manual
PN 9001079
Rev.B
4. If the job exits the queue but does not print, make sure that you have the correct driver
installed. If you do, turn DSW2-4 on and cycle power. Try resending your print job. If
something prints out at this point than we now that the connection is there but that the
data is not correct.
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
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
I
f 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 ):
l. The problem may be the result of mismatched or duplicate IP addresses. Verify that the
IP address is correctly loaded into the SATO enhanced ethernet adapter 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, rarpd -a,
in.rarpd -a, or equivalent command. Verify that the /etc/ethers file contains the correct
Ethernet address and that the SATO enhanced ethernet adapter 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.