Article ID: 238070
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4
This article was previously published under Q238070
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
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, 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 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: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
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:
- Modify the LoadTrustedDrivers value in the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers
LoadTrustedDrivers = 1 - Depending on your computer, edit the appropriate registry key (where
windiris your Windows folder): 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. - Edit the AddPrinterDrivers value in the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers
AddPrinterDrivers = 0
Data Type REG_DWORD - 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: kbhotfixserver kbqfe kbbug kbfix kbqfe KB238070
