Lantronix ETS16PR - Manual (Page 40)

NetWare Configuration
40 ETS Installation Guide
Area to Check Explanation
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
ETS is located. DSContext is the context where
the ETS is located; it must match the context on
the file server (The DSContext must be of the
following form: ou=fruit.o=exotic). DSLicensed
should be yes.
Printer and queue
changes have
propagated through
the NDS tree It may take a few minutes for the changes to
propagate. If the ETS doesn’t attach, reboot the
ETS.
Table 6-3. NDS Errors from the File Server
Code Meaning Remedy
0xfffffda7 Object could not be
found in the given
context Check the ETS server name, DScontext,
and DStree to ensure the printer server is
set up correctly with PCONSOLE.
0xfffffda5 Requested attribute
could not be found Use PCONSOLE to ensure that the ETS
has associated printers and the printers
have associated queues.
0xfffffd69 DS Database is
locked An administrator is probably updating the
database. Wait a few minutes and issue
the Set Protocol NetWare Reset
command.
0xfffffd63 Invalid password The password for the print server object
under PCONSOLE must match the ETS
login password. If the login password on
the ETS is left as the default (access),
there should be no password for the print
server object.
0xfffffd54 Secure NCP
violation Turn down the NCP packet signature
level so that it is not required.
Table 6-4. NDS Errors from the File Server
Bit Meaning Remedy
1 Server out of
memory Turn the ETS off, wait a few seconds, and
turn it back on. Disable unused protocols
and/or remove fileservers without print
queues from the NetWare access list.
2, 3 Unexpected
response from file
server Report the problem to Lantronix
Technical Support.
4 No printers found for
the ETS Ensure that there are printers for the
ETS, and the printer names match the
service names on the ETS.
5 No printer queue
found Ensure that the printers have associated
queues.
6 Login failed Ensure there is a print server object
configured with the same name as the
ETS.