Section 6: Troubleshooting

LAN ETHERNET INTERFACE TROUBLESHOOTING

If the printer does not come up ready: Ensure the printer is powered on, all cables are connected, and the printer is on-line. If possible, connect a terminal to the serial port and observe for a boot prompt indicating the print server firmware has not been loaded properly. If reloading does not correct the problem, try setting switch 1 to On (factory defaults) and powering the printer server off and then on again. If the problem persists, the product may be defective.

If the printer comes up ready but will not print: There is a problem with the interface between the server and the printer, network connection or cabling, or queue setup flaw. The queue setup flaw could be the result of a faulty print server setup or other protocol-related senarios. Systematically perform checks and tests to isolate the cause.

The interface between the printer and server may be checked by waiting approximately two minutes after the printer is powered on and then run a self-test label. If a self-test label does not print, there could be a harware problem. Double check the cable connections. In some rare cases, disabling NBUF with the command SET PORT P1 NBUF DISABLED will solve the problem.

If connecting to a 10baseT network, verify that the OK LED is illuminated. If the appropriate LED’s are not on, there is a possiblity of a defective cable or connector. Try connecting a different cable, port, or device to observe the results.

If using a repeater or hub, ensure that SQE (heartbeat) is turned off at the hub (this is the default setting for most hubs). Also, test the hub or repeater by trying the print server on a different port.

If using a bridge or router located between the print server and the host computer, ensure that the device is setup to allow the print server to send and recieve data from the host. For example, a bridge can only be set up allow certain types of Ethernet addresses to pass through (a process known as filtering). Such a bridge must be configured to allow print server addresses. Likewise, a router can be set up to only pass certain protocols. Ensure that the desired protocol can be passed through to the print server. In the case of routers, also ensure that the protocol is routable (LAT, NetBEUI, and DLC/LLC are not routable.

Ensure that you are not attempting to perform an illegal operation such as printing a labell larger than the printer can handle.

Check the protocol troubleshooting sections provided with the Ethernet Interface Module for additional causes of intermittant printer problems.

Experiencing intermittant printing problems: Excessive NetWare polling may be a big cause of intermittant problems. Ensure that only the needed NetWare file servers have been enabled (do a SHOW NETWARE command from the print server console to see the enabled file servers). If V3.21 or earlier versions of firmware is in use, ensure that NetWare polling is disabled by using the console command SET NETWARE RANGE 0. If Netware is not in use, disable NEtWare entirely with the command SET NETWARE DISABLED.

SATO M10e Service Manual

PN 9001113A

Page 6-7

Page 61
Image 61
SATO 10e service manual LAN Ethernet Interface Troubleshooting