Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/252644

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:15, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base

Printer Error Messages Incorrectly Redirected to Terminal Server Instead of Client Session Where Error Occurred

Article ID: 252644

Article Last Modified on 3/1/2007


  • Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4
  • Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 5
  • Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 6

This article was previously published under Q252644


When you try to print from your Windows NT Server version 4.0, Terminal Server edition-based client computer to a printer configured locally on the Terminal Server (such as LPT1), you may receive the following error message on the Terminal Server console (or the client assigned to session zero):

Error writing to LPT1: for Document print job name: The device is not ready.
Do you wish to retry or cancel the job

NOTE: The error message must be cleared on the console (or the client assigned to session zero) before the spooler will continue printing any queued requests. This error message will not occur on the client computer that requested the print job.


This problem can occur if there was an incorrect check to determine which Windows-based computer actually has a direct connection to the local printer.


Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Windows NT 4.0. 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


This problem was first corrected in Microsoft Windows NT 4.0 Service Pack 6.Microsoft has confirmed that this is a problem in Windows NT 4.0.

Keywords: kbhotfixserver kbqfe kbenv kberrmsg kbfix kbprb kbprint kbqfe KB252644