LPD Job May Cause TCPSVCS to Hang

After you sent a print job by using LPR to the TCP/IP Print Server, the TCP/IP Print server stops responding (hangs) and causes over 90 percent CPU usage in TCPSVCS.

This behavior occurs when the print job contains a value of 0x1B (ESC) in any of the following conditions:

• At offset 0xFFF (4095).
• As the very last character in a file.
• As the only character in a file.

TCPSVCS has a routine to detect PCL or PostScript jobs, which goes into an infinite loop under these conditions.

Windows NT 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/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how 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:

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:

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 5 and Windows NT Server 4.0, Terminal Server Edition Service Pack 5.