Remote Desktop client does not map client printers

[jacksondorado]

On certain Windows XP desktops, I log onto a terminal server and my printers don't appear, even though I have checked "Printers" as a resource.

Does anyone know how to upgrade the Remote Desktop Client? I try to install the latest version but the error tells me that I already have a built-in version.

 

[markdmac]

that is most likely not your issue.

In order for Printers to be properly redirected, the server needs to have the print drivers loaded for those same printers. have you verified if this is the case? You will see in the Applicaiton Logs a bunch of errors registered to Terminal Services if this is the case.

Another source of troubles is if the printers in question are either network or USB printers. To resolve issues with printing to these kind of printers, run the following VB Script on the workstation BEFORE connecting to Terminal Services. (You only have to run it once PER USER).

One final issue, All In One printers will never work with Terminal Services as they require print software rather than a print driver to connect to.

'==========================================================================
'
' NAME: TSPrintFix.vbs
'
' AUTHOR: Mark D. MacLachlan , The Spider's Parlor
' URL: [URL unfurl="true"]http://www.thespidersparlor.com[/URL]
' (c) 2003 All Rights Reserved
' DATE  : 12/22/2003
'
' COMMENT: Fixes printing via terminal services to allow DOT4 printers
'
'==========================================================================
myPrompt = MsgBox("This script will set up your printers for use with Terminal Services",vbOKCancel,"Setup Printers for Terminal Services?")
If myPrompt = 1 Then 
	Set WshShell=WScript.CreateObject("WScript.Shell")
	keypath ="HKCU\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR\FilterQueueType"
	WshShell.RegWrite keypath, -1, "REG_DWORD"
	If WshShell.RegRead(keypath) = "-1" Then
		MsgBox "Setup was successful",,"Success"
	Else
		MsgBox "Sorry A Problem Was Encountered" & vbCrLf & "Make sure you have permission to write to the registry.",,"Something went wrong"
	End If	
End If
WScript.Quit

The latest copy of the RDP client is available for download at microsoft.com.

http://www.microsoft.com/downloads/...21-d48d-426e-96c2-08aa2bd23a49&DisplayLang=en

I hope you find this post helpful.

Regards,

Mark

 

[jacksondorado]

Thanks. I forgot to mention that other computers print using the same printers. They are networked printers but the other computers have no problem printing.

Another indicator that it is a problem with the Remote Desktop version is that when I connect using the Internet Explorer Web Client, the printers load and print just fine.

I wonder if I can uninstall the current RDP or install the new one parallel to it.

 

[jacksondorado]

I solved my problem and figured I would post the solution here for anyone else that has the problem.

It appears that with an XP computer with an older version of RDP, network printers are not mapped to the Terminal Server Session. there is a registry fix to allow all printer port names to be mapped. I followed the article instructions and the laserjet 1300 with a jetdirect 200m printserver prints from the TS session fine now.

The article can be found here,

http://support.microsoft.com/kb/Q264039

Good luck