Hi Russell,

in order to print on the clients printers you need to install the same driver in the host (server) machine. As you are running a 64 bit server, you may not find the matching drivers for the server, so you need to do a "mapping", i.e. install a compatible driver in the server (not in the client) and tell the server to use this compatible driver when the user tries to map a certain printer.
This is done via a mapping file, and you have instructions in this page:
http://www.msterminalservices.org/articles/Windows-Terminal-Services-Printing.html

Once you do the mapping, you only have to test for the driver that works. Try with the "HP LaserJet 4", or you can try with HP Universal drivers:
http://h20338.www2.hp.com/hpsub/cache/343033-0-0-225-121.html?jumpid=ex_r2845_go/universalprintdriver

The HP Universal Driver at first sight seems like the holy grail for printing in remote desktops in HP printers, but be warned that they do not work with many HP printers. Try them, but they are not as universal as HP says.

If all of this fails, then try some 3rd partu printing solutions for terminal services, like Uniprint, Tricerat, o Thinprint, but these solutions are in the range of 1.000-1.500 US dolars per server.

>I have a client that I'm moving to Terminal Services. It's a 64-bit box running Win2K3 64 bit and the application is done in VFP 9 SP 1. We're having some crashes that seem to be related to printing. As many of us know, printer drives used to sometimes play havoc with VFP, but mostly those problems have been fixed. But in this environment we may be encountering the same problems. The printers in use are HP 2420's. We are using the HP LaserJet 5000 Series PCL 6 driver because - and I'm a little sketchy on this - the native drivers are compatible with Terminal Services, I think. Also, these are USB printers and I believe Terminal Services really wants something hung on LPT1. So you can make these work using a different driver, but this may be the cause of the crashes.
>
>I'm looking for some advice from anyone with experience running a VFP app on Terminal Services and how you get printing to work. The user needs to be able to print to the printer from a desktop app and the app running via Terminal Services. I think this was part of the issue, according to the network guys.
>
>What the user sees is what I call the "grey screen of death" - the entire terminal window is grey, but they can still see the tab at the top that has the server's IP address, the close button, etc. I believe they then have trouble getting that to close and getting logged back in. What I see on the server is a error dialog that say the program experienced an error and had to close and it has the buttons for sending (or not) the error report to Microsoft.
>
>So . . . any ideas or thoughts or best practices or whatever would be appreciated.
>
>Russell Campbell