Chapter 7 Troubleshooting (10/100Base-T)

•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. At this point 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 indicates one of the following: 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.

•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 read: “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 does not match an existing destination name on the NIC, or Novell has been disabled for that destination. If there is a valid “Destination =” line, then double check that there is an entry for this number under the “ENP INFO” section.

NOTE: Debug messages for the PSERVER setup are in the RPRINTER section here because the PSERVER setup on the NIC shares some code with the RPRINTER setup.

•Try a debug nest logs telnet command (or find the “General Messages” section on the Novell HTML status page). Look for a valid entry for the printer. It will look something like this:

“(0:InitSinglePrinter): printer=<X> name=<NAME>”. Then lookfor the following lines: “(0:Printf): RemoteMonitor(<X>); printer

is” and “(0:Printf): WAITING_FOR_JOB”. If you see these lines, the NIC is set up properly, and the problem points to a setup issue on the workstation.

196