23

A failure was detected when the print server tried to attach to one of the

UNABLE TO

queues assigned to the print server object. This may be because no

ATTACH TO

servers are allowed to attach to this queue. There may also be a

QUEUE

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.

24

The NetWare print server requested a termination of the connection

PSERVER CLOSED

with the print server. No error exists or is indicated. Make sure the

CONNECTION

NetWare print server is running, and restart it if necessary.

25

The SPX connection to the print server was lost after the connection had

DISCONNECTING-

been made. This indicates a possible network problem, or a problem

SPX TIMEOUT

with the print server. Make sure all cables and routers are functioning

 

correctly. Try restarting the print server.

26

The print server encountered an unexpected fatal error after it had

UNKNOWN NCP

successfully connected to the file server. A wide variety of failures

RETURN CODE

could produce this error message, including a downed file server or a

 

network router failure.

27

The print server sent some data when the print server had not given its

UNEXPECTED

permission to do so. This indicates a possible print server problem,

PSERVER DATA

possibly a software problem.

RCVD

 

28

The print server was unable to allocate a buffer from its internal

OUT OF BUFFERS

memory. This indicates all buffers are busy due possibly to heavy

 

broadcast traffic or large amounts of network traffic directed to the print

 

server.

29

The print server has been trying for over 3 minutes to determine the

UNABLE TO

NetWare protocol used on the network. Make sure that any file servers

SENSE NET

and routers are operating correctly. Make sure that the settings for

NUMBER

NetWare frame type and source routing are correct.

2A

More queues were assigned than the print server can handle. Remove

NDS ERR:

one or more print queues from the list to be serviced by Queue Server

EXCEEDS MAX

mode.

SERVERS

 

2B

Unable to log onto the NetWare directory tree. Make sure that the print

NDS ERR:

server object is defined in the directory at the correct context. Clear the

UNABLE TO

print server password using NWADMIN or similar NetWare tool.

LOGIN

 

2C

Unable to log onto the NetWare directory tree. Make sure that the print

AUTHENTICATION

server object is defined in the directory at the correct context.

ERROR

 

Page 127
Image 127
HP 175X, 310X manual NetWare print server is running, and restart it if necessary