Client printer doesn't map to TS...

[moontea]

....but an instance of the same printer, installed on
another computer as a network printer, does map to TS. So
I don't think it's a matter of the name of driver, which I
read is to blame for most of these cases.

Nor do I receive any message in the System log.

Any ideas?

 

[Vera Noest [MVP]]

Are these 2 clients running the same OS? Driver names for the same
printer can vary on different OSs. Have you checked the redirection
properties on the rdp clients? Are you running the latest rdp client?

 

[Biggs]

Is the printer connected directly to the computer that it doesn't work
on? If the printer is connected directly then there is a registry hack
that you need to do to pass all the ports through to the TS session.
Mapped printers will work fine. Let me know if this is the case and
I'll check our database for the Q article.

 

[Guest]

Yes you are right about the registry hack. I found that solution, too. The link i
http://support.microsoft.com/default.aspx?scid=kb;en-us;302361&Product=termsv
It worked great, too