problem with maping network printers on terminal server

[Miha]

Hi

We're having trouble with mapping network printers from client side (Windows
XP, using RDC) to terminal server (Windows 2003 Standard).
All printers that client has installed on his system are mapped correctly,
but the network printer that is connected directly through TCP/IP protocol
(has it's own IP address) and client also use it does not map. No entries on
server's event log, not even any driver problems.. Printer just don't map
into the TS session.
Can anyone help me please with that?
It's strange, because all other printers that clients has installed that are
also network printers but connected to servers and other workstations and
shared are mapped correctly, the only problem is with printers that are
connected directly to network like I said via TCP/IP

Thank you all in advance
Best regards
Miha

 

[Jetro]

Install the most recent version of the client. (If this isn't possible, see:
Windows 2000 Terminal Services Does Not Redirect Network Printers (Q264039)
and 302361 - Multifunction Printers That Use DOT4 Ports Are Not Redirected
By Using Remote Desktop.)

 

[Miha]

Thanks for the reply.
I checked, and all clients are using the most recernt version of RDC. It's
strange, because network printers that clients have installed are actually
mapeed into TS, problem is only with TCP/IP network printers ?
I found the solution to install the same printer locally on LPT1 at client
side and then share and map this TCP/IP printer using net use \\lpt2
\\server\printer.
But I find this rather dissapointing, becasue all this talking about new
features on Win2003 TS, and Microsoft couldn't make this to work...
thinking about 3rd party product for printing through terminal services.

Regards
Miha