Network printer can not be mapped on Terminal server

X

xiaomei

Hi, There,
Last time we found the network printer with RJ-45 interface and build-in
print server can not be mapped on the TS when login to remote Terminal
server, we checked and got the document from MS as following:
http://support.microsoft.com/default.aspx/kb/302361/en-us

It instructed to change client registry then it will work, I did the test,
yes, it worked fine after the changes.

However, the problem come: We have around 700 desktop in each brance office,
it will be a big task if we did this on each machine one by one.
Is that any other solution to solve the problem, like any patches from Ms.
Because for windows vista, it does not need the changes.

Many thanks for any suggestion!

Shermaine
 
L

Lanwench [MVP - Exchange]

xiaomei <xiaomei@discussions.microsoft.com> wrote:
> Hi, There,
> Last time we found the network printer with RJ-45 interface and
> build-in print server can not be mapped on the TS when login to
> remote Terminal server, we checked and got the document from MS as
> following: http://support.microsoft.com/default.aspx/kb/302361/en-us
>
> It instructed to change client registry then it will work, I did the
> test, yes, it worked fine after the changes.
>
> However, the problem come: We have around 700 desktop in each brance
> office, it will be a big task if we did this on each machine one by
> one.
> Is that any other solution to solve the problem, like any patches
> from Ms. Because for windows vista, it does not need the changes.
>
> Many thanks for any suggestion!
>
> Shermaine


Hi. Did you see the replies to your nearly identical post (you sent it
7/5/2005) ?

The answer is to have them all use the latest MS Remote Desktop
Client....you don't need to do anything in the registry then.

I see that you're using the web interface to the newsgroups, which makes it
difficult to find/follow/track/search anything. I suggest you start using a
newsreader instead. You already have OE, but there are many other options.

The following is from a post by MVP Malke ...

-------------------------------------------------------
Here's information on Usenet and using a newsreader:

http://www.elephantboycomputers.com/page3.html#12-09-02 - a brief
explanation of newsgroups
http://michaelstevenstech.com/outlo...ssnewreader.htm
http://rickrogers.org/setupoe.htm
http://support.microsoft.com/defaul...wto/default.asp
- Set Up Newsreader

http://www.dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html
http://aumha.org/nntp.htm - list of MS newsgroups
microsoft.public.test.here - MS group to test if your newsreader is
working properly
http://www.mailmsg.com/SPAM_munging.htm - how to munge email address
http://www.blakjak.demon.co.uk/mul_crss.htm - multiposting vs.
crossposting

Some newsreaders for Windows
http://www.forteinc.com/agent/index.php - for Forte
http://www.mozilla.org (Thunderbird does newsgroups)
http://gravity.tbates.org/

-------------------------------------

The MS public news server is msnews.microsoft.com, no authentication
required, and you can subscribe to as many groups as you wish.
 
X

xiaomei

Dear Lanwench,
Thanks for your time to attend my problem again.
Yes, I download RDC Ver 6.0, installed on my windows XP SP2 machine, but
found no help. I even tried the same process on my coleague windows XP SP2
machine, the printer were not mapped.

However, we tried to login with Windows Vista (Also version 6.0) , we can
see the same printer mapped, so I am sure I installed with correct driver on
the Terminal server.
Not sure where am wrong? :(

Thanks again !!
Shermaine


"Lanwench [MVP - Exchange]" wrote:

> xiaomei <xiaomei@discussions.microsoft.com> wrote:
> > Hi, There,
> > Last time we found the network printer with RJ-45 interface and
> > build-in print server can not be mapped on the TS when login to
> > remote Terminal server, we checked and got the document from MS as
> > following: http://support.microsoft.com/default.aspx/kb/302361/en-us
> >
> > It instructed to change client registry then it will work, I did the
> > test, yes, it worked fine after the changes.
> >
> > However, the problem come: We have around 700 desktop in each brance
> > office, it will be a big task if we did this on each machine one by
> > one.
> > Is that any other solution to solve the problem, like any patches
> > from Ms. Because for windows vista, it does not need the changes.
> >
> > Many thanks for any suggestion!
> >
> > Shermaine

>
> Hi. Did you see the replies to your nearly identical post (you sent it
> 7/5/2005) ?
>
> The answer is to have them all use the latest MS Remote Desktop
> Client....you don't need to do anything in the registry then.
>
> I see that you're using the web interface to the newsgroups, which makes it
> difficult to find/follow/track/search anything. I suggest you start using a
> newsreader instead. You already have OE, but there are many other options.
>
> The following is from a post by MVP Malke ...
>
> -------------------------------------------------------
> Here's information on Usenet and using a newsreader:
>
> http://www.elephantboycomputers.com/page3.html#12-09-02 - a brief
> explanation of newsgroups
> http://michaelstevenstech.com/outlo...ssnewreader.htm
> http://rickrogers.org/setupoe.htm
> http://support.microsoft.com/defaul...wto/default.asp
> - Set Up Newsreader
>
> http://www.dts-l.org/goodpost.htm
> http://www.catb.org/~esr/faqs/smart-questions.html
> http://aumha.org/nntp.htm - list of MS newsgroups
> microsoft.public.test.here - MS group to test if your newsreader is
> working properly
> http://www.mailmsg.com/SPAM_munging.htm - how to munge email address
> http://www.blakjak.demon.co.uk/mul_crss.htm - multiposting vs.
> crossposting
>
> Some newsreaders for Windows
> http://www.forteinc.com/agent/index.php - for Forte
> http://www.mozilla.org (Thunderbird does newsgroups)
> http://gravity.tbates.org/
>
> -------------------------------------
>
> The MS public news server is msnews.microsoft.com, no authentication
> required, and you can subscribe to as many groups as you wish.
>
>
>
 
Back
Top Bottom