T r o u b l e s h o o t i n g
C h a p t e r 1 1 : T r o u b l e s h o o t i n g
❖
11-9
Novell
NetWare
Problems
Table 11.2 lists common Novell NetWare problems, the possible
causes, and recommended corrective actions. Before you take
any action, however, refer to the Novell Print Server Guide, and
verify that the queue, print server, and printer were configured
correctly.
Table 11.2 Novell NetWare problems
Problem
Possible Causes
Corrective Actions
Print job doesnt print.
Printer is on a large network which
has 25 or more Novell fileservers.
Refer to XNIC Configuration Options,
page 3-43 for setting the following
parameters on the XNIC:
Tree name and context name (for NDS
mode)
Preferred/Required fileserver (for 3.x)
PServer name for RPrinter/NPrinter
mode.
Printers Print Server
name is not displayed in
the list after the
command tes name or
set port tes is entered.
Printers Print Server
name is not displayed in
the list after the Novell
console command
display servers is
entered.
Bad cabling.
See your network administrator for the
wiring problem.
XNICs SAP IDs are filtered out by a
network router that is located
between your printer and the
Novell file server.
Ask your network administrator to
reconfigure the router, or
Move the printer to the network segment
where the Novell fileserver resides.
The tes name or set
port tes command
displays your printer
server name, but you are
unable to log into the
XNIC remotely.
Your client workstation does not
have the latest update about the
XNIC from the fileserver.
At the C:\TES-KRMT prompt, enter tes
unload to unload the program from
memory. Then enter tes again.
The NetWare protocol on the XNIC
is disabled by someone.
Use Telnet to log into the XNIC. Enable the
NetWare protocol feature again. Refer to
Table 3.2 on page 3-55 for the XNIC
command.
The XNIC is in an unknown state.
Refer to
Resetting the XNIC to the Factory
Defaults
(page 11-7).
ETR-CH11 Page 9 Thursday, October 24, 1996 7:14 AM
