Re: [2003] Why can't app print?
- From: CJ <CJ@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 09:53:01 -0800
Thank you for your excellent and informative reply.
Regarding logging for TS, I found some information regarding turning on
Security logging for TS. Is this what you were refering to? If so, which
logging event will show printer redirection success or failure? Account
Logon Events?
I attempted to apply the steps in KB 302361 but could not locate the
referenced key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server
Client\Default\AddIns\RDPDR
Specifically, Terminal Server is not under the Microsoft key.
What does that mean?
"Vera Noest [MVP]" wrote:
That's built-in functionality of TS..
Configure the server to allow redirecting of printers, in Terminal
Services Configuration (is enabled by default)
Configure the client to redirect local printers (in Options - Local
resources)
Then start a TS session and check if you see the redirected printer
in your session:
1) If it's there, problem is solved.
2) If it is *not* there, check the EventLog on the Terminal Server.
If you see *no* Events at all about printer redirection, then it
means that redirection is not attempted at all. Solution: check the
configuration of printer redirection in the RDP client and on the
Terminal Server, update the RDP client to at least the XP SP2
version or apply KB article 302361 to get support for redirection
of non-standard local port names, including tcp/ip ports.
http://support.microsoft.com/?kbid=302361
3) If you *do* see an error regarding printer redirection, then
redirection is attempted, but fails because the server doesn't have
a driver for the printer.
Solution: whatever you do, do not install a 3rd party printer
driver on the Terminal Server, unless it is a Windows Hardware
Quality Labs (WHQL) signed driver. Many non-WHQL drivers are not
TS-compatible, and some are known to crash your printer spooler or
the whole server. In stead, map the printer to a native driver by
creating a custom ntprintsubs.inf file, as described in KB article
239088.
http://support.microsoft.com/?kbid=239088
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
=?Utf-8?B?Q0o=?= <CJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 04 jan
2007:
"Vera Noest [MVP]" wrote:
No, I mean this: I assume that the users have a connection to
this printer on their workstations. That means that - given the
correct version and settings on the rdp client on the
workstation - the printer could be automatically created for
them in the session, without installing the printer at all on
the server. That's called a redirected session printer.
Can you please explain how I can configure TS so that - the
printer could be automatically created for them in the session,
without installing the printer at all on the server?
Thanks
- Follow-Ups:
- Re: [2003] Why can't app print?
- From: CJ
- Re: [2003] Why can't app print?
- References:
- Re: [2003] Why can't app print?
- From: Vera Noest [MVP]
- Re: [2003] Why can't app print?
- Prev by Date: No License Server
- Next by Date: Re: [2003] Why can't app print?
- Previous by thread: Re: [2003] Why can't app print?
- Next by thread: Re: [2003] Why can't app print?
- Index(es):
Relevant Pages
|
