Discussion Locked

Terminal Services Remote Printing

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a Windows 2000 Server with Terminal Services and about a dozen remote users connecting from different sites either via DSL modem on their local lan or dialup. Recently 4 users moved from the lan (with TS) to another lan at the remote site.I configured their network printers using the NET USE command to print to LPT2, LPT3 and successfully printed from the business application on the TS to the remote printers. The next day the remote print servers are getting the message: "error found when printing filename to LPT1:" Do you want to retry or cancel". I suspect that the NET USE command may be confusing the server at the remote site. The user can print to LPT1: when logged on to the local PC but not when logged on to the network. I have the same setup on a second lan (using NET USE to map to a printer server) and have not had problems. Anyone having similar problems?

2 replies

by bogdansua

Are you using SP3? Ithink their are known issues with Printing on a W2K Terminal Session with SP3.

by lmayeda

No, am still on W2K Server SP2. I ran across a caveat somewhere that Microsoft does not support remote printing when the remote printer is not directly connected to LPT1. However, I have a couple of sites where the remote clients are printing to their (remote) network printers. What I need to understand is if the remote network server comes into play in any way when the NET USE command is used by the remote clients to map to the remote network printers.

This discussion is closed to new replies.