said by angussf:
Are these printers USB printers on the local workstations that are shared at the server? Can you provide more details on the printer types and where, including port names and types, that they're attached and shared?
This article might help:
Printers that use ports that do not begin with COM, LPT, or USB are not redirected in a remote desktop or a terminal services session
Seen that article many times and a few others in many days of google searching... Very frustrating issue... to which there appears to be no solution. I've seen many other threads (not here) detailing the same problem with no luck on the result.
A potential cause mentioned here:
»forums.msterminalservices.org/Wi ··· 270.html
Quote from thread: "The problem is that when you issue a 'net use' command, you are doing a
redirection at a very low level in the operating system, and therefore this
mapping becomes global. Hence, when one person issues the command things
will work right, but the next person to issue the command will override the
first person's mapping. Windows 2000 didn't do this, as you noticed. I
think Microsoft chose to do things this way to try and force people to rely
on the automatic priner and port mapping that comes with Windows Server 2003,
although unfortunately, manually mapping this in DOS mode are practically
But as for the general setup..
2 locations A and B, though issue was still present when machines were brought to the same location, but not needed since Latency from point A to B is non-existent.
Terminal Server at location A.
Client Machines at location B.
Each client machine has a printer attached via parallel port (LPT1).
Each client has their printer setup to be shared.
Outside of Dos, each machine prints to their own printers just fine on the TS. Dos program is silly hard coded to use LPT1... so a redirection is necessary.