SATO CL412E Operator And Technical Reference Manual page 226

Section 7. Troubleshooting
in as ADMIN. Also, make sure that you are not trying to run XAdmin32
with the 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 that you have enabled at least one NetWare file server using the
SET NETWARE SERVER servername ENABLED command.
4. Have you exceeded your NetWare user limit?
5. If you have V3.00 or earlier firmware , make sure that you enabled 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 that you have
enabled bindery emulation on the file server.
6. Make sure that 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).
Windows NT/LAN Server Troubleshooting
If you are having trouble printing with Windows NT or LAN Server, check the
following:
1. Make sure that you can ping the print server using the DOS or OS/2
command PING ipaddress, where ipaddress is the IP address of the print
server. If you cannot ping the print server, you will not be able to print.
2. Make sure that TCP/IP and lpr printing are installed and running on the
Windows NT system or the LAN Server file server.
3. If you are having problems printing to the print server from a client PC
that is connected to a Windows NTAS or LAN Server file server, verify that
you can print a job directly from the DOS or OS/2 prompt on the file
server. If you can print from the file server but not from the client, then
the problem is probably with the NetBEUI communications rather than
with the TCP/IP link to the print server. Check your file server network
Page 7-8 PN 9001074 Preliminary SATO CL Series "e" Printers