HP Jetdirect 310x - Print Server For Fast Ethernet User Manual page 127

23
UNABLE TO
ATTACH TO
QUEUE
24
PSERVER CLOSED
CONNECTION
25
DISCONNECTING-
SPX TIMEOUT
26
UNKNOWN NCP
RETURN CODE
27
UNEXPECTED
PSERVER DATA
RCVD
28
OUT OF BUFFERS
29
UNABLE TO
SENSE NET
NUMBER
2A
NDS ERR:
EXCEEDS MAX
SERVERS
2B
NDS ERR:
UNABLE TO
LOGIN
2C
AUTHENTICATION
ERROR
A failure was detected when the print server tried to attach to one of the
queues assigned to the print server object. This may be because no
servers are allowed to attach to this queue. There may also be a
networking or security problem. Use PCONSOLE to make sure that
servers are allowed to attach to the queue, to delete the print server
object from the list of queue servers if you want the print server to
service other queues, or to delete the queue and create a new one (the
print server object must be added to the list of queue servers).
Note: When the print server is configured for multiple file servers, the
error is only displayed on the configuration page if none of the file
servers was successfully connected.
The NetWare print server requested a termination of the connection
with the print server. No error exists or is indicated. Make sure the
NetWare print server is running, and restart it if necessary.
The SPX connection to the print server was lost after the connection had
been made. This indicates a possible network problem, or a problem
with the print server. Make sure all cables and routers are functioning
correctly. Try restarting the print server.
The print server encountered an unexpected fatal error after it had
successfully connected to the file server. A wide variety of failures
could produce this error message, including a downed file server or a
network router failure.
The print server sent some data when the print server had not given its
permission to do so. This indicates a possible print server problem,
possibly a software problem.
The print server was unable to allocate a buffer from its internal
memory. This indicates all buffers are busy due possibly to heavy
broadcast traffic or large amounts of network traffic directed to the print
server.
The print server has been trying for over 3 minutes to determine the
NetWare protocol used on the network. Make sure that any file servers
and routers are operating correctly. Make sure that the settings for
NetWare frame type and source routing are correct.
More queues were assigned than the print server can handle. Remove
one or more print queues from the list to be serviced by Queue Server
mode.
Unable to log onto the NetWare directory tree. Make sure that the print
server object is defined in the directory at the correct context. Clear the
print server password using NWADMIN or similar NetWare tool.
Unable to log onto the NetWare directory tree. Make sure that the print
server object is defined in the directory at the correct context.