ANOTHER printer redirect problem...

[Vera Noest [MVP]]

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==?= <***@discussions.microsoft.com>
wrote on 11 dec 2006 in

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

[Vera Noest [MVP]]

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 -------------*

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

Post by Vera Noest [MVP]
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==?=

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

[Vera Noest [MVP]]

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==?= <***@discussions.microsoft.com>
wrote on 13 dec 2006 in

Thanks Vera. I'll give it a try. Any suggestions on the
network IP printer?
Steve

Post by Vera Noest [MVP]
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==?=

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

Post by Vera Noest [MVP]
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==?=

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