I have a situation where this office had problems and had to reload printers on all of their computers. They connect to their terminal server running win2003. Right now all the win98 machines can print to their local printer, but none of the XP machines can. The printer is installed as a local printer connected to a tcp/ip port. I've tried using a net use command and i've tried editing the registry according to an article i find from microsoft. I'm at a loss. Please help. Thanks.

I am not sure if this has anything to do with it or nor but when I was setting up a couple printers (that did not come with jet direct cards) attached to a print share device on the network, the regular users (non-admins) could not print to those printers until I gave them read/write rights the print spooler folder on the local computer. This was on Windows 2000 but maybe it also applies to XP.

Thanks for the response. The users are able to print locally to the printer. On the terminal server the printer does not even show up as an option for XP users. Remote Desktop has the box checked to map local printers. Normally that does the trick. Also, when admin is logged into the terminal server on an XP machine the printer can be seen attached to the win98 users and you can print to it through them.

According to Micro$oft, for the Remote Desktop Connection printer mapping to work, the printer has to be connected to Local LPT or COM ports NOT a locally mapped TCP/IP port. I found this to be correct. I even tried doing a manual mapping. One thing to watch for is that some of the newer printers like HP setup a new bi- directional printer port. Even though its a Parallel Centronics connection connected to LPT1 on your computer. You have to go in to port settings and change it from the HP created "DCOM" bi-directional port to the standard LPT1.

But then why do the Win98 machines work just fine with the TCP/IP printer? They are also running RDC and they can print. I don't think they're even using port capturing. There has to be a way to do this.

Did you ever get this figured out? If not, you could try this inelegant solution: 1. Setup the printer to be shared 2. Redirect lpt1: to the shared printer 3. Install the printer locally to lpt1: