Unable to Print Locally on terminal Server

I have a Terminal server running Win2k3 SP2 Standard.  I need to enable remote clients to print on their local printers from the TS.  The TS looks to be setup to allow client print mapping.  I have also added the print drivers for all the printers I need under the Printer Server properties.

The clients are using RDC 6.0 which I believe is the most recent, and printers are enabled under local resources so I don't think it has anything to do with the client side.  One thing I am unsure of however is that within my Terminal Services Config utility under the "Connections" folder I have one connection of type "Microsoft RDP 5.2"  I tried to create a new connection hoping for a more recent version but 5.2 is my only option.  Not sure if that has something to do with it.  Windows updates don't show anything available here.  Any help is much appreciated
Who is Participating?
lamaslanyConnect With a Mentor Commented:
Ugrading the Remote Desktop Connection client does affect the server components of Remote Desktop.

The server-side connection versions are:

Microsoft RDP 6.1 (Windows Server 2008)
Microsoft RDP 6.0 (Windows Vista)
Microsoft RDP 5.2 (Windows Server 2003)

The latest Remote Desktop Connection clients are:

RDC 6.1 (Windows Vista SP1, Windows XP SP3, Windows XP SP2 with KB952155, Windows Server 2008)
RDC 6.0 (Windows XP x64 with KB925876)

With regards your specific issue robstacey is correct - the Windows logs are a good place to start.  To assist you might want to look at Microsoft's Terminal Server Printer Redirection Wizard Tool:  http://www.microsoft.com/downloads/details.aspx?FamilyId=9AD27BE9-40DB-484F-862E-38A094EEEAF7&displaylang=en

A few other things to note:

* ensure that the client has elected to re-direct their printers
* ensure that the same driver version is used on the client and server
* if the client printer doesn't use a COM, LTP or USB port type you need to tweak the client registry (http://support.microsoft.com/kb/302361)
robstaceyConnect With a Mentor Commented:
If you check the event log on your Terminal Servers you may find a whole bunch of errors where it says that it can't create client side printers.  I think you have to make sure that the printer drivers are installed on the terminal server for the models that your clients have. They don't need to be configured to each device, the driver files just need to exist and be registered.  We have this kind of thing here and the event logs fill up if the drivers on the pCs don't match the drivers installed on the server.
fishizzaAuthor Commented:
Thanks for the tips.  I think it is along the way of drivers.  I was able to get some of the printers to show but not all the ones needed yet so I have been able to make some progress.  Perhaps that registry tweak is my answer as the printers not showing up right now on configured on the client LAN using standard TCP/IP ports.  I'll give that a try
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

fishizzaAuthor Commented:
Looking good now, thanks!
Thanks for the feedback.

I just have one minor correction to my last post just in case anyone else reads this looking for advice:

Ugrading the Remote Desktop Connection client does affect the server components of Remote Desktop.

should read:

Ugrading the Remote Desktop Connection client does *NOT* affect the server components of Remote Desktop.

No worries, glad I was able to assist.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.