Printer Not Recognized Using Remote Desktop

[Ron Williams]

Brother MFC 6800 connected via USB not recognized during
Remote Desktop connection. Printer is connected to
client. Cannon inkjet connected to LPT1 is recognized, but
if I connect the Brother to LPT1 with the appropriate
drivers it still is not recognized. Printer port in Win
XP Professional on client begins with USB. Pooling to
LPT1 doesn't help. Registry fix in MS Knowledge Base was
no help. Any ideas?

[Cari \(MS-MVP\)]

Did you install the software BEFORE connecting the USB device?

Cari
www.coribright.com

"Ron Williams" > wrote in message
...
> Brother MFC 6800 connected via USB not recognized during
> Remote Desktop connection. Printer is connected to
> client. Cannon inkjet connected to LPT1 is recognized, but
> if I connect the Brother to LPT1 with the appropriate
> drivers it still is not recognized. Printer port in Win
> XP Professional on client begins with USB. Pooling to
> LPT1 doesn't help. Registry fix in MS Knowledge Base was
> no help. Any ideas?

[Ron Williams]

I've got it to work. Yes, drivers were installed prior to
connecting with USB. Remote Desktop reserved a TSO port
for the printer, just didn't show it as being available. I
installed drivers on host, connected remotely using client
and ran Add Printer Wizard. I added the Brother and chose
the free TSO port and it worked. Why XP set up my inkjet
automatically and not the Brother I don't know. Maybe it
has to do with its multifunction capability. Hope this
helps others with the same problem!

>-----Original Message-----
>Did you install the software BEFORE connecting the USB
device?
>
>Cari
>www.coribright.com
>
>"Ron Williams" > wrote in message
...
>> Brother MFC 6800 connected via USB not recognized during
>> Remote Desktop connection. Printer is connected to
>> client. Cannon inkjet connected to LPT1 is recognized,
but
>> if I connect the Brother to LPT1 with the appropriate
>> drivers it still is not recognized. Printer port in Win
>> XP Professional on client begins with USB. Pooling to
>> LPT1 doesn't help. Registry fix in MS Knowledge Base
was
>> no help. Any ideas?
>
>
>.
>