Computer May Hang if Multiple Terminal Server Users Connect to a Remote Printer and Print Simultaneously

ID: Q238070

The information in this article applies to:
  • Microsoft Windows NT Server version 4.0 SP4, Terminal Server Edition
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

A computer running Windows NT Server 4.0, Terminal Server Edition, Service Pack 4 may stop responding (hang) or may display an error message on a blue screen if multiple Terminal Server users connect to a remote printer and print simultaneously.


CAUSE

This behavior occurs if the printer driver that is installed is incompatible with Terminal Server.


RESOLUTION

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

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack


STATUS

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


MORE INFORMATION

You can use this update to prevent non-administrative users from installing printers. To install a printer, use the appropriate option.

Option 1

Install the appropriate printer, which installs the drivers locally. Non-administrative users can create printers based on these drivers.

Option 2

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

Copy all the printer drivers to a trusted path on the local computer so non-administrative users can install the drivers from this local path. To set the trusted path:
  1. Modify the LoadTrustedDrivers value in the following registry key:


    2. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers

    LoadTrustedDrivers = 1
  2. Depending on your computer, edit the appropriate registry key (where windir is your Windows folder):


    3. For x86-based computers:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\servers

    TrustedDriverPath = "windir\system32\spool\drivers\w32x86"

    The value data type should be REG_SZ.
    For Alpha-based computers:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\servers

    TrustedDriverPath = "windir\system32\spool\drivers\w32alpha"

    The value data type should be REG_SZ.
  3. Edit the AddPrinterDrivers value in the following registry key:


    4. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers

    AddPrinterDrivers = 0

    Data Type REG_DWORD
  4. Restart the computer.


NOTE: Make sure that newer printer drivers are compatible with Terminal Server. You should ask multiple users to install and use the drivers in a test environment prior to installing the drivers on production servers.

Additional query words: wts printing crash

Keywords : ntstop ntsp kbbug4.00 kbfix4.00
Version : winnt:4.0 SP4
Platform : winnt
Issue type : kbbug


Last Reviewed: November 23, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.