Question Locked

How to connect local printers while accessing Terminal server through RDP

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello Everyone,

We have terminal server installed on windows 2003 server and all clients are windows xp system.

I am trying to connect my local and network printers while accessing terminal server.but somehow i am not able to see any of my local printers on terminal server.

i have one savin 2015dp pcl printer installed as a network printer in my network.all my printing is done through this printer.

now when i login to terminal server i want to connect my local printers to terminal server but i cannot see any printers in terminal server printer and faxes.

All settings in RDP are set like connect local printers when connection id done.

can any one help me how can i get my local printers connected while i am accessing terminal server?

I am really in desperate trouble.

I need to resolve this issue as soon ass possible.

Thanks in advance for all your help.

Thanks,
Bharat

9 replies

by techrep

Terminal server works with Parallel or Serial printers, not USB or network. I'm guessing the network printer isn't on the same network as the terminal server. To use a network printer (IP), setup your firewall to open port 9100 to the printer, then setup a local printer on the terminal server with the public IP address of the network printer. If you don't have s static IP, you can use dyndns.com (or something simular) and list the dyndns name as the IP address. Your print job will be routed back to the printer directly from the terminal server, bypassing terminal server's print relocation. If you have the capability, you can use PAT (Port Address Translation) to have a nonstandard printing port (like 9101) routed to the standard printer port (9100). This would also be a way to have mutiple IP printers on the same netwwork segment (9101 routes to printer 1, 9102 routes to printer 2, etc.) The TCP/IP port monitor in the printer port setup would changed to 9101 or 9102 so the print job would get routed to the correct printer.

by sue t

You do not have to install the printer on the server but the server must have the printer driver installed before your local pritner will be accessible in Terminal Services. There is an option in server 2003 add printers to just install the driver(s) you need so you do not have to install the actual printer. I am not in front of the server right now to give exact directions so if you can't find the option to install just the driver then install the printer and then delete it. The driver will be installed and you should be good to go.

by david.west

Hi Sue; is the ONLY way to access local printers to load drivers onto the Terminal Server? We are trying to provide teachers, working from home, with a MLE (Managed Learning Environment) via Windows Remote Desktop; they want to use the same software at home as they use in school. It is unrealistic to load the printer drivers from each client-teacher onto the server; there could be hundreds of users with appropriate numbers of printer types. There surely must be another answer?
Hopeful of Harrogate

by shhite

As long as you have the Terminal Services Server set to use the local computer's printers and faxes and the printer that is being used at home is in the menu to add a printer .... The Ts will see that printer. Only when it sees a printer it doesnt know do you come accross the issue of having to install the driver. We have several local printers that we did not have to install drivers to because the TS already "knew" that printer. We have also discovered that if it doesnt know it, it will attempt to do the closest match which sometimes works as well. In our case it uses and hp driver to run on of our toshibas and it does print that way.

The only way to test this is to have your uses log in at home which could very well get messy.

Not sure if this helps.

by p.yamauchi

I found that depending on what version of Server you are using 2000 or 2003 will depend on the amount of Printer support it will provide, to get the best functionality out of a printer that is being used through a TS connection you would have to install the drivers for that printer with administration rights, once this is done as an admin and you can see the printer, when the user logs in they should be able to see and use it as well.

by harishan

Having same issue on TS 2008. Local printers not showing on the list under XP, but under vista in some machines. Puzzles alot.

by john in oz

If this is working for some but not others, the problem isn't on the server. I suspect the RDP Client version might be too old on the older (XP) machines. Needs to be version 6.0 at least, I think.

Click "About" for remote desktop client to check your version - it's under the top left icon on the RDP Client window. Or you could try a Windows Update, which should identify your RDP Client as being too old. (The latter method might not work due to group policy or Windows Update being disabled for some other reason, or if you've previously skipped the RDP Client update).

This discussion is closed to new replies.