
Chapter 6 Troubleshooting (10/100Base-T)
•Is the PrintNet configured as the queue’s “Currently Attached Server”? If not, make sure you have associated the queue and the printer. See “Novell Host Configuration” on page 79.
•Is there a hold on the print job? If you select the job from PCON- SOLE’s CURRENT PRINT JOB ENTRIES, change the User Hold or Operator Hold to “no.”
•If you look in PCONSOLE’s CURRENT QUEUE STATUS within the PRINT QUEUE INFORMATION menu, is the server configured to service entries in this queue? It is possible to turn servicing off here.
If you’ve followed the suggestions above and are still having printing problems, try rebooting the PrintNet. Then either review every step you took when configuring the PrintNet, or try
The job prints incorrectly
This category really can be broken down into several
(e.g., CAPTURE, NPRINT, etc.):
•Did you include the No Tabs option?
•Did you specify No Banner with PostScript printers?
•Did you turn off banner pages and form feeds if this is already taken care of within an application or on the PrintNet? Doubling up of these types of print features is easy to do since these options are provided both on the PrintNet (in a model) and within the print command.
•Are you running the latest version of PSERVER (later than 1.22)? If not, upgrade the PSERVER software.
•In a PSERVER setup, did you ensure that the printer name (e.g. d1prn) was set up as “Defined Elsewhere”?
•Is the timeout option in the CAPTURE command set high enough so the printer doesn’t time out before the print processing has had a chance to complete? This can be a problem with graphic jobs.
116