NetWare 4.1/9000 Print Services

6-19

Setting Up Printers Attached to Workstations or Servers

Troubleshooting Tips for Administering Printer Stations

For a comprehensive discussion of strategies for troubleshooting network

printing, see Appendix D, “Troubleshooting Printing Problems.”

Printing is Slow Using NPRINTER.EXE as a Remote Network Station

The following are possible reasons why printing might be substantially

slower using NPRINTER.EXE as a remote network station than using the

same printer locally from DOS:

• You may have an IRQ conflict.

Change to polled mode.

• Your port may not support hardware interrupts.

If this is the problem, use polled mode. (You can get the ability to use interrupts

by installing an I/O board that supports them.)

• You may be using the wrong type of cable or a defective cable.

Try a new cable. Some printers require a non-standard parallel cable. They will

work with a standard cable, but not effectively. Examples: IBM 4019 and 4029.

The Message “Printer is not connected” Appears on the Console Screen

This message may indicate that NPRINTER has not yet been loaded to

activate a printer that has been previously deﬁned in PCONSOLE.

Remote Serial Printer Self-Tests Successfully But is Not Working as

Network Device

Serial printers must be conﬁgured the same way as they are conﬁgured in

PCONSOLE or NetWare Administrator. The printer must be conﬁgured

through its DIP switches or through menus. See your printer’s

documentation for details.

The printer conﬁgurations must agree on baud rate, data bits, stop bits,

XON/XOFF, and parity.

NPRINTER.EXE Does Not Initialize or Hangs Periodically at Random

Sometimes the presence of a router between the NPRINTER station and the

print server can cause problems for NPRINTER, causing the printer to hang.