Printer Doesn't Map In Terminal Services

Hi Experts.  I have a customer with a SBS 2003 Premium server and about 10 remote clients.  They connect to this server via Terminal Services to get to a specific application.  Everyone maps to their local printer with no problems...except for one user.  This particular user has an HP Color LaserJet 2605dn.  I installed the driver on the SBS TS, but the printer won't show up.  The odd thing is that every other printer this user has (Adobe PDF, a local fax server, etc.) shows up in the Event Viewer as failing to find a driver (this is expected since I purposely haven't loaded drivers for them).   But, there's no Event Viewer entry for the 2605dn printer.  Since it's trying the other printers the user has, it would seem that everything is set up correctly as far as local resources in the mstsc client, the rights within the user ID, and in TS itself.  I know the driver matches because it was loaded off the same disk and the names match exactly.  And, since there's no entry for this printer in the Event Viewer, I don't think it's a driver issue at all.  Is there something I need check in the driver locally?  I can't imagine what, though.  Any one have any ideas?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You need to add a registry tweak

[HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR]

I'll find the KB in a sec...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
breichardAuthor Commented:
On the server or on the client?
Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session (
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Sorry!  The tweak needs to be done on the client.
You can either create a .reg file and import it or run:

REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR" /v "FilterQueueType" /t REG_DWORD /d 0xffffffff
No No the tweak needs to be done on the server.  The server is what allows or disallows the redirection of printers from clients.
To allow all redirection or any type or printer setup you need to follow the MS article given a few posts above but you do it on the server.

1. Click Start, Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR  
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type FilterQueueType, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type FFFFFFFF, and then click OK.

This enables all ports on the client to be redirected
breichardAuthor Commented:
Would it hurt to just do it on both the client and the server?
There is no need to do it on the client the client isnt responsible for the printer redirection the server is.
All your doing by running this tweak is telling the server to allow all type of printer connections from clients.  tcpip ports/usb/lpt1/ect
ryansoto  Are you sure?

To resolve this problem on a computer that is not running Windows Server 2003, force all ports (including DOT4) on the client computer to be filtered for redirection. To do this, add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF.

To me that reads that it is the client that is filtering the ports.
And if you add the key to the client it suddenly starts to work... (well you might need to log off and then back in again)
Positive I had the same issue a few weeks ago.  When my users were logging into the server their printers wouldnt work.  The printer that wouldnt work was a printer using a tcpip port.  By default windows 2003 doesnt redirect all ports such as tcpip.  The change needs to be made on the server.  Positive.

To test you could definately change that value on the client and test.
☠ MASQ ☠Commented:
Add it to both - it won't do any harm - but the theory is it allows the CLIENT to redirect - the registry fix changes the RDC settings so when "Share printers" is ticked in the remote desktop options more than the basic range of ports are shown to the terminal server.
You run it on the client

But have you checked your logs on the server?  Make sure you are not missing the driver on the server.  You will see an error in event logs that states the print driver is missing.  To add it go to printer and faxes on the server.  Go to file    server properties.  Then select the driver tab and install the driver.

Optionally if you do not see an error change the port to Parallel on the client if it connects via parallel.  If USB run the above script.

Either solution works but you may lose some capability if you change the port to parallel.  In my experience the port change has worked without issue.  You right click on printer. Select properties.  Go to Ports and change it to parallel and print a test page.  If it works you are off  (Assuming it is a parallel printer of course)

Do not run on server
breichardAuthor Commented:
I hope to get this tested early this week.  I will let you know about server vs. client.

dcohn, yes, as I stated in the first post, the driver is there and every other printer is redirecting (but failing because none of their drivers are loaded...on purpose).  Just the one we actually want isn't showing up...or erroring in the event viewer.
breichardAuthor Commented:
Putting this entry on the client solved the issue.  Thanks!
lamaslany   Thank you for that one liner Reg ADD by the way.  

Much simpler than instructing users to make a registry change.

I had a tech at a very large corporate office tell me the only solution he could find was to directly map the local printers to the remote terminal server
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Printers and Scanners

From novice to tech pro — start learning today.