Terminal Server Printing WithWindows NT/2000 Terminal Server

7/31/2019 Terminal Server Printing WithWindows NT/2000 Terminal Server

1/48

Terminal Server Printing With Windows NT/2000 Terminal Server

October 31, 2002

Carlo E. Aranda

Advanced Technology Specialist

Network Solutions Center

Ricoh Corporation


2/48

Ricoh Corporation / Network Solutions Center - Windows NT/2000 Terminal Server Printing White Paper 2

The information contained in this document represents the current view of Ricoh Corporation on thediscussed issues as of the date this document was created. Because of an ever-changing market, neither

Ricoh Corporation nor any of its affiliates can guarantee the accuracy of any information after the date of

this publication.

This white paper is for informational purposes only. Ricoh Corporation makes no warranties, expressed or

implied, in this document.

No part of this document may be reproduced, stored in or introduced into a retrieval system, or transmittedin any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any

purpose, without the express written consent of Ricoh Corporation.

Ricoh Corporation may have patents, patent applications, trademarks, copyrights, or other intellectualproperty rights covering subject matter in this document. Except as expressly provided in any written

license agreement from Ricoh Corporation, the furnishing of this document does not give you any license to

these patents, trademarks, copyrights, or other intellectual property.

2001 Ricoh Corporation., All rights reserved.

Other products and company names mentioned herein may be the trademarks of their respective owners.


3/48


Table of Contents

Table of Contents ______________________________________________________ 3

Introduction___________________________________________________________ 4

What is Terminal Server? _______________________________________________ 4

Advantages of a Terminal Server Environment _____________________________ 5

Printing related differences between Terminal Server versions ________________ 6

Microsoft Windows NT 4.0 Terminal Server Edition: _________________________ 6

Microsoft Windows 2000 Terminal Server Services: __________________________ 6

What about Citrix Metaframe?___________________________________________ 7

Printing Scenarios______________________________________________________ 8

Scenario 1: Printer installed on the server / print device is local to the server______ 8

Scenario 2: Printer installed via point and print / print device is local to the client_ 10

Scenario 3: Windows 2000 Auto-create / Automatic Printer Redirection _________ 12

Scenario 4: Windows 2000 Manual Printer Redirection ______________________ 14

Configuration Guides _______________________________________________ 16

W2K Auto-Create / Automatic Printer Redirection Configuration Guide _________ 16A Look Behind The Scenes __________________________________________ 28

W2K Manual Printer Redirection Configuration Guide: ______________________ 32

Questions You Should Ask______________________________________________ 46

Ricoh Products Support Status __________________________________________ 47

WIndows2000 Terminal Server Services __________________________________ 47

Windows NT 4.0 Terminal Server Edition _________________________________ 48


4/48


Introduction

The main purpose of this document is to assist field personnel supporting Windows

Terminal Server printing in Windows Terminal Server environments. The intended

audience is anyone who will provide any type of support with regard to Terminal Serverenvironments and Ricoh products. Because it is essential to know the platform you are

trying to print on, this document can also satisfy a need for a Terminal Server overview.

This paper will focus more attention to the Windows 2000 configurations mainly becausethis is the more recent technology that is being implemented in the field.

One of things that I would like to address before you proceed through this document issome of the terminology that will be used. Like many others, I have adopted Microsofts

terminology with regard to printing. The terminology is fairly simple, however, I have

seen it cause some confusion. To avoid any unnecessary confusion, I will list some of theterms that will be used in this document and my interpretation of their meanings:

Printer When I use the term printer, I am referring to the software component of

printing, also known as a print driver.

Printing device- When I use the term printing device, I am referring the physical

printing device, i.e. the MFP, Aficio 2610N, etc.

Local / Locally When I refer to a local printer, I am referring to a printer that is

pointing/ported/attached directly to a printing device from the workstation (i.e. LPT, LPRdirectly to the device). This indicates that the printer is not configured for a print server.

Note: Resources/printers located at other nodes on the network are referred to as remote.

What is Terminal Server?

Windows Terminal Servers contain three main components: a multi-user component(MultiWin), a remote presentation component/protocol (RDP Remote Desktop

Protocol), and client software (Terminal Server Client).

These three components enable a user running a thin client/dumb terminal to connect to

the Terminal Server and use resources on the server. All processing and resource usage is

done on the server. This includes all data storage, processing, and application execution.Basically, the only thing that travels the network between the client and the Terminal

Server are keystrokes and screen updates.

The multi-user component is an essential component on Windows Terminal Servers. This

component is responsible for the multi-user functionality of the product. The term multi-

user means that multiple users can access an application, driver, and operating system


5/48


processes on the Terminal Server simultaneously. The mechanics/logic behind the multi-

user component can get pretty intricate and is beyond the scope of this document. For thepurpose of this document, just remember that one of the main components of a Windows

Terminal Server is the multi-user component (MultiWin) and it is responsible for making

sure that the servers hardware (processor, memory, etc.) and software (applications,

registry, etc.) can be accessed simultaneously by many users without causing conflicts.Because of Terminal Services multi-user nature, it is essential that any software loaded

on a Terminal Server is multi-user compatible. Most software that is written according

to Microsofts standards will not have a problem. However, many third party softwarevendors do not comply completely with Microsofts standards and can result in a wide

array of compatibility issues.

The RDP (Remote Desktop Protocol) is just like the name suggest. Its main function is

to bring the servers desktop to the users who are running the client software, hence the

name Remote Desktop Protocol. If you have ever been exposed to MicrosoftsNetMeeting, Symantecs PC Anywhere, or VNC, you are already familiar with the

remote desktop concept. Currently there are two versions of this protocol that you mayrun into out in the field: RDP 4.0 and RDP 5.0. RDP 4.0 was first introduced with

Windows NT 4.0 Terminal Server Edition and RDP 5.0, which is the current version, isimplemented in Windows 2000 Terminal Server. One point to remember about RDP is

that it is only supported over TCP/IP. I will explain in sections to come how the different

versions of RDP affect printing.

The third component, the Terminal Server Client, is also crucial to this environment. The

client is a small piece of software that is included with Window NT/2000 TerminalServers. The client software gets installed on the client machine / terminal. Once you

launch the Terminal Server Client you can then select the terminal server that you want toconnect to. Once connected, you are in a terminal session and have access to the

resources on the terminal server. The Terminal Server Client uses RDP to communicate

with the server.

Note: The Terminal Services Advanced Client (TSAC) has recently superceded the RDP

client that ships with Windows 2000. The TSAC is based on the RDP 5.0 feature set, but

comes in the form of an ActiveX control. It can be downloaded and executed withinMicrosoft Internet Explorer, or any application that can make use of ActiveX controls.

Terminal Services technology is includedin Windows 2000 Server, Windows XP, andthe upcoming Windows .NET Server.

Advantages of a Terminal Server Environment

Some advantages of implementing a Terminal Server environment include the following:

Centralized management.


6/48


Software upgrades do not have to be rolled out over hundreds/thousands

of computers. Only the Terminal Servers need to be upgraded. Client machines can be very inexpensive dumb terminals / thin clients

reducing cost. Desktop support cost can be greatly reduced because the IT staff would

not have to be as robust due to having thin clients.

Printing related differences between Terminal Server versions

Microsoft Windows NT 4.0 Terminal Server Edition:

Windows NT 4.0 Terminal Server Edition only allows printing in the configurationwhere the printer is installed on the terminal server. It allows any direct connect or

network connection.

When printing devices are connected to the remote client machines, the remote client

must share the printer on the network. The printer is then installed on the server as a

network printer. In this case the client is acting as the print server. Printing is not different

from when it is in a single user network-connected printing environment.

We will take a closer look at these configuration methods in the following Printing

Scenarios.

Note: Windows NT 4.0 Terminal Server Edition is based on the RDP 4.0 feature set. It

does not support any type of port redirection. We will see in the sections to come that

Microsoft added port redirection to the RDP 5.0 feature set included with Windows 2000Server.

Microsoft Windows 2000 Terminal Server Services:

Windows 2000 Terminal Services has the ability to auto-create print queues for a usersterminal session as the user logs into the terminal server. This auto-created queue will

redirect its output to a printer that resides on the client terminal / PC.

This process is automated as long as the terminal client / PC has the same print driver

installed locally as a print driver that is installed on the terminal server. If the driver

installed on the client is different then the driver installed on the server, you can manually

create and redirect a printer on the server to the client.

We will take a closer look at these configuration methods in the following Printing

Scenarios.


7/48


What about Citrix Metaframe?

Citrix Metaframe is software developed by Citrix Systems, Inc. that must be ran on a

terminal server when implemented on Windows platforms. Citrix Metaframe is often

associated and sometimes confused with Terminal Server, therefore, I will provide someinformation that can help you with determining the difference between a Citrix

Metaframe environment and a Windows Terminal Server environment.

Citrix Metaframe is a software package that uses Terminal Servers multi-user

environment to its advantage. In fact, it was Citrix who created MultiWin, the multi-user

component in Terminal Server. In May 1997, Microsoft and Citrix signed an agreementto cross-license their technologies so that Microsoft could bring the MultiWin component

into the mainline NT code base. This MultiWin component was first introduced into a

Microsoft OS with Windows NT 4.0 Terminal Server Edition.

So whats the purpose of Citrix? Some of the benefits that Citrix adds to MicrosoftsNT/2000 Terminal Server are the following:

The ICA protocol: This protocol is much more efficient than the RDP protocol.

Can support many more client operating systems than Windows Terminal Server. Can support many more client devices than Windows Terminal Server. Can support many more protocols than Windows Terminal Server. RDP runs only

over TCP/IP. Can support more connection types i.e., direct dial up, direct serial (async). Advanced multi-media support. Additional client capabilities i.e., SpeedScreen and Program Neighborhood Contains more management tools than Windows Terminal Server

Better web based support Can publish apps to the web (ALE)

One thing you will want to remember if you support Terminal Server / Citrix Metaframe

printing is that with Metaframe you can auto-create / auto-redirect a printer on the server

directly to a network printer that is attached to the client. This is not possible with

Windows Terminal Servers. Windows 2000 Terminal Server will only map local printerson the client that are configured with a LPT, COM, or USB port.

Note: Windows 2000 Terminal Servers Auto-create / Automatic port redirection featureis explained in greater detail in following sections.

Note: The same auto-create / auto-redirect concept that is used on Windows 2000Terminal Servers are used for Citrix terminal servers.


8/48


Printing Scenarios

Prior to Windows 2000 there were two common terminal server-printing methods.

The following are two general ways that a driver could be installed on Windows NTTerminal Servers:

1. The printer (driver) is installed directly on the terminal server.2. The printer (driver) is installed on the terminal server via point and print by

browsing to a shared printer on the client.

In the first case, an administrator installs the driver directly on the terminal server. Thedriver becomes available to all terminal server clients. In the second case, the driver is

installed via point and print from the client while the client is in a terminal session. The

driver gets installed on the terminal server and will be available to the client only.

Note: The administrator can also install the printer on the server via point and print and

make it available to all users.

In addition to these two methods, with Windows 2000 Terminal Services, you have two

additional types of printing.

1. The printer is installed on the server and client. The session is auto-created / auto-

redirected when the user logs into a terminal session.2. The printer is installed on the client and the administrator manually creates /

redirects a printer on the server to the client.

In the sections to follow we will take a look at each of these methods.

Scenario 1: Printer installed on the server / print device is local to the server

In our first scenario we are running Windows NT or 2000 Terminal Server and the printeris local to the Terminal Server. This is a very basic setup and does not require a large

amount of focus on configurations in order to implement. All you would be required to

do is install the printer on the Terminal Server and direct the port to the locally attached

print device. This would mean that either the printer driver on the server is using a LPTport, LPR port, TCP/IP port, etc. that connects directly to the print device.

When any client connects to the Terminal Server through a terminal session, all printersinstalled on the server will be available to them. They can launch an application and print

to the servers locally attached printer just as if they were sitting at the console of the

server. In this scenario, the print job is rendered and spooled only on the terminal serverand then sent directly to the printing device.


9/48


This scenario works well in an environment where the printer and the terminal client user

are both located at the same physical location and the client does not need access to alocally attached printer on the client terminal / PC. Because users will only have access to

the print devices that are locally attached to the server, they should be able to physically

walk up the print device that is providing their output. Please refer to figure 1-1 and 1-2

for a graphical explanation of this scenario.

Note: This scenario applies to Windows NT and 2000 Terminal Servers.

Terminal Client / PC Terminal Server Print Device

Printer installed

Figure 1-1 Printer installed on the server / print device is local to the server.

Terminal Client / PC

Terminal Server

Print Device

2

Spooler

1

4

3

Figure 1-2 Scenario layout.

1. The client connects to the Terminal

Server creating a Terminal Session.

2. The user launches an application from

within their terminal session (application is

launched on the server) and selects file/print.

3. The file gets rendered and spooled on the

server and is then sent to the printing device.

4. The data is outputted from the printing

device.


10/48


Scenario 2: Printer installed via point and print / print device is local to the client

In our second scenario, we will see how to allow the client to access a print device that is

locally attached to the clients terminal / PC.

In this scenario, the terminal client will have asharedprinter installed on the local

machine and will be directing its output to its locally attached print device via LPT, LPR,

etc. You will then connect to the terminal server via a terminal session and install theprinter on the server via point and print. This will create a network printer on the terminal

server that is pointing to the shared printer on the terminal client. When the terminal

client user connects to the terminal server, they will then be able to print to their locallyattached print device. In this case, the terminal client / PC is acting as the print server.

In this scenario the terminal client user will launch an application from within a terminalsession. They will then select file/print and the job will be rendered and spooled on the

printer installed on the server. Because the printer was installed on the server asnetworked printer that is pointing to the shared printer on the client, the output will be

sent to the terminal client / PC and get spooled on the shared printer. Because the sharedprinter on the client is configured to communicate directly to the printing the device, the

print data stream is then sent directly to the printing device.

This scenario is beneficial in an environment where the terminal client user needs to be

able to print to a locally attached printer. Because of the way point and print works, this

scenario is not ideal over a WAN/Internet. This situation is ideal when the terminal clientuser is located within the same network infrastructure as the Terminal Server and needs

access to a local printer connected to their workstation while in a terminal session. Pleaserefer to figure 2-1, 2-2, and 2-3 for a graphical explanation of this scenario.

Note: This configuration assumes that the client has the appropriate permissions/rights toinstall printers on the server. If they do not, the administrator will have to install the

driver on the server via point and print.

Note: This scenario applies to Windows NT and 2000 Terminal Servers.

Terminal Client / PC Terminal ServerPrint Device

Printer installed

Printer installed

Figure 2-1 Printer installed via point and print / print device is local to the client.


11/48


Terminal Client / PC Terminal Server

Print Device

2

1

3


Terminal Client / PC Terminal Server

Print Device

2

Spooler

Spooler

1

5

4

3


1. The client connects to the terminal

server creating a terminal session.

2. The user opens network neighborhood

from within the terminal session and

browses to the installed/shared printer on

the client PC.

3. The user connects to the shared printeron the client machine, which results in

the driver being installed on the server

(point and print).

1. The terminal client user connects to the

terminal server via the terminal server

client.

2. The user launches an application fromwithin the terminal session and prints.

3. The job is rendered and spooled on the

server and sent to the clients sharedprinter.

4. The job is spooled on the client andthen sent to the print device.

5. The job is outputted at the print device.


12/48


Scenario 3: Windows 2000 Auto-create / Automatic Printer Redirection

Windows 2000 Terminal Services provides automatic queue creation / automatic printer

redirection. The queue creation / printer redirection is an automated process providing

that the terminal client / PC has the same print driver installed locally as the Windows

2000 Terminal Server. Any printer that is attached to the client via LPT, COM, or USBwill be automatically detected as long as the same print driver installed on the terminal

client is installed on the Terminal Server that it is connecting to. When the client logs in,

a printer / queue will be automatically created for that users terminal session. This auto-created queue will automatically redirect its output to the locally attached (LPT, COM,

USB) printer on the client. When the client disconnects or ends the session, the printer

queue is automatically deleted and all pending print jobs are terminated.

In this scenario the terminal client user will launch an application from within a terminal

session. They will then select file/print and the job will be rendered and spooled on theserver using the auto-created / auto-redirected print queue. The spooled file will then be

sent to the locally attached LPT, COM, or USB printer installed on the terminal client.From there, the data-stream will be spooled and sent to the printing device that is attached

to the client.This scenario is gaining popularity in situations where the client is remotely connected to

the terminal server via the Internet / WAN and wants to print to a printer that is local to

the client.

Please refer to figure 3-1, 3-2, and the following Windows 2000 Auto-Create /

Automatic Printer Redirection Configuration Guide for a graphical explanation of thisscenario. We will see how to configure this scenario step by step. In addition, to having

the printer auto-created / automatically redirected for the local printer attached via LPT,COM, or USB, we will then take it one step further and also see how to work around the

limitation of printing to only LPT, COM, and USB attached printers. We will use the net

use command to enable us to use this technology to print to the terminal clients localprinter that is not configured with a LPT, COM, or USB connections. This will require

an additional printer to be installed on the client.

Note: Citrix Metaframe natively supports auto printer creation / auto printer redirectionfor all printers that are local to the client regardless of the port configuration. The

following configuration guide will show you how this can be implemented with Windows

2000 Terminal Server with just a few extra configuration steps.

Note: Automatic Printer redirection is supported on all Win32 client platforms, including

Windows 95, Windows 98, and Windows NT and can be disabled on a per-connectionbasis using Terminal Services Connection Configuration or on a per-user basis using

Active Directory Users and Computers or Local Users and Computers.

Note: Print administrators can see all redirected printers, both on the server and those

redirected from their session while normal users can see normal printers on the server and

only their own redirected printers.


13/48


Note: Redirected printers appear in the Printers folder in Control Panel.

Note: If a printer driver is not found on the server, an event is logged and the client

printer is not created. To make the printer available, the driver must be manually installed

on the server.


Internet

Printer installed

Printer installed

Figure 3-1 Windows 2000 Auto-create / Automatic Printer Redirection

Terminal Server

Print Device

2

Spooler

Spooler

Spooler

1

5

4

3LPR Port


LPT Printer Installed


1. The user connects to the Terminal

Server with the terminal server client,creating a terminal session. The printer

queue is auto-created / auto-redirected.


within the terminal session and selects

file print.

3. The file is spooled on the server and the

job is then redirected to the client PC.

4. The job is spooled on the LPT printer

that is installed on the client and printed.

Note: If the print device is not attached

with a LPT, COM, or USB port on the

client, we will install an additionalsharedprinter and use the Net Use

command to redirect lpt1 on the client tothesharedprinter installed on the client.

5. The job is spooled on the shared network

printer (installed on the client) and then

directed to and out utted at the device.


14/48


Scenario 4: Windows 2000 Manual Printer Redirection

In our fourth scenario we will take a look at another feature that is specific to Windows

2000 Terminal Server Services. This scenario is ideal when you have a remote user who

wants print to their local printer while in a terminal session, but they are not using adriver that is compatible with the Terminal Server. For example, lets say when you are at

home you use the RPCS driver to print to your AP 2610N that is connected via a LPT

port. When you connect to the terminal server at the office, you want to be able to print toyour locally attached AP 2610N. However, when you connect to the Windows 2000

Terminal Server at the office with the Terminal Services Client, you never get a printer

auto-created. After doing some research, you realize that the RPCS driver is notsupported on Windows Terminal Servers and therefore the Network Administrator at the

corporate office is not going to install it on the server.

The way that you could get around this situation is by having the administrator manually

create / redirect a printer for your session. For example, the Network Administrator at thecorporate office can install a generic print driver on the server and have it redirect its

output to your local RPCS printer, which will in turn send the output to the print device.

In this case, the printer is manually installed / redirected using the Add Printers wizard.

The client computer name is used to select the printer port from the list of available ports.After the initial manual redirection, printers are automatically redirected during

subsequent logon sessions.

Please refer to figure 4-1, 4-2, 4-3, and the following Windows 2000 Manual Printer

Redirection Configuration Guide for a graphical explanation of this scenario. We willsee how to configure this scenario step by step. In addition, to having the printers

manually redirected for the local printer attached via LPT, COM, or USB, we will then

take it one step further and also see how to work around the limitation of printing to onlylocally attached printers. We will use the net use command to enable us to use this

technology to print to a local networked printer on the client from within a terminal

session.

Note: Terminal Server Services does not support manualredirection of printers

connected through USB ports (only LPT and COM).


Internet

Printer installed

Printer installed

Figure 4-1 Windows 2000 Manual Printer Redirection


15/48



Terminal Server

2

Spooler

1

3



Terminal Server

Print Device

2

Spooler

Spooler

Spooler

1

5

4

3LPR Port




1. The user connects to the Terminal

Server with the terminal server client,creating a terminal session. The user

then calls the Network Administrator so

that he can manually install / redirect aprinter for the users session

2. The Network Administrator manually

installs and / or redirects a printer to theusers session using Add Printer or

editing the properties of an existing

printer.

3. The printer is created and will redirect

its output to the LPT printer installed on

the client.

1. The user connects to the TerminalServer with the terminal server client,

creating a terminal session.


within the terminal session and selects

file print.

3. The file is spooled on the server and thejob is then redirected to the client PC.

4. The job is spooled on the LPT printer

that is installed on the client and printed.

Note: If the print device is not attached

with a LPT, COM, or USB port on theclient, we will install an additional

sharedprinter and use the Net Use

command to redirect lpt1 on the client tothesharedprinter installed on the client.

5. The job is spooled on the shared network

printer (installed on the client) and thendirected to and outputted at the device.


16/48


Configuration Guides

W2K Auto-Create / Automatic Printer Redirection Configuration Guide:

This configuration guide will walk you through the implementation of printing to a localLPT printer while connected to a remote Windows 2000 Terminal Server. In addition to

printing to a local LPT printer, this configuration guide also explains how to redirect the

LPT output to a non-LPT printer.

The following is performed on theServer:

1. Make sure you are running Terminal Server Services on your Windows 2000 Server.

Note: On Windows 2000 Server you can simply add the Terminal Server Service fromwithin Add / Remove programs if it is not already installed

2. Launch the Terminal Services Configuration tool on the terminal server and open up

the properties for the RDP-Tcp connection (notice that the RDP type indicates that it is

RDP 5.0).


17/48


3. Select the Client Settings tab and make sure that Windows printer mapping, LPT portmapping, and Connect client printers at logon is unchecked. Notice that Windows

printer mapping is also an option. To follow is an explanation between LPT port

mapping and Windows printer mapping.

Note: You can disable printer redirection by using Terminal Services Group Policies, or

on a per-connection basis by using the Terminal Services Configuration utility.

Connect client printers at logon: Select the check box to automatically

reconnect to all mapped local client printers while logging on.

Default to main client printer: Select the check box to automatically print to the

default printer of the client. Otherwise, the default printer of the server is used as

the default printer for all client sessions.

Windows printer mapping: Select the check box to disable client Windows

printer mapping. By default, this feature is enabled. When enabled, clients areable to map Windows printers and all client printer queues are automatically

reconnected at logon. However, when both LPT and COM port mappings aredisabled, you will be unable to manually create printers. When disabled, clientsare unable to map Windows printers and client printer queues are not reconnected

at logon. However, you will be able to manually reconnect printers if LPT port

mapping or COM port mapping is enabled.

LPT port mapping: Select the check box to disable client LPT port mapping. By

default, this feature is enabled. When enabled, client LPT ports are automatically


18/48


mapped for printing and are available in the port list of the Add Printer wizard.

You need to manually create the printer to the LPT port using the Add Printerwizard. When disabled, client LPT ports are not automatically mapped. You will

be unable to manually create printers using LPT ports.

4. You will first install the driver on the server. When you install it on the server you willinstall it as a local printer.

5. When you install the printer on the server, you will need to configure it with a inactive

TS (Terminal Server) port. This port is going to allow the auto-create/automatic

printer redirection.


19/48


6. The printer does not need to be shared.

7. The printer is installed on the server configured with a TS port.

The following is performed on the client:

8. On the client you will install the same printer locally.


20/48


9. Because W2K will only map printers that are configured with a LPT port, you willhave to install this first printer using LPT1 for the port.

10. The printer does not need to be shared.

11. The first printer on the client is installed and configured with a LPT port.


21/48


12. You will then start the installation of the second local printer on the client.

13. In this example we are going to point this printer to the printing device using a LPRport.

Note: You can use any network port in this step to point the printer to theprinting device (i.e. UNC path, TCP/IP port, etc.).

14. Install the necessary information for LPR printing.


22/48


15. This printer must be shared. We will later use the net use command that will require

the share name. Take note of the share name in this step.

16. The second shared printer is installed and configured with a LPR port pointingdirectly to the printing device.


23/48


17. In this step you will need to find out the computer name for the client machine. Wewill be using the net use command that will require the computer name.

Note: In Windows 2000 you may see the FQDN (Fully Qualified Domain Name) beingindicated as the Full computer name. In this instance you would take note of the

hostname / host portion of the FQDN. In our example it is win2000proa.


24/48


18. We will now go to a command prompt and map the lpt1 port to your shared printerusing the net use command. The syntax we will use is the following: net use {port}

\\{client computer name}\{printer share name}

Note: If you want to make sure that you have correctly mapped your lpt port on the

client to the network shared printer, you can print a test page from the first (lpt)printer that was installed on the client. The output for the test page should print on the

networked printing device.

Note: For Windows NT, you may have to use the following command: net use lpt1\\computername\printer /persistent:yes

Note: For Windows 95, Windows 98, and Windows ME perform the following: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 will enable

you to select the LPT port that you want to map to this network path.

Note: Because you are using a UNC (Universal Naming Convention) path to the

share, you may be required to have a NetBIOS compatible protocol running on theclient. On a windows PC, you can run NetBEUI, enable NetBIOS over TCP/IP, or use

a WINS server.

Note: If you ever want to remove the mapping that you just created with the net usecommand, you can enter the following command from a command prompt: net use

lpt1: /delete


25/48


19. From the terminal client / client PC, launch the Terminal Services Client.

20. Select the Terminal Server you want to connect to from the Available Servers list.

If there is more than one terminal server, make sure you select the server that containsthe driver installed in step 3.


26/48


21. Once connected, login with your user account to the terminal server. Once you login,

you are then within a terminal session.

22. Launch an application from within your terminal session. In our example we

launched a test Microsoft Word document and selected File/Print. Notice that you

have two printers available to you. The first printer in the list is the printer that wasconfigured with a TS port. The second printer is the auto-created / auto re-directed

printer. The printer name will indicate the clients computer name and terminal session

ID (i.e. Ricoh Aficio 1035 PCL 5e/WIN2000PROA/Session 2).


27/48


Note: Clients see only their own redirected printers in the Printers dialog box.

23. To confirm that the configuration is working as we expected, you can open each

printer prior to printing the job (the auto-created printer within the terminal sessionand the two printers on the client). When you print the job, you should see the job go

through each queue as it is printed.


28/48


A Look Behind The Scenes:

1. This screenshot is taken from the terminal servers printers folder. It displays that

printer that was auto-created when the user logged in. Notice that it indicates in theprinter name, the users computer name and session ID.

2. As soon as the user logs off its terminal session, the auto-created printer isautomatically deleted and the TS printer is indicated as inactive by its grayed out

icon.

Note: When a client disconnects or ends the session, the printer queue is deleted and any

incomplete or pending print jobs are lost. Information about the client's local printers and

settings are saved on the client computer. During subsequent logon sessions, the printer

queue is created using the information stored on the client computer.


29/48


The following are events that will be logged within event viewer when the a user logs

onto the Windows Terminal Server with the Terminal Server Client and a printer is

successfully auto created:


30/48


When a user logs off the Terminal Server ending their terminal session, the auto-created

print queue will automatically be deleted. The following are events that will be logged

within event viewer when the user logs off the Windows Terminal Server:


31/48


The following event will be logged in event viewer when a successful print job is sent

through a auto-created / redirected printer:


32/48


W2K Manual Printer Redirection Configuration Guide:

This configuration guide will walk you through the implementation of printing to a local

LPT printer while connected to a remote Windows 2000 Terminal Server. In addition to

printing to a local LPT printer, this configuration guide also explains how to redirect the

LPT output to a non-LPT printer.


1. The first step is to install the printer on the client terminal / PC. This printer will be alocal printer.

2. Because W2K can redirect jobs to a printer configured with a LPT port, we are goingto configure this printer with a LPT1 port.


33/48


3. This printer does not need to be shared.

4. The print driver is installed on the client terminal / PC and is configured with a LPT1port.


34/48


5. The user will then connect to the Windows 2000 Terminal Server using the Terminal

Services Client.


35/48


6. Notice that there is no auto-created / auto redirected print driver available from the

printers list. This is because the only driver that is installed on the server is a 1075 PS

driver. We connected to the server with a 1045 RPCS driver installed locally. In thisexample we currently do not have any available printer to print to. The 1075 PS printer

is a printer that is local to the server. We need to print to our local Aficio 1045 printer.At this point the user will have to call the Network Administrator and ask him to

manually install / redirect a printer that we can use.


36/48


7. The user will have to provide the administrator with the computer name for the

terminal / PC that he / she is using. The network administrator will use the computername to manually redirect the printer on the server to the printer on the client terminal /PC.

Note: In Windows 2000 you may see the FQDN (Fully Qualified Domain Name) being

indicated as the Full computer name. In this instance you would take note of thehostname / host portion of the FQDN. In this example we will supply the administrator

with the computer name of scanpc1.


37/48


The Network Administrator performs the following on the server:

8. On the server we only have one printer installed (1075 PS) that is of no use to the

terminal client / PC user.

9. In this step we will add a local printer on the server using the Add Printer wizard.


38/48


10. In this step, you will need to select a TS port based on the terminal client / PC that

needs a printer to be redirected. This is where you will need the computer name that

you took note of in step 7. The TS port description is based on the computer name ofterminal client / PC. This is the reason why you must be within a terminal session in

order for the Network Administrator to manually redirect a printer from the server.

The TS port is created when the user logs in. When the terminal server has no activesessions, all of the TS ports will indicate inactive TS Port within the port

description.


39/48


11. Because we do not want to install the same driver on the server that we have on theclient, we may want to install a basic driver to just give the terminal client user basic

printing functionality. In this example, we will install the HP LaserJet 5Si driver.


40/48


12. This printer does not need to be shared.


13. In order to print to a networked printer that is local to the client, we will need toinstall an additional local printer on the client.


41/48


14. In this example we are going to point this printer to the printing device using a

Standard TCP/IP port.

Note: You can use any network port in this step to point the printer to the

printing device (i.e. UNC path, LPR port, Novell queue etc.).

15. This printer must be shared. We will later use the net use command that will requirethe share name. Take note of the share name in this step


42/48


16. The second shared printer is installed and configured with a Standard TCP/IP port

pointing directly to the printing device.

17. In this step you will need to find out the computer name for the client machine. We

will be using the net use command that will require the computer name.

Note: In Windows 2000 you may see the FQDN (Fully Qualified Domain Name) being

indicated as the Full computer name. In this instance you would take note of the

hostname / host portion of the FQDN. In our the computer name is scanpc1.


43/48


18. We will now go to a command prompt and map the lpt1 port to your shared printer

using the net use command. The syntax we will use is the following: net use {port}

\\{client computer name}\{printer share name}

Note: If you want to make sure that you have correctly mapped your lpt port on the

client to the network shared printer, you can print a test page from the first (lpt)printer that was installed on the client. The output for the test page should print on the

networked printing device.

Note: For Windows NT, you may have to use the following command: net use lpt1

\\computername\printer /persistent:yes

Note: For Windows 95, Windows 98, and Windows ME perform the following: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 will enable

you to select the LPT port that you want to map to this network path.

Note: Because you are using a UNC (Universal Naming Convention) path to the

share, you may be required to have a NetBIOS compatible protocol running on theclient. On a windows PC, you can run NetBEUI, enable NetBIOS over TCP/IP, or use

a WINS server.

Note: If you ever want to remove the mapping that you just created with the net

use command, you can enter the following command from a command prompt:

net use lpt1: /delete


44/48


19. The user that is connecting via the Terminal Services Client will now have the HP 5

SI printer available to them. This printer will redirect the print job to the terminal

client / PC from the server which will then be redirected to the shared printer on the

client and then outputted on the print device.


45/48


20. To confirm that the configuration is working as we expected, you can open each

printer prior to printing the job (the HP5SI queue on the server and the two Aficio

1045 RPCS queues on the client). When you print the job, you should see the job go

through each queue as it is printed.


46/48


Questions You Should Ask

In my experiences, I have found that if you probe the customer correctly you can usually

get a pretty good grasp of the scenario / configuration that they have implemented and /

or trying to implement. To follow are some suggestions of the questions you may want

to ask a customer who is having a issue with a Ricoh product in a terminal serverenvironment. These questions can be useful when escalating an issue or to act proactively

before visiting the site.

1. What version of Terminal Server are you running?

2. What Operating System are the Server and the client machine running?

3. What terminal server client software and version number is the customer using toconnect to the terminal server?

4. Is Citrix MetaFrame also installed on the terminal server?

5. Is the print driver installed on the server?6. Is the print driver installed on the client?

7. Was the same exact print driver used on the server and the client?8. How was the print driver installed on the server / client?

9. What version are the print drivers that have been installed?10. Is the driver the latest driver posted on the Ricoh-USA website?

11. Is the printing device local to the server or is it local to the client?

12. How is the port configured for the printer on the server?13. How is the port configured for the printer on the client?

14. What medium is the client using to connect to the terminal server (i.e. LAN,

WAN, Internet, etc.)15. What indications does the event viewer give as the possible cause of the problem?

16. Have you tried the mini driver? If so, did this driver work?17. Can you print to the printing device from the servers console?

18. Does the problem only occur when you are within a terminal session?

19. Can you print to the printing device from a normal PC that is not being used as aterminal server/terminal client?

20. Windows 2000 Terminal Servers What is enabled / disabled in the following

screen: Terminal Services Configurations \ Connections \ RDP-TCP Properties \

Client Settings.


47/48


Ricoh Products Support Status

Server WIndows2000 Terminal Server Services

PCL5e/c PCL6Driver

Mono Mini Mono

RPCS PS

AP 1400/2000 NG OK NG N/A OK

AP1600/2100 OK (V1.3.0.0 or later) OK OK (V1.3.0.0 or later) N/A OK

AP 2700 NG OK NG N/A OK

AP 3200 OK (V1.0.0 or later) OK OK (V1.0.0 or later) N/A OK

AP 4500 NG OK OK (V1.5.0 or later) N/A OK

Aficio 401 N/A N/A N/A N/A N/A


Aficio 350/355/450/455 NG OK OK (V1.8.0 or later) N/A OK

Aficio 650 NG OK NG N/A OK

Aficio 150/180 NG OK NG N/A OK

Aficio 220/270 NG OK OK (V1.2.0 or later) N/A OK

Aficio 350e/355e/450e/455e NG OK NG N/A OKAficio 551/700 OK (V1.0.0 or later) OK OK (V1.0.0 or later) N/A OK

Aficio 850/1050/1085/1105 OK (V1.3.0 or later) OK OK (V1.3.0 or later) N/A OK

AP 2600N OK (V1.0.0 or later) OK OK (V1.0.0 or later) NG OK

Aficio 1035/1045 OK (V1.0.0 or later) OK OK (V1.0.0 or later) NG OK

AP 3800C OK (V1.0.0 or later) N/A N/A NG OKAficio 1022/1027/1032 OK (V1.0.0 or later) OK OK (V1.0.0 or later) NG OK

AP 4510 OK (V1.0.0 or later) OK OK (V1.0.0 or later) NG OK

AP 2610/2610N OK (V1.0.0 or later) OK OK (V1.0.0 or later) NG OK

Aficio 120/FX12/1013 OK (V1.0.0 or later) OK OK (V1.0.0 or later) N/A TBA

Aficio 1015/1018 OK (V1.0.0 or later) OK OK (V1.0.0 or later) N/A TBA

Server Windows2000 Terminal Server Services

Driver IPDL-C RPS

AP 204 NG OK

AP 206 NG OK (V1.00 or later)

AP 305 NG OK


RC-200 NG OK

RC-210 NG OK

PCL: Supported with all models by Mono driver from the AP2600N and onward. Models earlier than

the AP2600N are supported by the Mini driver (with some exceptions).

PS: Supported with all models by using the MS driver (except the Aficio 200 and the Aficio 401).

RPS: Supported with all models by using the MS driver.

RPCS and IPDL-C: Not supported

Note: At the time of this writing, Ricoh

Corporation was in the process of creating a

Windows Terminal Server / Citrix

MetaFrame Support Statement that will be

posted on the Ricoh-USA website

(www.Ricoh-USA.com). Please refer to the

website for the latest information.


48/48

Server Windows NT 4.0 Terminal Server Edition

PCL5e/c PCL6Driver

Mono Mini Mono

RPCS PS

AP 1400/2000 NG OK NG N/A OK

AP1600/2100 OK (V1.3.0.0 or later) OK OK (V1.3.0.0 or later) N/A OK

AP 2700 NG OK NG N/A OK

AP 3200 OK (V1.0.0.0 or later) OK OK (V1.0.0.0 or later) N/A OK

AP 4500 NG OK OK (V1.50 or later) N/A OKAficio 401 N/A N/A N/A N/A N/A


Aficio 350/355/450/455 NG OK OK (V1.80 or later) N/A OK

Aficio 650 NG OK NG N/A OKAficio 150/180 NG OK NG N/A OK

Aficio 220/270 NG OK OK (V1.20 or later) N/A OKAficio 350e/355e/450e/455e NG OK NG N/A OK

Aficio 551/700 OK (V1.00 or later) OK OK (V1.00 or later) N/A OK

Aficio 850/1050/1085/1105 OK (V1.30 or later) OK OK (V1.30 or later) N/A OKAP 2600N OK (V1.00 or later) OK OK (V1.00 or later) NG OK

Aficio 1035/1045 OK (V1.00 or later) OK OK (V1.00 or later) NG OK

AP 3800C OK (V1.00 or later) N/A N/A NG OKAficio 1022/1027/1032 OK (V1.00 or later) OK OK (V1.00 or later) NG OK

AP 4510 OK (V1.00 or later) N/A OK (V1.00 or later) NG OK

AP 2610/2610N OK (V1.00 or later) N/A OK (V1.00 or later) NG OKAficio 120/FX12/1013 OK (V1.00 or later) OK OK (V1.00 or later) N/A TBA

Aficio 1015/1018 OK (V1.00 or later) OK OK (V1.00 or later) N/A TBA

Server Windows NT 4.0 Terminal Server Edition

Driver IPDL-C RPS

AP 204 NG OK


AP 305 NG OK


RC-200 NG OK

RC-210 NG OK

PCL: Supported with all models by Mono driver from the AP2600N and onward. Service Pack 6 or

later must be installed on the terminal server.

Models earlier than the AP2600N are supported with the Mini driver (with some exceptions).

PS: Supported with all models by using the Adobe driver.

RPS: Supported with all models by using the MS driver.

Note: At the time of this writing, RicohCorporation was in the process of creating a

Windows Terminal Server / Citrix

MetaFrame Support Statement that will be

posted on the Ricoh-USA website

(www.Ricoh-USA.com). Please refer to the

website for the latest information.

Documents

Terminal Server Printing WithWindows NT/2000 Terminal Server