You need to do two things to make this work, assuming that your
Brother printer driver software is TS-compatible:

1.) Use Remote Desktop Client version 5.2.3790.0 or later on
your office PC.

- Version 5.2.3790.x can be found on a 2003 server in the
following folder:

C:\WINDOWS\system32\clients\tsclient\win32\

- You can download version 6.0.6000.16386 here:

http://www.microsoft.com/downloads/d...f-d4f18c8f5df9

2.) Install the Brother printer driver software on your home PC.
You can do this by "pretending" that the Brother is attached to the
computer and running through the Add Printer wizard, making sure
to uncheck "Automatically detect and install my Plug and Play Printer".
Do *not* print a test page, this is unnecessary and will not work.
Also, the local port you select is irrelevent, so simply choose the
default LPT1.

After you have successfully completed the wizard, delete the
Brother printer you just installed--the necessary driver software
will remain.

Next time you connect to your home PC from your Office PC, your
Brother printer will automatically show up as an option. It will be
named something similar to "Brother HL-2040 (from COMPUTER)".

The technique GTS describes (sharing, pooling, etc.) was a
workaround for an older version of the client, but has not been
necessary for years.

-TP

cfman wrote:
> HI all,
>
> I installed a Brother printer in office(hereafter I call PC O), and
> now I am remotely connecting back to my home(hereafter I call it PC
> H).
>
> On PC O, the printer was installed in a local LAN peer-to-peer
> printing mode, using LPR protocol.
>
> The remote desktop does not recognize this printer at all - on the PC
> H, when I want to print, actually I want it to print to this Brother
> printer on PC O. But it never had this option in the scroll-down list
> of the printer list.
>
> Is there a way I can let the remote PC H know that it should print
> via PC O to the Brother printer in my office?
>
> What's wrong with remote desktop?
>
> Do I need to install a virtual network printer on PC H, in order to
> use it to print to Brother printer in office? Since it was installed
> as peer-to-peer printing using LPR protocol, I am not sure how to
> install a printer driver on PC H for this Brother printer in my
> office...
>
> Any ideas?
>
> Thanks a lot

You're information is incorrect. What you describe is how RD printing works
if the printer is attached to the PC. cfm has a printer connected as an
Ethernet node. There is no need for the newer client, and the printer
pooling method is required to route the print traffic through the local
network.
--

"TP" <tperson.knowspamn@mailandnews.com> wrote in message
news:%23N91lkpFHHA.3780@TK2MSFTNGP02.phx.gbl...
> You need to do two things to make this work, assuming that your Brother
> printer driver software is TS-compatible:
>
> 1.) Use Remote Desktop Client version 5.2.3790.0 or later on your office
> PC.
>
> - Version 5.2.3790.x can be found on a 2003 server in the following
> folder:
>
> C:\WINDOWS\system32\clients\tsclient\win32\
>
> - You can download version 6.0.6000.16386 here:
>
> http://www.microsoft.com/downloads/d...f-d4f18c8f5df9
>
> 2.) Install the Brother printer driver software on your home PC. You can
> do this by "pretending" that the Brother is attached to the computer and
> running through the Add Printer wizard, making sure to uncheck
> "Automatically detect and install my Plug and Play Printer".
> Do *not* print a test page, this is unnecessary and will not work.
> Also, the local port you select is irrelevent, so simply choose the
> default LPT1.
> After you have successfully completed the wizard, delete the Brother
> printer you just installed--the necessary driver software will remain.
>
> Next time you connect to your home PC from your Office PC, your Brother
> printer will automatically show up as an option. It will be named
> something similar to "Brother HL-2040 (from COMPUTER)".
>
> The technique GTS describes (sharing, pooling, etc.) was a workaround for
> an older version of the client, but has not been necessary for years.
>
> -TP
>
> cfman wrote:
>> HI all,
>>
>> I installed a Brother printer in office(hereafter I call PC O), and
>> now I am remotely connecting back to my home(hereafter I call it PC
>> H). On PC O, the printer was installed in a local LAN peer-to-peer
>> printing mode, using LPR protocol.
>>
>> The remote desktop does not recognize this printer at all - on the PC
>> H, when I want to print, actually I want it to print to this Brother
>> printer on PC O. But it never had this option in the scroll-down list
>> of the printer list.
>>
>> Is there a way I can let the remote PC H know that it should print
>> via PC O to the Brother printer in my office?
>>
>> What's wrong with remote desktop?
>>
>> Do I need to install a virtual network printer on PC H, in order to
>> use it to print to Brother printer in office? Since it was installed
>> as peer-to-peer printing using LPR protocol, I am not sure how to
>> install a printer driver on PC H for this Brother printer in my
>> office... Any ideas?
>>
>> Thanks a lot

You're information is incorrect. What you describe is how RD printing works
if the printer is attached to the PC. cfm has a printer connected as an
Ethernet node. There is no need for the newer client, and the printer
pooling method is required to route the print traffic through the local
network.
--

"TP" <tperson.knowspamn@mailandnews.com> wrote in message
news:%23N91lkpFHHA.3780@TK2MSFTNGP02.phx.gbl...
> You need to do two things to make this work, assuming that your Brother
> printer driver software is TS-compatible:
>
> 1.) Use Remote Desktop Client version 5.2.3790.0 or later on your office
> PC.
>
> - Version 5.2.3790.x can be found on a 2003 server in the following
> folder:
>
> C:\WINDOWS\system32\clients\tsclient\win32\
>
> - You can download version 6.0.6000.16386 here:
>
> http://www.microsoft.com/downloads/d...f-d4f18c8f5df9
>
> 2.) Install the Brother printer driver software on your home PC. You can
> do this by "pretending" that the Brother is attached to the computer and
> running through the Add Printer wizard, making sure to uncheck
> "Automatically detect and install my Plug and Play Printer".
> Do *not* print a test page, this is unnecessary and will not work.
> Also, the local port you select is irrelevent, so simply choose the
> default LPT1.
> After you have successfully completed the wizard, delete the Brother
> printer you just installed--the necessary driver software will remain.
>
> Next time you connect to your home PC from your Office PC, your Brother
> printer will automatically show up as an option. It will be named
> something similar to "Brother HL-2040 (from COMPUTER)".
>
> The technique GTS describes (sharing, pooling, etc.) was a workaround for
> an older version of the client, but has not been necessary for years.
>
> -TP
>
> cfman wrote:
>> HI all,
>>
>> I installed a Brother printer in office(hereafter I call PC O), and
>> now I am remotely connecting back to my home(hereafter I call it PC
>> H). On PC O, the printer was installed in a local LAN peer-to-peer
>> printing mode, using LPR protocol.
>>
>> The remote desktop does not recognize this printer at all - on the PC
>> H, when I want to print, actually I want it to print to this Brother
>> printer on PC O. But it never had this option in the scroll-down list
>> of the printer list.
>>
>> Is there a way I can let the remote PC H know that it should print
>> via PC O to the Brother printer in my office?
>>
>> What's wrong with remote desktop?
>>
>> Do I need to install a virtual network printer on PC H, in order to
>> use it to print to Brother printer in office? Since it was installed
>> as peer-to-peer printing using LPR protocol, I am not sure how to
>> install a printer driver on PC H for this Brother printer in my
>> office... Any ideas?
>>
>> Thanks a lot

What I said is correct, and will achieve the desired result. The
newer client version is not *required*, however. I recommended
it because using the newer version will be less brittle than making
the required registry change. This is because the registry change
is per user, so when another user logs on they will also need to
make the same change.

Your method suffers from the same problem (brittle) as the registry
change--each unique user will have to perform the net use lptx
in order to make printing work. In addition, you are unnecessarily
requiring that the printer be shared. Printer sharing is there so
that someone else on the network can print to the printer, not as
a method to facilitate printer auto creation on the remote PC.

What happens when there are several ip printers? Would you
have them continue to use net use until they run out of LPT ports?

Years ago, the technique you describe was created to work
around a specific limitation of the Terminal Services Client. That
is, the client did not support redirection of network printers.
Note, I am referring to network printers here, not printers that
are installed locally with an IP port, like in the poster's
situation. This workaround was rendered unnecessary when
the 5.1.x.x version of the client shipped (w/XP).

Windows 2000 Terminal Services does not redirect network printers

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

Now, many TS techs knew of the above workaround, and applied
it to solve the issue the original poster has: by default, versions
5.0.x.x and 5.1.x.x of the client only attempt to redirect local
printers attached to ports that begin with LPT, COM, or USB.
This behavior can be changed by adding a registry value, but at
the time *most* were unaware of this. Then this article helped:

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/kb/302361

Newer client versions 5.2.x.x/6.0.x.x default to the ANY local
port name behavior, but can be changed to the old behavior by
registry setting. This change in default is why I recommend them
to solve this particular issue.

-TP

GTS wrote:
> You're information is incorrect. What you describe is how RD
> printing works if the printer is attached to the PC. cfm has a
> printer connected as an Ethernet node. There is no need for the
> newer client, and the printer pooling method is required to route the
> print traffic through the local network.
>

What I said is correct, and will achieve the desired result. The
newer client version is not *required*, however. I recommended
it because using the newer version will be less brittle than making
the required registry change. This is because the registry change
is per user, so when another user logs on they will also need to
make the same change.

Your method suffers from the same problem (brittle) as the registry
change--each unique user will have to perform the net use lptx
in order to make printing work. In addition, you are unnecessarily
requiring that the printer be shared. Printer sharing is there so
that someone else on the network can print to the printer, not as
a method to facilitate printer auto creation on the remote PC.

What happens when there are several ip printers? Would you
have them continue to use net use until they run out of LPT ports?

Years ago, the technique you describe was created to work
around a specific limitation of the Terminal Services Client. That
is, the client did not support redirection of network printers.
Note, I am referring to network printers here, not printers that
are installed locally with an IP port, like in the poster's
situation. This workaround was rendered unnecessary when
the 5.1.x.x version of the client shipped (w/XP).

Windows 2000 Terminal Services does not redirect network printers

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

Now, many TS techs knew of the above workaround, and applied
it to solve the issue the original poster has: by default, versions
5.0.x.x and 5.1.x.x of the client only attempt to redirect local
printers attached to ports that begin with LPT, COM, or USB.
This behavior can be changed by adding a registry value, but at
the time *most* were unaware of this. Then this article helped:

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/kb/302361

Newer client versions 5.2.x.x/6.0.x.x default to the ANY local
port name behavior, but can be changed to the old behavior by
registry setting. This change in default is why I recommend them
to solve this particular issue.

-TP

GTS wrote:
> You're information is incorrect. What you describe is how RD
> printing works if the printer is attached to the PC. cfm has a
> printer connected as an Ethernet node. There is no need for the
> newer client, and the printer pooling method is required to route the
> print traffic through the local network.
>

"TP" <tperson.knowspamn@mailandnews.com> wrote in message
news:%23N91lkpFHHA.3780@TK2MSFTNGP02.phx.gbl...
> You need to do two things to make this work, assuming that your Brother
> printer driver software is TS-compatible:
>
> 1.) Use Remote Desktop Client version 5.2.3790.0 or later on your office
> PC.
>
> - Version 5.2.3790.x can be found on a 2003 server in the following
> folder:
>
> C:\WINDOWS\system32\clients\tsclient\win32\
>
> - You can download version 6.0.6000.16386 here:
>
> http://www.microsoft.com/downloads/d...f-d4f18c8f5df9
>
> 2.) Install the Brother printer driver software on your home PC. You can
> do this by "pretending" that the Brother is attached to the computer and
> running through the Add Printer wizard, making sure to uncheck
> "Automatically detect and install my Plug and Play Printer".
> Do *not* print a test page, this is unnecessary and will not work.
> Also, the local port you select is irrelevent, so simply choose the
> default LPT1.
> After you have successfully completed the wizard, delete the Brother
> printer you just installed--the necessary driver software will remain.
>
> Next time you connect to your home PC from your Office PC, your Brother
> printer will automatically show up as an option. It will be named
> something similar to "Brother HL-2040 (from COMPUTER)".
>
> The technique GTS describes (sharing, pooling, etc.) was a workaround for
> an older version of the client, but has not been necessary for years.
>
> -TP
>


It worked! Thank you so much TP.

As a greenhand in these stuffs, I chose the easiest way, so I downloaded the
new client. I didn't know there was one. I saw the release date was
11/28/2006, just a few days ago.

The new client worked. Learning from TP and GTS' discussion, I learned that
it was the default behavior of the new client to redirect all local printers
that helped. Yes, I noticed that the initial connection to the PC H was
actually slower than the old client -- the reason is that it is redirecting
a lot of printers connections, etc. I can sense that out, for the initial 30
seconds, there are a lot of chaos going on; but after 30 seconds, all my
printer can now be accessed from PC H.

One thing to note is that if I just install the driver from the CD on PC H,
it did not work;

But if I use the Setup Wizard to install everything from the CD on PC H, and
then delete the installed printer, then it worked;

So indeed the Setup Wizard has done a lot hidden things, in addition to
install the driver itself.

I am sure with this trick of using Setup Wizard then delete, GTS's method
will also work.

Thank you both for your expertise and excellent suggestions. This solves my
headache which lasted for one year.

I appreciate your great help!

MIke

"TP" <tperson.knowspamn@mailandnews.com> wrote in message
news:%23N91lkpFHHA.3780@TK2MSFTNGP02.phx.gbl...
> You need to do two things to make this work, assuming that your Brother
> printer driver software is TS-compatible:
>
> 1.) Use Remote Desktop Client version 5.2.3790.0 or later on your office
> PC.
>
> - Version 5.2.3790.x can be found on a 2003 server in the following
> folder:
>
> C:\WINDOWS\system32\clients\tsclient\win32\
>
> - You can download version 6.0.6000.16386 here:
>
> http://www.microsoft.com/downloads/d...f-d4f18c8f5df9
>
> 2.) Install the Brother printer driver software on your home PC. You can
> do this by "pretending" that the Brother is attached to the computer and
> running through the Add Printer wizard, making sure to uncheck
> "Automatically detect and install my Plug and Play Printer".
> Do *not* print a test page, this is unnecessary and will not work.
> Also, the local port you select is irrelevent, so simply choose the
> default LPT1.
> After you have successfully completed the wizard, delete the Brother
> printer you just installed--the necessary driver software will remain.
>
> Next time you connect to your home PC from your Office PC, your Brother
> printer will automatically show up as an option. It will be named
> something similar to "Brother HL-2040 (from COMPUTER)".
>
> The technique GTS describes (sharing, pooling, etc.) was a workaround for
> an older version of the client, but has not been necessary for years.
>
> -TP
>


It worked! Thank you so much TP.

As a greenhand in these stuffs, I chose the easiest way, so I downloaded the
new client. I didn't know there was one. I saw the release date was
11/28/2006, just a few days ago.

The new client worked. Learning from TP and GTS' discussion, I learned that
it was the default behavior of the new client to redirect all local printers
that helped. Yes, I noticed that the initial connection to the PC H was
actually slower than the old client -- the reason is that it is redirecting
a lot of printers connections, etc. I can sense that out, for the initial 30
seconds, there are a lot of chaos going on; but after 30 seconds, all my
printer can now be accessed from PC H.

One thing to note is that if I just install the driver from the CD on PC H,
it did not work;

But if I use the Setup Wizard to install everything from the CD on PC H, and
then delete the installed printer, then it worked;

So indeed the Setup Wizard has done a lot hidden things, in addition to
install the driver itself.

I am sure with this trick of using Setup Wizard then delete, GTS's method
will also work.

Thank you both for your expertise and excellent suggestions. This solves my
headache which lasted for one year.

I appreciate your great help!

MIke