PSERVER Setup

When setting the NIC up as a PSERVER, did you specify a destination on the NIC (e.g., d1prn) for the printer name, and did you remember this name is case sensitive?

Note

NIC destinations are case sensitive so they will not be recognized if they

 

are typed incorrectly. By default, they are all in lowercase. If you are setting

 

up in a NetWare 4.x environment, the destination must be renamed to

 

uppercase to match the PCONSOLE or Netware Administrator entry.

 

Please see set dest destination name newname on page 247 for

 

information on changing names.

 

 

Does the destination you used in your PSERVER setup have the Novell service enabled? See Chapter 13, “Commands” for information on enabling/disabling services.

Try doing a debug nest ipx telnet command on the NIC (or find the “IPX Layer” section on the Novell HTML status page). Check that a board has been bound to the NIC and that the network number is correct for your network. If not, you may want to set a specific frame type for the NIC to use. You can find out what frame type is bound to which board number using the debug nest odi command (or from the “ODI Layer” section on the Novell HTML status page).

Try a debug nest fserver telnet command (or find the “File Servers” section on the Novell HTML status page). If no file servers show up, then there is probably a problem with the network connection, or the NIC is not on a Novell network. Try a debug nest sap telnet command (or find the “SAP” section on the Novell HTML status page) to see if the NIC is seeing any network activity.

Try a debug nest pserver telnet command (or find the “PSERVER” section on the Novell HTML status page). Look for a valid queue under the “EPS QUEUES” section. If the printer field contains a number and there is a valid file server but no queue, then you probably made an error in the setup and should try again. If it is an NDS PSERVER setup, look for a line with the following type of message “Could not login to NDS Tree <TREE> as <PSERVER.<CONTEXT>.” This means that either the tree is wrong; the context stored on the NIC for the print server object is wrong; the print server object password is wrong; or the print server object name is wrong.

237

Page 237
Image 237
Printronix P5000LJ user manual Pserver Setup