• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 707
  • Last Modified:

Remote Printing via Terminal Server

Terminal Server - Windows Server 2003 R2
Remote Desktop Clients - Windows 98SE, 2000 and XP SP2

I wish to allow clients to send the print jobs back to printers at the client side when they are connecting to the Terminal Server via Remote Desktop Connection.  This is working fine with older model printers which Windows Server 2003 has the default printer drivers.  For newer printers, I followed the guides from EE to add the printer drivers to the Terminal Server (printers  and faxes->Server options->Drivers->Add). At the client side however, I am confused how the printer setup should be done.  My questions are as follow:

1. Do I have to add the printer drivers for all OS versions (98SE, W2K and XP) at the Terminal Server?

2. How is the printer setup at client side?  To print to specific printer, do I have to set the printer as default printer at each client PC?  How about those non-default printers that are also connected to client PCs?  Can they print to other non-default printers?

3. Most the printers are connected to the client PCs via standard TCP/IP port.  Is it neccessary to map the printers to client PC's local port or LPT port?

Please advise.  THank you.
0
hoggiee
Asked:
hoggiee
  • 4
  • 3
1 Solution
 
mglmrtnzCommented:
Try Installing the printer drivers for each printer on the server,
The client should see their local printer when trying to print.
The client should also have printers checked under local devices in RDP options.  Thats how i did it oncce.

Hope it helps

0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
hoggiee,

1.  You only have to install printer drivers for the OS versions that have those particular printers.  Generally the W2K and XP drivers are the same, so the only issue would be installing 98SE drivers for printers owned by users that are connecting with 98SE.

2.  The printer is already set up on the client side... it's their printer.  They can print to any printer that's connected to their computer locally which also has the driver installed on the Terminal Server.  (They can also print to any printer that's attached to the Terminal Server or available on the LAN through Active Directory -- if permissions are granted to do so).

3.  You don't have to do anything on the client side.  If they can print locally then it'll automatically be redirected when they connect via RDP as long as the driver is installed on the Terminal Server.

If you need any further information, this is the Ultimate Guide to Terminal Server Printing:
http://www.brianmadden.com/content/content.asp?ID=62

Jeff
TechSoEasy
0
 
hoggieeAuthor Commented:
TechSoEasy:

I did as what you said, adding the required printer drivers on the Terminal Server.  I am having the following problem:

1. For printer HP LaserJet 5100: No problem for Windows 2000 and Windows XP RDC clients.  For Windows 98 RDC clients however, the printer could not be seen in the Printers and Faxes of the Terminal Server.  Below is what the Event Viewer says:

"Driver HP LaserJet 5100 Series PCL 6 required for HP LaserJet 5100 Series PCL 6 is unknown.  Contact the administrator to install the driver before you login in again."

2. For printer HP LaserJet 2420:  Again the same problem with problem no. 1.  Below is from the Event Viewer:

"Driver HP LaserJet 2420 PCL 6 required for printer FNA LaserJet 2420 is unknown.  Contact the administrator to install the driver before you login in again."

* FNA is the name given to indicate my Finance Department.

3. For Canon ImageRunner iR5000 Series Copier: This printer could not be seen at all for all types of Windows OS versions.  But no error in Event Viewer!

For your info, below is the driver details copied from "Printers and faxes -> Server Properties-> Driver" part of the Terminal Server:

Canon iR5000-6000 PCL5e   x86   Win 2000,Win XP and Windows Server 2003
Canon iR5000-6000 PCL5e   x86   Win 95, Win 98, and Windows Millennium Edition
HP LaserJet 2420 PCL 6       x86   Win 2000,Win XP and Windows Server2003
HP LaserJet 2420 PCL 6       x86   Win 95, Win 98, and Windows Millennium Edition
HP LaserJet 5100 PCL 6       x86   Win 2000,Win XP and Windows Server 2003
HP LaserJet 5100 Series PCL 6    x86    Win 2000,Win XP and Windows Server 2003

I'm really running out of ideas.  Please guide me what else I can do.  By the way, what is the file (.inf) that stores all the printer drivers in Windows Server 2003?  Thank you.  
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I'm a bit confused... does the Win98 client have a HP LaserJet 5100 and a HP LaserJet 2420 attached locally?

Are you using Terminal Services within your LAN???

Jeff
TechSoEasy
0
 
hoggieeAuthor Commented:
TechSoEasy:

Both the HP LaserJet 5100 and LaserJet 2420 are attached to a print server LPT1 and LPT2 port, and are added to all client PCs in the client LAN.  Terminal Services is not within the LAN, it's between 2 remote sites.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
So, I still don't understand what these printers have to do with printing on the CLIENT SIDE?  If they are in your LAN, they are on the SERVER SIDE, no?

Jeff
TechSoEasy
0
 
hoggieeAuthor Commented:
TechSoEasy:

The client PCs and the HP LaserJet printers are in the same local LAN at client side. The client PCs and Terminal Server are in different LAN, different physical location. When client PC connects to the Terminal Server via a RDC, run some applications on the server, and print reports on the server which will redirect the print jobs back to the HP LaserJet printers at the client side.  Have a better idea?
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Yes, I do understand now... and I'm wondering if you read the document I provided which describes your situation specifically and provides you with the exact steps necessary to accomplish what you are wanting to do.

Jeff
TechSoEasy
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now