Oki B6100 Configuration Guide: NIC Option - Page 18

NetWare Host Troubleshooting

Page 18 highlights

2-10 Ethernet Network Interface Card Configuration Guide NetWare Host Troubleshooting Netware Host Troubleshooting (Bindery Mode) Area to Check Explanation The server and queue names Use PCONSOLE to check. match the print server and service name NetWare access table Scanning too many file servers can cause a delay between jobs.Configure the access list to only scan for jobs on the file servers of interest. Netware Host Troubleshooting (NDS) Area to Check Explanation NetWare access table By default, only local (non-routed) file servers are scanned for queues. The login password on the NIC and the queue password on the file server The passwords must match or the NIC will not be able to log into the file servers to scan for jobs. The print server has successfully attached to the queue Type NETSTAT at the Local> prompt. This will display information about fileservers, printers, and queues that the print server has found. If a queue is in JobPoll, the print server has successfully attached to the queue. The DSTree, DSContext, and DSLicense Type Show Protocol NetWare NDS. This command shows the tree and the context that you have configured, a failure code, and an NDS error code for each server. DSTree is the directory service tree on which the print server is located. DSContext is the context where the print server is located; it must match the context on the file server (The DSContext must be of the following form: ou=fruit.0=exotic). DSLicensed should be yes. Printer and queue changes have It may take a few minutes for the changes to propapropagated through the NDS tree gate. If the print server doesn't attach, reboot the server. NDS Printing Errors Bit Failure Code Meaning Remedy 1 NIC out of memory 2, 3 Unexpected response from file server Cycle power. Disable unused protocols and/or remove fileservers without print queues from the NetWare access list. Contact Technical Support.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54

2-10
Ethernet Network Interface Card Configuration Guide
NetWare Host Troubleshooting
Netware Host Troubleshooting (Bindery Mode)
Area to Check
Explanation
The server and queue names
match the print server and service
name
Use PCONSOLE to check.
NetWare access table
Scanning too many file servers can cause a delay
between jobs.Configure the access list to only scan
for jobs on the file servers of interest.
Netware Host Troubleshooting (NDS)
Area to Check
Explanation
NetWare access table
By default, only local (non-routed) file servers are
scanned for queues.
The login password on the NIC
and the queue password on the
file server
The passwords must match or the NIC will not be
able to log into the file servers to scan for jobs.
The print server has successfully
attached to the queue
Type
NETSTAT
at the Local> prompt. This will
display information about fileservers, printers, and
queues that the print server has found. If a queue is
in JobPoll, the print server has successfully
attached to the queue.
The DSTree, DSContext, and
DSLicense
Type
Show Protocol NetWare NDS
. This com-
mand shows the tree and the context that you have
configured, a failure code, and an NDS error code
for each server.
DSTree is the directory service tree on which the
print server is located. DSContext is the context
where the print server is located; it must match the
context on the file server (The DSContext must be
of the following form: ou=fruit.0=exotic). DSLi-
censed should be
yes
.
Printer and queue changes have
propagated through the NDS tree
It may take a few minutes for the changes to propa-
gate. If the print server doesn’t attach, reboot the
server.
NDS Printing Errors
Bit
Failure Code
Meaning
Remedy
1
NIC out of memory
Cycle power. Disable unused protocols and/or remove
fileservers without print queues from the NetWare
access list.
2, 3
Unexpected response
from file server
Contact Technical Support.