RDP and TS – problem with printer redirection

Topic

New Reply

I’m unable to get remote desktop clients to a Windows 2003 Server R2 (Terminal Services). I’m aware that in normal circumstances, it is required to install the print driver from the local printer on the server to allow printer redirection to work. Every printer I’ve tried from the remote clients do not have a driver available for Windows 2003 Server, so I tried using enabling the TS fallback driver as described in http://blogs.technet.com/b/askperf/archive/2007/08/24/terminal-server-and-printer-redirection.aspx. I set the option to default to PCL if driver not found. All the remote desktop clients (including myself) have locally connected printers using ports starting with USB*. 1 of the RD clients is running XP, another one is running Win7 Home Premium. I can’t use the advice given in http://support.microsoft.com/?kbid=2028992 since Print Management isn’t available on Win7 home premium or XP.

When I tried printing from RD, it showed my local printer available (via TS PCL Fallback Printer) but nothing happens. Nothing shows in print que. No error message. An event is logged on the TS that printing was successful.

On my printers, nothing happens. Nothing shows in print que. No error message. An event is logged that printing was successful.
– Tried steps from http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q268065
– TSCC.MSC already showed that Windows Printer Mapping and LPT Port Mapping was enabled (unchecked).
– added fEnablePrintRDR key with value of 1 to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWdsrdpwd

Reply | Quote

Replies

Unfortunately TS printing is one of the biggest pains in regard to Terminal Services and Citrix XenApp. In either case, it almost always boils down to issues with drivers. Lots of drivers are simply not compatible with Terminal Services. Stick with Windows native drivers whenever possible. Using third party drivers is usually trouble.

What make and models of printers? Maybe I can help you sort this out. You’ll want to look at the “common denominator” drivers, that is older drivers that have a wide range of compatibility. For example, I use an HP LaserJet 4000 Series PCL driver for HP 2300 printers. We’ve had issues with the 2300 drivers on Terminal Services. The HP LaserJet 4 driver is compatible with many non-HP printers. That’s because most modern business class laser printers have their roots in the old Canon print engine and HP software. Still, determining what print driver will work is TS is more trial and error than anything else. I spend many hours, perhaps over 100 hours, cleaning up the TS printing environment where I work.

Reply | Quote

The TS Fallback Driver is provided by Windows Server 2003 with SP1, so it isn’t a third party driver (or is it?). TS Fallback Driver uses HP Deskjet 500 driver emulation by default. I read in another forum posting that changing the default to an HP 550C driver helped solve someone’s redirection problem, so I tried it. To change that default to HP Deskjet 550C, I tried putting in the driver by adding the registry entry HKLMSystemCurrentControlSetControlTerminal ServerWdsrpdwd, adding FallbackPclDriver and FallbackPsDriver keys and setting them for the HP Deskjet 550C. Didn’t help a bit, although instead of getting no entries in the print que on the RD client using an HP Officejet 5600, they got an entry in the print que showing ‘error’.

To answer your question, one RD client (me) is using a Canon Pixma MP530 and a Samsung Universal Print Driver (ML-1740). Another client (this is the client that needs RD and print redirection to work the most) uses an HP Officejet 5600. I looked up a document on HP’s website and there was a listing of which printers were compatible with Citrix XenApp (TS): http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA0-8465ENW.pdf. The 5600 is listed in the table as not supported in the TS environment and that table, it shows PCL, PS and Host-based drivers as N/A. According to that document, any printer based on the LIDIL printer language are not supported.

According to that HP document, your 2300 printer has PCL language support, so that’s probably why you were able to use another HP print driver to work (since it also has PCL support). Since the HP Officejet 5600 (and many HP consumer-class printers) only utilize the LIDIL printer language and don’t have PCL support, does that mean that I’m SOL in getting it to work with TS?

Reply | Quote

Ouch. Yes, Inkjet printers are the least compatible with TS. They are not truly business class, so are not well supported in that environment. I don’t think your issue is with printer redirection. The fact that the printer is available in your app tells me that it is auto creating just fine. The drivers don’t match and are incompatible, that’s why your print jobs go into “never never land”. Your best bet is to look at a 3rd party universal driver made for Terminal Services. Thin Print and Screwdrivers are two of the more well know solutions. I’ve used Screwdrivers and not only is it an excellent product, they have excellent tech support. What these products do is drop a truly universal driver on the server that can emulate just about everything under the sun. Citrix makes it easy, since 4.x or Presentation Server/XenApp, the Citrix Universal print driver works with pretty much anything. I used to print at home with a Canon i2600 without a hitch. I suspect that adding XenApp may not be cost effective for you. Short of that, you may need to look at buying compatible printers.

Also, did you check you event logs on the server? The application log may give you a clue as to where your jobs are going. It may not, but its worth a look. Does the print spooler on the server crash? If so, check the System log also.

Reply | Quote

I figured that it was down to using a 3rd party universal print driver. I had looked into 2 of them: http://www.terminalworks.com/tsprint.php and http://www.elusiva.com/products/UniversalPrinter, but I’ll check out the 2 links you included. The event log on the server had indicated that printing was successful.

Thanks for your help.

Reply | Quote

We also had same problem and then we found few commercial solutions: http://www.tricerat.com/ – good but to expensive and another one at http://terminalworks.com/ – low price but works great. hope it helps

Reply | Quote