atcomsystems.ca/forum Forums Computers & Programming Computers, Software, Accessories remote desktop printing

The printer I am trying to use is a Brother HL-2140. It is connected to PC A via USB. No other printer icons are present on PC B. I am assuming that the driver is present on PC B, as this printer is listed in the built-in Windows list when I added the printer. Thats the one I used anyways.

The best I can say is the driver just will not work under TS with Vista. You see that often in printers which rely heavily on support programs, such as the HP Photosmart printer. Those never work under TS. That said, you can look into Microsoft's Easy Print. I have not dealt with it myself, and it may only run under 2008 Server but have a look.

Man ffej010, i sure wish you would have done an internet search on what i recommended above; and perhaps you wouldn't have led everybody on this wild goose chase. Not only that you might have solved the problem by now.

I am not sure that this has been a wild goose chase as you call it. I think it is just an issue of this particular printer/driver not working over RDP. I have searched the Internet high and low, trying just about every suggestion mentioned. I even have tried installing the printer locally, as you suggested, to PC B verified print is ok, and then taking printer back to PC A and trying again w/ no luck.

I think I will leave this dead horse lie and attempt another avenue. I do appreciate everyone's time and suggestions.

I am chiming in late on this... sorry.

but for posterity, this is what we do.

I have 5 hotels and a CenRez that Remote into a Property Management System. Obviously I can't load 100 different printers onto the Terminal Server.
I use a program that emulates local printer drivers for each TS Client session...works like a champ.

The problem (and this may have been discussed) is that traditionally, even though the printers are available through the Terminal Server Client, there has to be a translation driver-wise for the Terminal Server to at least pass the job along. That whole process has been jacked since Citrix, which is really all RDP is (even the DOS comands for querying and removing clients is the same.) anyway, the only solid way to get it running is to:

a: Install the drivers on the server for every flavor of windows.

b: Use ScrewDrivers to emulate and pass the drivers to your Terminal Server on a connection by connection basis.

A: sucks
B: doesn't require possibly blowing up your server with dirty drivers for 100 different printers, gives the client the ability to choose what printer they want to use, and requires 0 install on the server.

PM'ing a link if you'd like to 'evaluate' it.

M$ never fixed what really is a bad way to do printing over TS. What they really just needed was a passthrough driver that redirected the printing to the client. PCAnywhere did just that and it worked fine.