When you use Remote Desktop Connection or the
Terminal Services Client version 4.0 or 5.0 to connect to another
Windows-based computer from a computer that is not running Windows
Server 2003, your local printers may not be redirected. As a result,
your local printers are not available in the remote desktop or terminal
For example, if your Windows XP-based computer has a multifunction print
device using a DOT4 port, it may not be redirected in a remote desktop
session to a Windows 2000- or Windows Server 2003-based computer.
This problem occurs because the printer port does not
begin with COM, LPT, or USB. By default, printer port names that do not
begin with COM, LPT, or USB are only redirected in Windows Server 2003.
By default, multifunction print devices may not be redirected unless
you are running Windows Server 2003 on your local computer because they
use DOT4 ports.
To resolve this problem on a computer that is not
running Windows Server 2003, force all ports (including DOT4) on the
client computer to be filtered for redirection. To do this, add a DWORD
value named FilterQueueType to
Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF.
Follow these steps, and then quit Registry Editor:
This enables all ports on the client to be redirected.
To work around this problem on a client computer that has a
multifunction print device, change the port that the multifunction print
device uses from DOT4 to an LPT port.
For example, to configure a multifunction print device to use an LPT port on a Windows XP-based computer, follow these steps:
When a multifunction printer is using a standard LPT
port instead of the DOT4 port, it loses its multifunction capabilities,
such as scanning, faxing, or copying. To regain the multifunction
capabilities, the print device must use the DOT4 port.
Alternatively, Microsoft offer an automated tool which can apply this fix for you. It is avalable at: