NetWare 4.1/9000 Print Services

D-17
Troubleshooting Printing Problems
Troubleshooting Notes
application to determine if this is the case.
• Interrupt conflicts may exist between the port and another device. Configure the
printer for no interrupts (polled mode).
• The baud rate may be slow (serial printer).
• XON/XOFF may need to be enabled (serial printers).
• Your hardware (cable, port, printer) may be faulty.
• The /B parameter may be needed with CAPTURE if the job is a binary file.
16. Determining Whether a Printer is Connected as a Network
Printer
In order for a printer to be accessed by the network, ALL of the following
must occur:
• The printer must be properly connected to a server or workstation (or to the
network cabling with a network-direct device).
• The printer must be functional as a local printer (unless it is a network-direct
printer). If a printer will not work locally, it will not work as a network printer.
See Note 3 for more information.
• The printer must be configured and have a queue assigned to it (using Printer
Setup, PCONSOLE, or NetWare Administrator).
• The server or workstation the printer is connected to must have the port driver
loaded (NPRINTER).
17. Troubleshooting Jobs Printed in Pieces on Separate Pages
A print job can be broken and printed on separate pages for several reasons:
• The CAPTURE timeout setting may be too short. If there is a pause in the flow
of data between the application and the port, and it is long enough for the timeout
to end the job, the next data that comes will be sent to the queue as a new job. The
new job will be printed on a new page because a form feed is issued.
• Misinterpreted control characters in a job may also cause a form feed in the
middle of a job. Sometimes this problem can be corrected by sending the job as
Byte Stream (No Tabs).
• The printer may not have sufficient memory to hold the entire page to be printed.
If it does not, it will print the part of the page it has in memory and continue