Discussion Locked

Terminal Services printing issues

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have some remote users who are on a network separate from our network connecting to an application server running Terminal Services.
These remote users are running Windows 98 and are printing to an HP Laserjet 5Si printer via a JetDirect port connection (their printer connections are configured using the HP JetDirect port).
The Terminal Server is a Win2K server.
They are connecting to the Terminal server via TSAC (web). When the connect, the Laserjet 5Si printer is not available in the list of printers.

2 replies

by rsison

Try this solution...
Go to the terminal server and install the printer HP laserjet5si using the driver for Win2K. After installation delete the printer.Why ??? You need the printer driver in the server because whatever you do in the terminal ...theprocessing is done at the server and that includes the printing. I recommended to delete it after installation...(weird ??) even you deleted the printer still the driver is still in the registry and the terminal server could still access it wheneverit is needed.
Good luck

by pburke

You may also want to manually edit the wtsuprn file to map the name of the printer driver if it is different between the client system and server.
I need to frequently do this as my clients are running Windows 2000 or XP and the Terminal Server is still NT4.
A mapping would look similar to this:

"HP LaserJet 5si [MS] = "HP LaserJet 5si"

The first entry is the exact driver name on the client and the second is the exact driver name on the server. If the two are not the same, the printerwill not be able to map correctly.

I would also stay away from any printer driver not listed on the server. It is better to use a substitute drive that comes standard with the server OS.

This discussion is closed to new replies.