Service manual

Page 8-8
Section 8. Troubleshooting
Rev. A
SATO M-8485Se Standard Print Engine
Service Manual
The LAN Ethernet Interface (Cont)
16. If you have problems with queues locking up when the active print job is deleted, try
setting the IP timeout to one minute with the console command SET IP TIMEOUT 1.
17. There were a number lpr/lpd-related problems fixed the V3.46 firmware. Therefore, if you
are experiencing intermittent queue problems and you have an older version of firmware,
SATO recommends you upgrade to 3.46 or later.
Netware Troubleshooting
If you cannot print from NetWare and you have checked the hardware and network as described
in the previous steps, first verify that the print server is attached to the server queue by going to
PCONSOLE, selecting PRINT QUEUE INFORMATION, and then CURRENTLY ATTACHED
SERVERS. If the print server does not appear in the list of attached servers, then check the
following. (Note it is always a good idea to try deleting and recreating the print server and
creating a new print queue in order to eliminate the possibility of setup errors.)
1. If you cannot create a print queue, make sure you have sufficient NetWare privileges. With
NetWare 3.12 and earlier, you MUST be logged in as SUPERVISOR (not someone with
Supervisor privileges). If you are having problems creating queues with NetWare 4.xx and
later, try logging in as ADMIN. Also make sure you are not trying to run XAdmin32 with
Microsoft NetWare client (you must use the Novell 32-bit client).
2. If you changed the login password, you must change the password in both the print server
(using the SET NETWARE PASSWORD command) and in the file server (using the
PCONSOLE Print Server Information Change Password command).
3. Make sure you have enabled at least one NetWare file server using the SET NET WARE
SERVER servername ENABLED command.
4. Have you exceeded your NetWare user limit?
5. If you have V3.00 or earlier firmware, make sure you enable either 802.3 or Ethernet II
frames on your file server, particularly if you have a NetWare 3.12 or 4.xx file server (since
these NetWare versions default to 802.2)since these versions of firmware do not support
802.2 or SNAP frames. Also, if you are using NetWare 4.xx make sure you have enabled
binary emulation on the file server.
6. Make sure the print server name you used in PCONSOLE exactly matches the name that is
configured in the print server and make sure it is defined as a Queue Server for the print
queue.
7. If you are running both 802.3 and Ethernet II frames on different file servers on your
network, there is a possibility that the print server may not make a connection to the
desired file server. Try forcing the frame type to the desired one using the SET NETWARE
FRAME command from the print server remote console.
8. If you are losing portions of your print job and you are using the DOS NetWare drivers, try
setting the TIMEOUT parameter in your CAPTURE statement to a higher value, (at least 50
seconds for Windows).