Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I can't seem to get my printer redirected in Terminal Service mode.

1) I've installed the driver on the Window 2003 server

2) Enabled the "Windows printer mapping" in RDP-TCP properties

But still no printer can be found in my Terminal Session.

Any ideas?

share|improve this question
Look in the System event log on the server after you've logged in to a TS session, there should be several events recorded that should give you some clues. Look for events from sources Print and TermServDevices. – joeqwerty Jul 3 '10 at 14:54
up vote 0 down vote accepted

1) The printer installed on your remote machine and the server are for the same model. Sometimes it helps to use a common "generic' driver (aka HP4 for laser printers that speak PCL)

2) Windows printer mapping should be unchecked for it to be enabled.

On the remote desktop login, go to Options and take a look at the Local Resources tab and make sure Printers is checked.

share|improve this answer
(2) should be unchecked? did u mean checked? – Atlas Jul 3 '10 at 11:41
Unchecked. In the Client Settings Tab the wording is: "Disable the following:" So you check what you want DISabled. By the way. On mine, LPT port mapping, Audio Mapping and COM port mapping are CHECKED. Everything else is UNChecked. And my printers work fine :) – dimitri.p Jul 5 '10 at 12:35

If your printer connected to USB (or network port) try to configure client settings for ports redirection as described here

And make sure you have exactly the same drivers installed on TS as used for local printer you want to redirect to remote session.

share|improve this answer

Open the "server properties" in Printers and Faxes, and check that driver name on your computer and on the remote desktop are EXACTLY the same. If not, your printer won't be redirected because windows won't find the driver - and it will log an error in the system log, from TermServDevices (like someone already pointed out).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.