http://www.microsoft.com/technet/boes/winnt/technote/lprfocus.htm (PC Press Internet CD, 03/1996)
| Updated: March 15, 1996 |  Go To TechNet Home Page |
By John Jacobs
ABSTRACT: Highlighting content available on the TechNet
CD, this article discusses Windows NT TCP/IP printing. It also
provides sample queries that demonstrate effective ways to locate
information.
Introduction
General Information
Compatibility
Setup, Configuration, and Usability
Administrative Information
Known Problems
Conclusion
Focus groups and product support statistics indicate that many people want TCP/IP printing information. "TCP/IP printing" can have any of three meanings:
A utility named Line Printer Remote (LPR) sends print jobs from a client computer, and a service named Line Printer Daemon (LPD) receives print jobs on a server computer. LPR and LPD encode messages to each other using a public specification, Request for Comment 1179 (RFC1179). The messages usually include the print job itself (the "data file") and printing instructions (a "control file" containing "control commands").
This type of "TCP/IP printing" generates by far the most calls to Product Support Services (PSS), and it is the topic of this article.
The Windows NT printing architecture allows third parties to write software that supports proprietary printing solutions, but the only such software supplied with Windows NT is designed for Digital Equipment Corporation PrintServer printers. Very few TCP/IP printing problems involve this software. For more information query TechNet using "DECPSMON" or "Digital Network Port."
Problems printing between NetBIOS computers are rarely protocol-specific. For more information query TechNet using key words from an error message, or words you think would be included in problem description.
This month's PSS Focus outlines the top Knowledge Base articles and TechNet documents that address LPR printing. Each section below includes a brief synopsis of each cited document, and boldfaced sample queries that show effective ways to search for information on the TechNet CD.
To find LPR and/or LPD information, query TechNet using (LPR or LPD). The best single source of information is Chapter 6 of the Windows NT 3.5 Resource Kit:
| Article Title | Article Summary |
| Windows NT 3.5 Resource Kit: Resource Guide-Chapter 6: Printing | Chapter 6: Printing explains the Windows NT printing architecture in detail. Subsections 6.5.2.2 and 6.5.6.6 provide information about LPR and LPD, respectively. Topics include setup and configuration, compatibility issues, and administration. |
RFC1179 is the industry standard specification for TCP/IP printing. Windows NT LPR can send print jobs to any RFC1179-compliant LPD service, such as one running on a UNIX computer, on another Windows NT computer, or on a printer with its own network adapter. Windows NT LPD can receive print jobs from any RFC1179-compliant LPR client, including UNIX computers and other Windows NT computers.
Many third-party TCP/IP printing solutions are not based on RFC1179, and most of the rest either do not implement the entire specification or else rely on proprietary extensions. Third party variations from the specification cause the majority of the reported compatibility problems. To find compatibility articles, query for RFC1179 and (LPR or LPD). Most of these articles are located in the Windows NT Knowledge Base:
| Article Title | Article Summary |
| Text of RFC1179 Standard for Windows NT TCP/IP Printing (PSS ID Number: Q137391) | Useful for decoding protocol analyzer traces to determine whether an LPR client and LPD server conform to the standard. |
| Windows NT LPD Service Requires One Control File Per Data File (PSS ID Number: Q124303) | Some UNIX computers send multiple data files with only one control file, contradicting RFC1179. |
| How Windows NT LPD Server Implements LPR Control Characters (PSS ID Number: Q124735) | Summary of Windows NT support for the control commands specified by RFC1179. |
| TCP/IP Printing Supports Only Berkeley Style Daemons (RFC1179) (PSS ID Number: Q121737) | There are two main types of UNIX operating systems: Berkeley (BSD), and System V. The former's print method is compliant with RFC1179; the latter's is not. |
| HP JetDirect Firmware Versions and Windows NT Protocol Support (PSS ID Number: Q124293) | Hewlett-Packard JetDirect internal adapters and external "print server" hardware may or may not support RFC1179, depending on the device's firmware revision. |
Online Help and the User Guide document basic setup, configuration, and usability topics. To find supplemental information, try one of the following queries:
| (LPR or LPD) and setup | For setup information |
| (LPR or LPD) and config* | For configuration information |
| (LPR or LPD) and "-o option" | Example of a product feature |
| (LPR or LPD) and "name of printer on that machine" | Example of key words from the user interface |
These queries find articles such as:
| Article Title | Article Summary |
| Windows NT 3.5 Resource Kit: Resource Guide-Chapter 6: Printing, Subsection 6.5.6.6. | Contains examples and guidelines for installing and using LPD. |
| Windows NT 3.5 Resource Kit: Update-Appendix C Minor Revisions to Existing Resource Kit Books, Resource Guide, Resource Guide | This document contains only one revision related to LPR printing, but it is important:
"When you use the LPR command to send print jobs to a Windows NT Server print server, the name of the printer is the text in the Print Name field of the Printer Properties dialog box; it is not the text in the Share Name field." |
| LPR.EXE Command Can Pass Control Characters to an LPD Server (PSS ID Number: Q124567) | How to use the -o switch with LPR.EXE to send a specific control command on a per-job basis. |
| Windows NT 3.5 Resource Kit: Networking-A.6 LPQ, and A.7 LPR | Syntax charts for the LPR and LPQ commands. |
Several articles provide planning and maintenance information unrelated to specific problems. Try queries of the form (LPR or LPD) and registry.
| Article Title | Article Summary |
| LPR and LPD Registry Entries for TCP/IP Printing (PSS ID Number: Q121786) | Details of four features not accessible through the LPR or LPD user interfaces. |
| Sockets Applications Do Not Switch to Second NIC if One (PSS ID Number: 129005) | This general topic applies to LPR and LPD because they are sockets applications. Useful for planning fault-tolerant print servers. |
| Windows NT Remote Printer Administration Limitations (PSS ID Number: Q120019) | The Windows NT printing architecture restricts certain remote administration tasks, some of which affect LPR and LPD. |
| Windows NT 3.5 Resource Kit: Update-Chapter 2 Licensing, Situations that Use Up Licenses | Connections to a Windows NT LPD print server count against legal connection limits. |
Articles about known LPR and LPD problems are located in the Windows NT Knowledge Base. Try these queries:
| (LPR or LPD) and "Cannot Reach the Destination" | Example of key words from an error message |
| (LPR or LPD) and "PostScript code" | Example of words describing symptoms |
The articles below describe the most frequently reported problems:
| Article Title | Article Summary |
| Troubleshooting Windows NT Print Server Alteration of Print Jobs (PSS ID Number: Q132460) | Windows NT print servers are able to alter client print jobs. This often occurs when a UNIX computer uses LPR to send a print job to a Windows NT print server. The most common symptom is PostScript or PCL code printed on the page. |
| Print Job to LPR Printer Does Not Print (PSS ID Number: Q128352) | LPR on a Windows NT print server writes temporary files in the %systemroot%\SYSTEM32 directory using the job creator's security context; restricting access to that directory prevents LPR from functioning. |
| LPR Unable to Print to LPD Queue Names with Lowercase Letters (PSS ID Number: Q128934) | Windows NT LPR always uses an uppercase version of the LPD server's queue name. This article documents the problem and workarounds. |
| Job Prints While Spooling Option Ineffective With LPR (PSS ID Number: Q131982) | The Job Prints While Spooling option reduces print times in most cases; however, RFC1179 does not permit this functionality. |
The documents described in this article can help you implement LPR and LPD printing on your Windows NT network. We hope these references make TCP/IP printing and troubleshooting easier, and that the querying tips give you ideas for more efficient search strategies.
Microsoft TechNet
Volume 4, Issue 2
February 1996
 |
Click Here to Search TechNet Web Contents | TechNet CD Overview | |
Microsoft TechNet Credit Card Order Form At this time we can only support electronic orders in the US and Canada. International ordering information. |
| Go To TechNet Home Page |
©1996 Microsoft Corporation |  Go To Microsoft Home Page |