Selective printing to local printer on TS client

[deus]

I have a client running W2k Pro with a local printer
(tried with both HP940c and HP6122, same results) that is
getting redirected by the 2000 TS server, pretty standard
stuff. I've installed the corporate/network drivers for
this printer on both the client and the server. Everything
seems ok, the printer shows up on the server when
connected with the TS client and I am able to print test
pages. I am also able to print using TAM, a program the
company I work with uses to do insurance ratings. For some
reason I am not able to print out of other MS apps though,
including: Word, Excel, Notepad, etc. from the client PC.
When the user is connected I can be on the TS server and
print normally from there to that user's local printer
with all apps including MS. Any ideas why I can print test
pages and out of some programs, but not others on the
client? Thanks.

deus

 

[deus]

Btw, forgot to mention that when I do print from Word,
Excel, Notepad, etc., it seems to go through perfectly
fine. This makes it even more annoying because it seems
like it goes through without errors (in the print queue or
event viewer), but nothing ever comes out of the printer.

deus

 

[Tom]

It sounds like a driver compatibility problem....

This is a well known issue in the term server / Citrix
community. You will find that quite a few printers (among
which are many HP DeskJet printers) cannot be used using
their regular driver. You will have to find another "term
server compatible" driver that will suit your needs (check
with HP for help....).

The fact that you can print from a couple in-house apps or
from the server (when you're logged in with admin rights)
can be explained by the coding of the apps and the user
that initiates the print process (in your apps it might be
the system that prints...).

You can also try to post something (or browse through the
KB) on Citrix's website.

Hope this helps...

Tom

 

[deus]

Well just so anyone who searches and finds this article
knows, it was a Win2k SP3 issue. I had to grab a hotfix
and now it works perfectly. The problem was printing from
a mapped drive on a TS client. You can tell if you have
this problem by looking at the port that you are printing
too. It will be something like \\*path_here*\TS002. And
you will also notice you have a file named TS002 now in
that directory. For some reason it prints to a file when
printing from a mapped drive on a TS client on Win2k SP3.
Weee...