E
EoinC
I've read every post I can find on this topic, and I have succeeded in
getting local and network printers (including a HP 3320 all-in-one)
for remote desktop clients working across a VPN using Win2K Server
terminal services. The tips that helped me were:
Don't use the old Terminal Services client - download the Remote
Desktop client instead
Install the same print driver on both client and server
If the printer is an all-in-one device, you need to make a registry
change on the client, and reboot (see Printers That Use Ports That Do
Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop
or Terminal Services Session
http://support.microsoft.com/?kbid=302361)
However, I still have just one all-in-one printer, a HP PSC 950, that
won't work properly. It prints a test page locally, and it is
auto-created in the user's remote desktop, but it only prints a blank
page. The result is the same whether the client is Win2K or WinXP.
Any suggestions?
EoinC
getting local and network printers (including a HP 3320 all-in-one)
for remote desktop clients working across a VPN using Win2K Server
terminal services. The tips that helped me were:
Don't use the old Terminal Services client - download the Remote
Desktop client instead
Install the same print driver on both client and server
If the printer is an all-in-one device, you need to make a registry
change on the client, and reboot (see Printers That Use Ports That Do
Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop
or Terminal Services Session
http://support.microsoft.com/?kbid=302361)
However, I still have just one all-in-one printer, a HP PSC 950, that
won't work properly. It prints a test page locally, and it is
auto-created in the user's remote desktop, but it only prints a blank
page. The result is the same whether the client is Win2K or WinXP.
Any suggestions?
EoinC