R
Rod
I am using Windows XP Professional. I have an HP Officejet 7410 locally. I
use remote desktop 5.2 to connect to another remote Windows XP Professional
desktop. When establishing the connection, I choose to connect the local
resource "printers" so that I can print from my remote desktop session to
the printer in my local printer. However, the remote desktop session cannot
"see" my Officejet printer.
In the application log of the remote desktop, it complains about not having
the proper driver for the Officejet. At the remote computer, I downloaded
the drivers for the printer and installed them (and since rebooted) but it
will still not see the printer.
I found a Microsoft Q article #302361 which seemed to address the problem
and I implemented the registry change that it suggested but it still does
not work.
I have tried hooking this printer up through a network connection and then
tried using a USB connection but both connections perform the same way when
connected to remote desktop.
I contacted HP and was told that my scenario was not supported but I feel
that there has to be some sort of workaround for this issue.
If anyone has any ideas on this, I would appreciate it.
Thanks,
Rod
use remote desktop 5.2 to connect to another remote Windows XP Professional
desktop. When establishing the connection, I choose to connect the local
resource "printers" so that I can print from my remote desktop session to
the printer in my local printer. However, the remote desktop session cannot
"see" my Officejet printer.
In the application log of the remote desktop, it complains about not having
the proper driver for the Officejet. At the remote computer, I downloaded
the drivers for the printer and installed them (and since rebooted) but it
will still not see the printer.
I found a Microsoft Q article #302361 which seemed to address the problem
and I implemented the registry change that it suggested but it still does
not work.
I have tried hooking this printer up through a network connection and then
tried using a USB connection but both connections perform the same way when
connected to remote desktop.
I contacted HP and was told that my scenario was not supported but I feel
that there has to be some sort of workaround for this issue.
If anyone has any ideas on this, I would appreciate it.
Thanks,
Rod