I want to be able to log into a certain program from Terminal Services across the internet and then print info from that program to a printer on my side. Is it possible and how do you do it?
When you connect to a terminal server you will see the printers on the client machine - the terminal server does need to have apropriate drivers installed and I seem to rember that usb printer won't work?
I just set this up last month.
You need your home printer drivers installed on Terminal Server.
I had the users printer brought in and I hooked it up the the terminal server and installed it (it was a USB printer to, by the way).
Then disconnected it and gave it back to the user.
When he terminaled back in later he had the option to print from his own printer that was attached to his home PC.
Then we got a brand new Termiinal server 3 days ago and he had to bring it back in again.
There might be a quicker better way but I didn't find it.
You don't have to carry printers around, you only need to install the driver on the TS itself. Go to the Printers folder on the TS, then File and Server Properties, Drivers and add the driver for the target printer.
I'm Certifiable, not certified.
It just means my answers are from experience, not a book.
Yeah, I tried that but after (the "have disk",yadayadayada)I pointed it to the .inf file for the printer I was taken to a page that had a box where I had to pick the printer and the box was empty and I couldn't continue.
Having the printer hooked up was the only way for me.
Maybe it was the printer?
HP6100 USB.
I don't know.
Ok, I went over and loaded the driver for the printer in the Printers folder, File, Server Properties, add a printer driver. I did all that. But how do I add a printer that I can't see. I know I can map a drive to a folder share through net share and all that. But how do you do a printer, so that I can print from a program being run on the 2000 Server, and the paper come out on the printer attached to the 2000 pro machine that is using terminal services to connect to it.
I'm just using terminal services to log into the Server itself and running an App on the Server. I want to print and it come out at the location I am dialing in from.
From what i remember, USB printers arent supported
All you should need is the printer drivers on the terminal server and the client logging on should be able to print if that driver is compatible with the local printer
I have had experience however where the standard driver doesnt work via TS, i think i had an issue with a HP laserjet 6 where i used the standard driver and it didnt work. I hunted around the HP website and i used an extended driver which did the job (cant remember the name of it though). It didnt say it had extra features for TS, but it worked non the less.
Test it yourself with a local printer in the office if you can
From experience, when having issues with printer redirection in TS I would -
1) make sure that the latest drivers are downloaded and installed at both client and server end, I've found TS to be quite fussy with different versions
2) install the newest TS client, as printer redirection is much enhanced - I downloaded it from
3) check the System event log on the server for indications of the problem - if there is a problem with driver mappings etc it's normally pretty good at telling you so.
before approaching this. Altho the site is Citrix based not TS centric it offers good advice on stable drivers.
TS printing can be a whole world of pain if not managed correctly. Wherever possible use the unidrv based drivers (ie from drivers.cab on install cd) not the HP ones. In most instances the extra functionality is superfluous.
Rememember - if you enable client printing and do not set default only then all client printers will be mapped. This can have nasty results if you are not aware of all the printers on the client machine. One solution is to install all the printers you plan to allow on a server then use printmig.exe to zip them to a .cab file. You can then replace the drivers.cab and sp*whatever*.cab in C:\WINNTDriver Cache\i386 with this and no rogue printers will be installed.
There are plenty of issues all over Technet concerning TS printer driver issues.
I read this thread with interest as I need to do exactly the same. I have the drivers for a Brother all-in-one (printer, fax etc.), and it has 3 *.inf files, so you can install just the printer drivers, or the scanner ones or all of them.
However, when I do the server properties, add drivers bit, and I select the *.inf file, it should come up with a window showing the printer names that it has found described in the *.inf file so that I can select as necessary and then install.
But in this case, it shows none, which ever *.inf file I select. I am using W2K drivers, since it will be W2K PCs that are printing via terminal services, but I cannot see how to proceed.
I could bring the printer to the server and use plug and play, but I suspect the same may happen.
First I loaded the Lexmark E323 driver on the Terminal Server by going to start, settings, control panel, printers and then selecting file, server properties, add and added the driver. But then I was still having problems because these two computers are on different networks, so I put a batch file in the startup of the server. I ran this and it connected me to the printer. (Something like net use \\192.168.1.66\ipc$ /user:monkey\administrator password
Everytime I log into the terminal server the batch file runs and loads up the printer. I can hit print on anything over there and it comes to me.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.