Link to home
Start Free TrialLog in
Avatar of cloughs
cloughsFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Printer is slow, when trying to print using remote desktop services

When our client is trying to print using remote desktop services, it takes minutes for the print dialogue to display.  Once it displays the printing process is quick but the time to show the list of printers is a long slow process?
Avatar of Vinicio Guzman
Vinicio Guzman
Flag of United States of America image

Are they using the latest RDC ? is this on Win XP ? 7 ?
Are you using EasyPrint ?
Also make sure the Server has the printer drivers installed.
Avatar of cloughs

ASKER

It's a Windows 7 Enterprise sp1 that they're connecting from, the server that the they're connecting to is Windows server 2008 R2 standard, They are using easy print. the RDC version is 6.2.9200 and the printer is a  Panasonic DP - 2330 ver 2 which is installed on the server.
did you install the optional RDP update for Win 8 compliance, as my Win 7 Pro Sp1 64bit RDP is version 6.1.7601??  RDP client has a setting on the Local Resources tab, make sure the users haven't ticked the Printers box, or their desktop printers will be copied over to their RDP session as well and make cause an issue.

What happens if you install the printer direct to your desktop and try and print, does it hang the same way?

I had a similar issue with users printing from Win 7 Pro 64bit to Xerox devices, it would take 2 - 5 mins for the Xerox driver properties/dialogue window to open.  Happened so long ago i am trying to remember the fix, I'm certain it was a 64 bit issue.

Might be worth checking that the server that has the printer Q loaded, has both 32 & 64 bit drivers loaded, and that they are the latest or global version from Panasonic.  Also that there are no old printers or ports still on the server, as this would increase the timeout.  Windows firewall might also be causing this, but most admins usually disable this while the systems are on the LAN.

Also worth checking the systems having the issue, see if their Bluetooth services are disabled, specifically the Bluetooth Support Service, some systems have worked fine with this issue after its running -- for some odd reason, and even if they don't have BT?
ASKER CERTIFIED SOLUTION
Avatar of joharder
joharder
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial