Troubleshooting Printing Problems in Windows NT 4.0

The information in this article applies to:

• Microsoft Windows NT Server version 4.0
• Microsoft Windows NT Workstation version 4.0

SUMMARY

This article describes how to troubleshoot printing problems in Windows NT 4.0.

MORE INFORMATION

Printing to a Local Device

1. Verify that you can print from a command prompt.

   Non-PostScript Printer:

   Type "dir > lpt1" (without quotation marks) at a command prompt.

   PostScript Printer:

   For information about printing from a command prompt to a PostScript printer, see the following article in the Microsoft Knowledge Base:

         ARTICLE-ID: Q64859
         TITLE     : Testing the Connection to a PostScript Printer
   
      Plotter:
   
      See the following Web site:
   
      http://hpcc923.external.hp.com/cposupport/plotters/support_doc/
      bpp02064.html
   
      This tests to determine whether the parallel port driver and the
      hardware are working correctly. If you do not receive any output, get
      garbled output, or receive an "Unable to write to port" message, check
      the following hardware issues:
   
       - Check the cable and see if it meets the IEEE 1284 specification. If
         it does, it is marked on the cable itself.
   
       - Remove any switch boxes.
   
       - Perform a self test on the printer. If it prints correctly, the
         issue is with Windows NT or the program.
   
      NOTE: Printing from a command prompt does not work if the printer is a
      PostScript Printer.
   
   

2. Try printing from WordPad or Notepad.

   This tests the printer driver. If it prints correctly, the problem lies with the program. However, this does not mean that Windows NT is not involved. Windows NT may not be running a particular printing command that the program requires. See the "Program" section of this article.

   If it does not print correctly, the problem may be in the printer driver. Try the following items:

       - If it is a PostScript printer, load the Apple LaserWriter NT driver.
         This is a very basic PostScript driver and using it will determine
         whether the problem is related to the particular PPD file for the
         printer.
   

       - If the printer is non-PostScript, load the Generic/Text Only printer
         driver. This is a very basic driver and using it will determine
         whether the basic printing stack is working properly.
   

       - If it is a plotter, load the Hewlett-Packard HP-GL/2 Plotter driver.
   

   If the device does not print with the basic drivers, see the "Printing Stack" section of this article. If it does print, see the "Program" section.

Printing to a Network Device

1. Verify basic network connectivity.

   Check user rights, protocols, share names, and so on to determine if you can see the server. Copy files to a share on the print server using File Manager in Windows NT 3.x or Windows NT Explorer in Windows NT 4.0. If you cannot access the server, you may not be able to access the printer.

2. Create a local printer and redirect the port to the network server.

   Create a local printer and in the Ports section, create a new port. Click Local, and type the server and printer name for the printer (use the \\servername\printername syntax). Use this port for the local printer. This determines whether there is a problem with the copying of files from the server to the workstation that occurs when you use a Connect To setup or click Network Printer in the Add Printer Wizard.

3. Printing from an MS-DOS-based program.

   Make sure that the NET USE command has been run to map the LPT port to the network share. If it has, delete it and re-map the port. If it then works, there may be an issue with ghosted connections. A command may need to be run in the login script to remap the port each time you log on.

   If it is still not printing, try typing "dir > LPT<x>" (without quotation marks) where <x> is the number of the port being mapped. If it still does not print, double-check the networking.

   NOTE: Printing from MS-DOS-based programs does not work if the printer is a Postscript Printer.

4. If you are using LPR or printing to a JetDirect card using the TCP/IP protocol, try these items:

       - Ping the IP address. If it fails, check the network connectivity and
         verify IP addresses.
   

       - Create an LPR port to the printer and then create a local printer
         connected to that port. This is the recommended way to connect to a
         JetDirect printer. Sharing this printer on the network allows the
         computer to act as a print queue for the JetDirect printer.
   

   For additional information, please see the following articles in the Microsoft Knowledge Base:

         ARTICLE-ID: Q124735
         TITLE     : How Windows NT LPD Server Implements LPR Control
                     Characters
   
         ARTICLE-ID: Q124734
         TITLE     : Text of RFC1179 Standard for Windows NT TCP/IP Printing
   
   

5. Determine whether you can print locally.

   If possible, try printing locally. This determines whether it is a network or computer-specific problem. Also see the "Program" and "Print Stack" sections of this article.

Program

1. Use a simpler file.

   Try creating a new document with less information in it. This determines if it is the program, or something in the document that is causing the problem.

2. Check the available disk space on the system drive.

   If there is not enough room to spool the job, larger jobs might fail where smaller jobs do not.

3. Try to print from another operating system.

   If possible, test with another operating system (such as Microsoft Windows 95). If it prints correctly, the problem is related to the output file.

Printing Stack

1. Verify that the Winprint.dll file is present. For information about how to do so, see the following article in the Microsoft Knowledge Base:

         ARTICLE-ID: Q105247
         TITLE     : Err Msg: There are no Print Processors... Creating a
                     Printer
   
   

2. Refresh all the printer files. To do so, remove all printers from the Printers folder, delete all the files from the Winnt\System32\Spool \Drivers\W32x86 folder, and then reinstall the printers.

   For additional information, please see the following article in the Microsoft Knowledge Base:

         ARTICLE-ID: Q135406
         TITLE     : Steps to Manually Remove and Reinstall a Printer Driver
   
      NOTE: If you are using a Service Pack, reinstall the Service Pack
      before reinstalling the printers.
   
   

3. Check the available space on the hard disk. If there is not enough room to spool the job, print jobs may fail.

DEC Printserver and DEC Print Monitor

The Digital Electronics Corporation (DEC) Printserver is a printer with an Ethernet card installed. It can be accessed with the TCP/IP or DECnet protocol. DECnet is available only from DEC.

When the Printserver printer is first turned on, it does not have a TCP/IP address assigned to it. The Windows NT DEC Print Monitor assigns the IP address to the Printserver printer by downloading the software and configuration to the hardware (MAC) address of the Ethernet adapter in the Printserver.

For more information about how to set this up, click Help in the Add New Port section of Print Manager. In Windows NT 4.0, see the Readme.txt file in the Drvlib\Print\Decmon folder on the Windows NT CD-ROM.

AutoCAD 13

If AutoCAD is not correctly configured to print, you may receive the following error message:

   The system is unable to set port parameters.

   http://pilot1.autodesk.com/support/techdocs/td13/td130759.htm