The information in this article applies to:
SUMMARYWhen trying to print from a Terminal Server (TS) version 4.0 client to a printer (on LPT1) on a TS server, the Printers Folder error dialog box pops up with the following message on the server side, and not on the client side:
MORE INFORMATIONSteps to Reproduce the BehaviorConfiguration:
ExplanationThe above situation could be a problem for the following reasons:
Client PrintersThis case is handled similar to the local printers. The error dialog box goes to the client, which owns that printer; otherwise, it goes to the console. The reasons for this design are as follows:
Local (System) PrintersThis case is the same as the standard Windows NT Server printer handling. Both the multiuser environments and the "server in a closet" case are handled.A Windows NT Server alert is sent to the printer Administrators. This alert, however, is sent only once per job if the dialog box keeps timing out, to prevent the overnight flooding of the error messages. If the dialog box is answered, then the ALERT is re-armed in case the job hangs up again. The local printer pop-up dialog box is sent to the console. This error dialog box times out in 5 minutes if the server is enclosed. If this message is not answered in 5 minutes, however, the job is not deleted. This is to prevent spooler threads from getting buried in the message box, preventing the printer Administrators from deleting the job and/or the printer. Because the spooler relies on blocking in a message box until an answer is received, the message box is still created on the console with the standard 5-minute timeout. This allows for the correction of the printer problem in less than 5 minutes, or an automatic retry of the job occurs in 5 minutes if the server is "in the closet". If someone purges the job from the Print Administrator during the 5-minute wait, the job is deleted when the message box times out. This keeps the printers from locking up when there is no console access, but still allows resuming faster when someone fixes the printer problem and answers the console. This is not the "ideal" way to handle the printer error pop-up dialog box for the remote logon user because the client doesn't receive any notification about this event and is left in the dark. This problem has been rectified in Windows 2000 where the error dialog box goes to the correct client session. Additional query words: Terminal Server
Keywords : kbNTOS400 kbPrinting kbGrpNTDDK |
Last Reviewed: August 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |