Some LPD Print Servers Reject an LPD Connection from Windows NT (237181)

SYMPTOMS

When print data is sent from a NetWare client to a computer running Windows NT Server and Microsoft File and Print Services for NetWare (FPNW), Windows NT's LPR sends a packet, whose format violates RFC1179, to the LPD print server (for example, UNIX). Some LPD print servers reject the attempted connection because of the invalid packet. As a result, NetWare clients cannot send print jobs to LPD print servers using a computer running Windows NT server and FPNW.

CAUSE

This problem occurs because RFC1179 states that host name field in a packet using the LPD protocol must contain 31 or fewer characters. When a print job comes from FPNW, Windows NT's LPR sends a packet that contains more than 31 characters in the host field to the LPD print server. This causes the packet and LPD connection to be rejected by some LPD print servers.

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/windows/servicepacks/ -or-
152734how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.