Paxar 9800 Series - Manual (Page 65)

Troubleshooting 10-5
1. If you cannot create a print queue, make sure that 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 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
XCD print server (using the S E T N E T W A R E P A S S W O R D command) and in the file
server (using the PCONSOLE P r i n t S e r v e r I n f o r m a t i o n C h a n g e P a s s w o r d
command).
3. Make sure that you have enabled at least one NetWare file server using the
S E T N E T W A R E S E R V E R s e r v e r n a m e E N A B L E D 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
S E T N E T W A R E F R A M E 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).
9. Because of a bug in the vendor's software driver, file servers equipped with
certain models of SMC Ethernet controllers may crash when the print server is
connected to the network. This problem, which primarily affects EISA-based
controllers made in 1993 or earlier, is not specific to Monarch print servers,
and can be fixed by upgrading the file server with the latest SMC drivers.
Contact SMC technical support at (516) 435-6250 for additional information and
instructions on how to download the new drivers from the SMC bu lletin board.