HP LQH-HW 3ULQWHUV manual Pserver Setup

PSERVER Setup

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

Note	LineJet Print Server 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 223 for information on changing names.

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

•Try doing a debug nest ipx telnet command on the LineJet Print Server (or find the “IPX Layer” section on the Novell HTML status page). Check that a board has been bound to the LineJet Print Server and that the network number is correct for your network. If not, you may want to set a specific frame type for the LineJet Print Server 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 LineJet Print Server card 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 LineJet Print Server card 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 LineJet Print Server for the print server object is wrong; the print server object password is wrong; or the print server object name is wrong.

•Try a debug nest rprinter telnet command (or find the “RPRINTER” section on the Novell HTML status page). Look for the following type of line: “(0:ENPReadConfig):[0:213] Destination = <X>,” where <X> is between 0 and 3. If they all say “Destination = 65536,” then the PSERVER setup did not complete properly. If there was a valid queue under “EPS QUEUES” in the debug nest pserver command, then the printer name probably doesn’t match an existing destination name on the LineJet Print Server, or Novell has been disabled for that destination. If

213