WD9 - Printing through Remote Desktop Connection

One of our clients uses our software on their (Win2003) server and let's their clients login via remote desktop connection over a VPN connection. Remote Desktop has a feature so that you can share your local printer in your session on the server, so you can print on it from the server.
Now it seems that not everybody can print. It's not a Vista issue, since both XP clients and Vista clients can print or not print.
All printer drivers are installed on the server (which is necessary to be able to print from the server). From what we have been able to find, is that the printer session queue is not ended correctly or gets stuck.
Have you had any problems with this when printing from WinDev (9) ?

Message forwarded from pcsoft.us.windev

Hi Peter,

You will have far fewer problems if you get your customer to buy Thinprint (or similar).
It is driver independent, does not require that the end user printer driver be installed on the server and also compresses the print job so that it is all much faster. It's about 1000 Euro, but what price can you put on 'no headaches'!!

Cheers

Bosher

Hello Peter

Remote printing in Windows has always been problematic. We had a similar case some years ago and I think we solved it by removing the printer drivers and reinstalling. If it is a USB HP printer then using the Dot4 driver may work better than the USB drivers in some cases.

This article from Microsoft may help
[support.microsoft.com]

This thread has some other ideas
[www.dslreports.com]

As a last resort would it help to try and force the closing of the spool sessions in some way. An IpageEnd inside the report at the very end may help or maybe run a report using Iprint() and IEndPrinting() to push a blank page through after your reports have ended may close the previous session and print it.

Regards
Al

Are these clients all connected to the same server? If so then I don't have any ideas, but if they are to separate servers then you should check the terminal server setting on the server and make sure access to client Printer is turned on.

Good luck,

Hyrum

ps: I hate printers