Link to home
Start Free TrialLog in
Avatar of hatzitha

asked on

Terminal server print problem

Hi everyone

I am using terminal services to connect to a terminal server 2008 to a remote location.
on my LAN I have printers connected on windows XP workstations and windows 7 workstations.
Through the terminal session I have connected the printers by using \\ip address\sharename format (same way to all workstations).
The problem is that on windows7 printers there is lag. A simple print on winxp printer takes 20 secs but on win7 can take 120 secs.
There is a lag even when I open printer properties. On winxp is instant but on win7 can take up to 30 secs.
On printer properties on port tab I notisted, the winxp printer has a port like: \\\hp2200 description:local port but at the win7 printer has port:USB001 description:virtual printer port

I think am missing something simple, please advice
Avatar of tonyperth
Flag of United Kingdom of Great Britain and Northern Ireland image

Is there a reason you are not using the the Terminal Server Easyprint option?  this would pick up the printers form the local machine and you would not need to install them as network printers on the Remote Deksotp Session.

The HP your refering to is probably a network printer. the USB is a dektop attached device which requires routing the print job through a shared pronter on a Win7 pc which adds more handshake time and processing before the file can be printed.

Additionally, if the Win7 Pc is currently being used, you are sharing resource time with the person using it.

Printing to a dedicated network printer is always preferable and normally quicker.

Hope this helps!
If the Windows 7 machines are 64-bit they will be using a surrogate program SPLWOW64.EXE to access 32-bit print drivers (even on the print properties page) - I have seen this be quite slow (even on local printers) compared to using 64-bit software to access the same printers.

You would NOT want to upgrade to 64-bit software to solve this problem, but you could test it by installing 64-bit PDF X-Change and see if it is just as slow.  If you do this test, DO NOT print from the browser as that is 32-bit.
Avatar of hatzitha


The terminal Server Easyprint is not an option because the ERP software doesn't work.

All the printers are USB and connected to workstations I don't have any native network printers.

If they are all HP I would suggest using the universal print driver, which should reduce the amount of clutter i the driver.  Set up a print que locally then add the 64 bit driver and share it to the remote desktop server.
Is there a way to setup a printer to be managed with windows xp compatibility?
AppCompat is not used to shim drivers.

As I mentioned a delay is typical for local 32-bit apps on the 64-bit OS.

Could you please clarify the following:

1) Is the Windows 7 machine 64-bit (RDS Client is ALWAYS 64-bit then)?

2) Is the Application running on RDS 32-bit or 64-bit or do you have the problem with both Application bitnesses?

3) Is Server 2008 64-bit?  (R2 is always 64-bit)

4) Could you test if splwow64.exe is starting by rebooting the Windows 7 machine (or killing any instances of splwow64.exe).  Run your normal slow print test and afterward check the process list for splwow64.exe.

Here are some Post SP1 print fixes for both Win7 and Server 2008.

Please answer the above questions so I can help you :)
1) the windows 7 machine is 64 bit
2) the application running on terminal server is 32bit
3) server is 2008 R2 64bit
4) the splwow64.exe is started on boot. If I stop it and then I connect to server I cannot see my printer inside the terminal session

I cannot see the fixes, is there a missing link?

Avatar of CSI-Windows_com
Flag of United States of America image

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