cancel
Showing results for 
Search instead for 
Did you mean: 

Client PC Remote Desktop Printer Was Not Mapped When Connected To Remote Terminal Server

KSChung_
Not applicable

Client PC Remote Desktop Printer Was Not Mapped When Connected To Remote Terminal Server

Hi,

I'm having client PC printing problem when connected to remote Microsoft Terminal Server, although the client PC have the "mapped printer" option enabled, but no printer was mapped when they connected to remote Terminal Server using Netscreen Remote dial-up VPN(Using Netscreen Remote v10.8.3) .

The client PC can PING and run the applications in Terminal Server as normal.

The cilent PC printer was mapped as normal in the Terminal Server when running in Local Area Network(LAN)

Currently, The Netscreen SSG5 firewall policy permits RDP 3389 port traffics.

Can someone help me to solve this issue?

Thanks in advance.

Best regards,

KS Chung

4 REPLIES 4
irtizas_
Occasional Contributor

Re: Client PC Remote Desktop Printer Was Not Mapped When Connected To Remote Terminal Server

I have got the same problem with one of my customers.

When using terminal services and with the map local printers setting ticked, USB printers are not showing as mapped in the terminal services session.

Can someone please confirm advise on this?

sk_
Contributor

Re: Client PC Remote Desktop Printer Was Not Mapped When Connected To Remote Terminal Server

had the same problem... we had a USB printer connected to a laptop that was RDP'ing in to a desktop.... the user could not print to her usb printer from her rdp desktop until I installed the printer manually on her desktop as well

dfry_
Occasional Contributor

Re: Client PC Remote Desktop Printer Was Not Mapped When Connected To Remote Terminal Server

This is a known bug per Microsoft.

http://support.microsoft.com/kb/302361

dfry_
Occasional Contributor

Re: Client PC Remote Desktop Printer Was Not Mapped When Connected To Remote Terminal Server

I'm also having a printing problem using RDP. In my case, the local printer shows when using a 2003 Terminal Server, but not when I connect to a regular XP desktop. Anybody have the same issue?