Windows 2003 Terminal Services Remote Printing
In order to let the printer redirection work in the Windows 2003 terminal server, you must meet the following requirement:
1. You must enable the printer redirection on the RDP client.
(Start the RDP client with the command MSTSC, Options => “local resources” => check the options of the “printers”)
2. You must enable the printer redirection on the terminal server.
Start => Terminal Services Configuration => Connections => Double click on “RDP-TCP”, click “Client Settings”, and make sure the following check boxes had NOT been checked in the “Disable the following” tab:
Windows Printer Mapping
LPT/COM port Mapping
3. Use Windows Server 2003 RDP client
Windows 2000 terminal server does not allow network printer to be redirected. Fortunately, Windows 2003 Terminal server allows it by default. To use this feature, please install and use the Windows Server 2003 Remote Desktop client from the following folder on the terminal server:
drive:\%systemroot%\System32\Clients\Tsclient\Win32.
264039 Windows 2000 Terminal Services does not redirect network printers
http://support.microsoft.com/?id=264039
4. On the terminal server, you must have the corresponding printer drivers installed.
When a client logs on, the Windows 2003-based server checks, the name of the printer driver on the client and looks for the same printer driver name in the Windows 2000 Ntprint.inf file. If the name of the driver is not found, the error messages are logged and the printer is not redirected. So you must have the corresponding printer drivers with the same name installed on the terminal server. For more information, please refer to the following Microsoft Knowledge Base article:
Windows 2000 Terminal Services Server Logs Events 1111, 1105, and 1106
http://support.microsoft.com/default.aspx?scid=kb;EN-US;239088
A new tool for this issue: Terminal Server Printer Driver Redirection Wizard
This tool will examine a remote or local Terminal Server and determine whether or not printer redirection has failed. For each printer driver that failed redirection, the tool will prompt the user to select an installed driver to create a new NTPrintSubs.inf file. This also integrates with a new Windows Server 2003 SP1 Group Policy to address printer redirection issues. This is an automation of the KB article 239088 entitled “Windows 2000 Terminal Services Server Logs Events 1111, 1105, and 1106″.
You can get the tool from:
http://download.microsoft.com/download/9/f/2/9f237742-e057-4e00-a0d5-62de2ebf9fbd/TSPDRW_Package.exe
5. Printer redirection does not work with the DOT4 port printers.
By default, printer port names that do not begin with COM, LPT, or USB are only redirected in Windows Server 2003. By default, multifunction print devices may not be redirected unless you are running Windows Server 2003 on your local computer because they use DOT4 ports. You can take a look at the following URL for more information of this issue:
302361 Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not
http://support.microsoft.com/?id=302361
I hope that the above information can be of assistance. If the problem continues, please collect the following information so that your IT can perform further investigation:
1. What is the model of the problematic printer?
2. Can other printers of other customers be redirected to the terminal server properly?
3. Which port does the problematic printer use?
4. Please perform the following steps to collect the MPSReport of the terminal server:
1) Download the MPSRPT_SETUPPerf.EXE file from the following website:
2) Double-click to run the MPSRPT_SETUPPerf.EXE file and wait for it to complete.
3) Send me the .cab file generated in the following folder: systemroot%\MPSReports\Setup\<Report Type>\Cab
