How to make a Network Printer work from Terminal Server

By tdnetwork ·

We have a office in Dubai and we have a Network printer (HP Laserjet 2015)which works fine. We have our Terminal Server based in the US which we connect thru RDC.

I have tried installing the driver/printer in the server. All possible attempts made. Even the Internet Printing option is activated. The print command goes thru but it doesn't print.

I need to know what is missing. I have done the following:
1. Installed the driver in TCP/IP port
2. Activated the Internet Printing in IIS
3. The Printers option is ticked before I login to Remotely

Please help me get thru this.

PS. Also we have a office in Australia and they are having a similar problem with a PORT printer.

Please assist.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Make a Network Printer work from Terminal Server

Windows 2000 Terminal Services does not redirect network printers

In Microsoft Windows 2000 Terminal Services you can redirect clients local printers when they log on to a Terminal Services session with the Microsoft RDP 5 Terminal Services client. The redirection of local printers is a default behavior.

When clients connect to a Terminal Services session and the clients have network printers configured, the client's network printers are not redirected. This behavior is by design. Microsoft does not provide support for redirection of network printers in Windows 2000 Server or Advanced Server. This functionality requires a 3rd party add-on product.

If terminal services users need to print to a network printer, the client may set up the network printer on the Terminal Services computer through the Add Printer Wizard and enable users to select and print to that printer. In cases where this is not an option, it is sometimes possible to map a local port (LPT) on the client side to the network path and install a printer driver to print to that local port. This workaround will automatically redirect jobs to the local printer, and the output sent to that printer will then be redirected again to the network printing device. This workaround is not a design feature of RDP 5, and it will not work in all cases.

The information in this article is provided as informational and not as a supported implementation of Terminal Services redirected printing.
If there is a special circumstance where the user needs to redirect a network printer, you can map the network printer to a local port.

For Windows 2000 and Microsoft Windows NT, you can use the following command:

net use lpt3 \\servername\printer /persistent:yes
This command maps the network printer to the local port LPT3. The user can then install the correct drivers for that printer as though the printer was installed on LPT3. If this is done, the printer on LPT3 is redirected when the user connects to the Terminal Services session. This also works with LPT1 and LPT2, as long as there is not a local device on either of these ports.

For Microsoft Windows 95, Microsoft Windows 98, and Microsoft Windows Millennium Edition (Me):

Right-click on the network printer in the printers folder and click Properties. From the Details tab in the Printer Properties box, click Capture Printer Port. This action can enable you to select the LPT port that you want to map to this network path.

The preceding workaround is useful in environments when a user opens a session to a Terminal Services computer on a remote network (for example, across the Internet) and wants to print back to a printer shared on the local area network (LAN).

An alternative way to work around this is to install the remote desktop connection client, which is compatible with the latest version of the Remote Desktop Protocol (RDP) protocol and is compatible with Windows 2000 terminal services. This client is included with Microsoft Windows XP and is also available for download at the following Microsoft Web site:
More here:

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

Collapse -

Windows 2003 terminal server & XP client

by tdnetwork In reply to Make a Network Printer wo ...


We are using:
Windows 2003 for Terminal Server
Windows XP for clients

If you have steps about how to go about the instatallation, it would be of great help.
- To install a network printer
- To install a LPT port printer

Thanks for your help

Collapse -

Step by step here for your terminal server printing...

Though take into account that it might (or not) work. It depends on your set up.

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

Collapse -

Not working

by tdnetwork In reply to Step by step here for you ...


Don't think this will work, coz its a Terminal server and will not find any printers on the network. Have tried that already a zillion times.

There must be another way out.


Collapse -

Have you installed the printer as a "Local" printer on the server.

by 1bn0 In reply to Not working

It sounds like you are having a problem installing the driver on the server. This a prerequisite before any attempt can be made to enable the printer for Terminal Services clients.

Keep in mind: Many new Windows based printers will not install unless the server can connect to the printer during printer installation.

You can use the "net use lpt3 \\servername(or IPAddress)\printer" to create a connection. All you need to accomplish on the server is getting the Drivers for the printer installed. If yu have a printer ofthe same model available on the network , local to the server use it as the connection. It does not matter as long as the driver gets installed.

Once the driver is installed on the server, you should have success using the information provided by Peconet.

Collapse -

Installation of the Printer

by tdnetwork In reply to Have you installed the pr ...

I have installed the driver by downloading the latest one from the website for Windows Server 2003.

The installation was also fine as I gave the IP Address as a PORT location.

The problem is that its a Network printer. I am assuming the best way to make it work is to make it an Internet printer. Could anyone help me with thiS?

Collapse -

Create a new "port"

by 1bn0 In reply to Installation of the Print ...

When you add the printer you have the option of selecting the "port" or creating a new one. Selecting a new TCP/IP port starts the add port wizard.

If the printer is already installed you can staret the wizard from the printer properties box on the ports tab. Just click on Add port and then select TCP/IP from the list and click OK. It will start the wizard and create the "port"

Collapse -

Some things to check

by cody In reply to How to make a Network Pri ...

Some things to check:

1. In the RDP connection settings, did you put a tick under [Local Resources] tab to automatically map the printer upon connection?

2. Check the Event Viewer log on the server. It will tell you whether the driver is missing on the server. Remember the driver must be EXACTLY the same on the workstation as it is on the SERVER. It must be NAMED the same as well. So if the printer driver displayed under the [Advanced] tab -> "Driver" is called "HP Laserjet 5" on the workstation but it's called "HP Laserjet 5 Series" on the server, it *WON'T* work.

3. If you are using a NETWORK PRINTER with an IP address, and checked the two steps above, it should work. Just check the Event Log for this.

4. If you are using a USB connected printer, then you will have to use PORT REDIRECTION or mapping. This is rather simple. The main printer on the WORKSTATION with the USB connection, share it out. Then from the command prompt, type in "net use lpt1 \\computer\printer". Replace that with the name of your computer and your workstation printer's share. RDP doesn't work with printers connected using USB but it works with LTP1 so essentially you're fooling your computer to think that LPT1 is going to your computer's shared printer.

Try that and let me know.

Related Discussions

Related Forums