(Msg. 1) Posted: Mon Dec 11, 2006 7:54 am
Post subject: ANOTHER printer redirect problem... Archived from groups: microsoft>public>windowsnt>terminalserver>client, others (more info?)
Hello:
I've browsed other printer redirect issues and can't find a solution ...
I use Windows 2003 Terminal Server
My remote clients are a mixture of WinXP Pro and W2k
My WinXP Pro clients print to their network printers just fine after applying:
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/en-us
My W2K clients cannot print to their network printers (they don't show in
the list) even after applying the registry changes from 302361.
(Msg. 2) Posted: Mon Dec 11, 2006 1:36 pm
Post subject: Re: ANOTHER printer redirect problem... [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Update the rdp client to the one that comes with your 2003 server,
in C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi and
check the EventLog on the server for driver name mismatches (case
sensitive!).
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?U3RldmUgSGFwcA==?= <SteveHapp DeleteThis @discussions.microsoft.com>
wrote on 11 dec 2006 in
microsoft.public.windows.terminal_services:
> Hello:
>
> I've browsed other printer redirect issues and can't find a
> solution ... I use Windows 2003 Terminal Server
> My remote clients are a mixture of WinXP Pro and W2k
>
> My WinXP Pro clients print to their network printers just fine
> after applying: 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/en-us >
> My W2K clients cannot print to their network printers (they
> don't show in the list) even after applying the registry changes
> from 302361.
>
> Any suggestions?
>
> Thanks
> Steve
(Msg. 3) Posted: Mon Dec 11, 2006 1:53 pm
Post subject: Re: ANOTHER printer redirect problem... [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Thanks Vera. Do you mean that I should copy the referenced file from the
server and load it onto the W2K client?
Also, just today I had a problem with a WinXP client ... a local printer
configured on the client as a standard IP port printer is not showing up.
Any idea on that one?
Thanks so much!
Steve
"Vera Noest [MVP]" wrote:
> Update the rdp client to the one that comes with your 2003 server,
> in C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi and
> check the EventLog on the server for driver name mismatches (case
> sensitive!).
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net > ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?U3RldmUgSGFwcA==?= <SteveHapp.DeleteThis@discussions.microsoft.com>
> wrote on 11 dec 2006 in
> microsoft.public.windows.terminal_services:
>
> > Hello:
> >
> > I've browsed other printer redirect issues and can't find a
> > solution ... I use Windows 2003 Terminal Server
> > My remote clients are a mixture of WinXP Pro and W2k
> >
> > My WinXP Pro clients print to their network printers just fine
> > after applying: 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/en-us > >
> > My W2K clients cannot print to their network printers (they
> > don't show in the list) even after applying the registry changes
> > from 302361.
> >
> > Any suggestions?
> >
> > Thanks
> > Steve
>
(Msg. 4) Posted: Tue Dec 12, 2006 6:11 am
Post subject: Re: ANOTHER printer redirect problem... [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
I mean run the .msi file on the W2K client (it's an installer
file).
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
=?Utf-8?B?U3RldmUgSGFwcA==?= <SteveHapp.RemoveThis@discussions.microsoft.com>
wrote on 11 dec 2006:
> Thanks Vera. Do you mean that I should copy the referenced file
> from the server and load it onto the W2K client?
>
> Also, just today I had a problem with a WinXP client ... a local
> printer configured on the client as a standard IP port printer
> is not showing up. Any idea on that one?
>
> Thanks so much!
> Steve
>
> "Vera Noest [MVP]" wrote:
>
>> Update the rdp client to the one that comes with your 2003
>> server, in
>> C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi and
>> check the EventLog on the server for driver name mismatches
>> (case sensitive!).
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net >> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?U3RldmUgSGFwcA==?=
>> <SteveHapp.RemoveThis@discussions.microsoft.com> wrote on 11 dec 2006 in
>> microsoft.public.windows.terminal_services:
>>
>> > Hello:
>> >
>> > I've browsed other printer redirect issues and can't find a
>> > solution ... I use Windows 2003 Terminal Server
>> > My remote clients are a mixture of WinXP Pro and W2k
>> >
>> > My WinXP Pro clients print to their network printers just
>> > fine after applying: 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/en-us >> >
>> > My W2K clients cannot print to their network printers (they
>> > don't show in the list) even after applying the registry
>> > changes from 302361.
>> >
>> > Any suggestions?
>> >
>> > Thanks
>> > Steve
(Msg. 5) Posted: Tue Dec 12, 2006 4:33 pm
Post subject: Re: ANOTHER printer redirect problem... [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Thanks Vera. I'll give it a try. Any suggestions on the network IP printer?
Steve
"Vera Noest [MVP]" wrote:
> I mean run the .msi file on the W2K client (it's an installer
> file).
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net > *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?U3RldmUgSGFwcA==?= <SteveHapp RemoveThis @discussions.microsoft.com>
> wrote on 11 dec 2006:
>
> > Thanks Vera. Do you mean that I should copy the referenced file
> > from the server and load it onto the W2K client?
> >
> > Also, just today I had a problem with a WinXP client ... a local
> > printer configured on the client as a standard IP port printer
> > is not showing up. Any idea on that one?
> >
> > Thanks so much!
> > Steve
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Update the rdp client to the one that comes with your 2003
> >> server, in
> >> C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi and
> >> check the EventLog on the server for driver name mismatches
> >> (case sensitive!).
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net > >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?U3RldmUgSGFwcA==?=
> >> <SteveHapp RemoveThis @discussions.microsoft.com> wrote on 11 dec 2006 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Hello:
> >> >
> >> > I've browsed other printer redirect issues and can't find a
> >> > solution ... I use Windows 2003 Terminal Server
> >> > My remote clients are a mixture of WinXP Pro and W2k
> >> >
> >> > My WinXP Pro clients print to their network printers just
> >> > fine after applying: 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/en-us > >> >
> >> > My W2K clients cannot print to their network printers (they
> >> > don't show in the list) even after applying the registry
> >> > changes from 302361.
> >> >
> >> > Any suggestions?
> >> >
> >> > Thanks
> >> > Steve
>
(Msg. 6) Posted: Wed Dec 13, 2006 4:52 am
Post subject: Re: ANOTHER printer redirect problem... [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Is redirection attempted at all? Anything in the EventLog when this
client connects?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?U3RldmUgSGFwcA==?= <SteveHapp.RemoveThis@discussions.microsoft.com>
wrote on 13 dec 2006 in
microsoft.public.windows.terminal_services:
> Thanks Vera. I'll give it a try. Any suggestions on the
> network IP printer?
>
> Steve
>
>
>
> "Vera Noest [MVP]" wrote:
>
>> I mean run the .msi file on the W2K client (it's an installer
>> file).
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net >> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?U3RldmUgSGFwcA==?=
>> <SteveHapp.RemoveThis@discussions.microsoft.com> wrote on 11 dec 2006:
>>
>> > Thanks Vera. Do you mean that I should copy the referenced
>> > file from the server and load it onto the W2K client?
>> >
>> > Also, just today I had a problem with a WinXP client ... a
>> > local printer configured on the client as a standard IP port
>> > printer is not showing up. Any idea on that one?
>> >
>> > Thanks so much!
>> > Steve
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> Update the rdp client to the one that comes with your 2003
>> >> server, in
>> >> C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi and
>> >> check the EventLog on the server for driver name mismatches
>> >> (case sensitive!).
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net >> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?U3RldmUgSGFwcA==?=
>> >> <SteveHapp.RemoveThis@discussions.microsoft.com> wrote on 11 dec 2006
>> >> in microsoft.public.windows.terminal_services:
>> >>
>> >> > Hello:
>> >> >
>> >> > I've browsed other printer redirect issues and can't find
>> >> > a solution ... I use Windows 2003 Terminal Server
>> >> > My remote clients are a mixture of WinXP Pro and W2k
>> >> >
>> >> > My WinXP Pro clients print to their network printers just
>> >> > fine after applying: 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/en-us >> >> >
>> >> > My W2K clients cannot print to their network printers
>> >> > (they don't show in the list) even after applying the
>> >> > registry changes from 302361.
>> >> >
>> >> > Any suggestions?
>> >> >
>> >> > Thanks
>> >> > Steve
All times are: Eastern Time (US & Canada) (change)
Page 1 of 1
You can post new topics in this forum You can reply to topics in this forum You can edit your posts in this forum You can delete your posts in this forum You can vote in polls in this forum
Home
Forums
Home
FAQ
Profile
Private Messages
Log in
Windows Other