We had the same problem and I found this fix on Microsoft's website:

KB article #302361:

RESOLUTION
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
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server
Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF.

Follow these steps, and then quit Registry Editor: 1. Click Start, click
Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server
Client\Default\AddIns\RDPDR
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type FilterQueueType, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type FFFFFFFF, and then click OK.
This enables all ports on the client to be redirected.



"ABeckCPA" wrote:

> Many terminal server users have multifunction printers at their homes. When
> the user logs into the terminal server they have RDC setup so that their
> local printers are automatically connected. Unfortunately, our terminal
> server won't recognize the multifunction printers. Typically, the printer
> vendor won't have non-multifunction printer drivers for these printers. Is
> there a workaround or fix?
>
> Thanks for your help