Home	RDP Sales	Contact Us	Training
RDP Support		Open a Web Support Ticket
RDPWin Knowledge Base	RDP-DOS Knowledge Base	IRM and IRM.Net Knowledge Base	Crystal Knowledge Base

Remote Printing is now possible using Carbon Copy 32

Added 11/28/02 - Article ID#: K000117

RDP no longer supports Carbon Copy.  See "Supported Environments" below.

Most RDP Customers have Carbon Copy 32 (CC32) installed on one or more workstations.  RDP Support connects to these workstations for training and problem solving.  It is also possible for the customer to connect from a remote site to these CC32 terminals.   It is now possible for these remote sites to print with RDP software when connected with Carbon Copy 32, as follows:

Setting up a Printer Connected to a Remote Workstation with Carbon Copy 32 

The steps below were produced using Carbon Copy 32, Version 5.70.350.  This version has service pack2 installed, which is available at www.altiris.com/.  Both the source PC and the Destination PC were running Windows 2000 professional.  Remote printing may, or may not, work with earlier version of CC32 and other operating systems.  The Help system built into CC32 has excellent general information on remote printing.  Terms:

• Remote PC  The remote PC that has the printer physically connected to it. 

• Source PC:  The PC at the property 

Before you can start to use Remote Printing, you need to configure both the PC at the property as follows:

To Configure the PC at the Property for Remote Printing in CC32:

The printer driver that will be used on the remote PC must be installed on the PC at the property. These steps assume you are familiar with setting up printers in Windows 2000/XP.  The steps are as follows: 

1. These steps assume the PC at the property is running Windows 2000 professional or Windows XP professional.  Remote printing will not work with RDP DOS if the PC at the property uses Windows 95/98.  Perform these steps from the PC at the property.

2. Before connecting with CC32, select start-settings-printers, and add a printer.

3. Select a "local printer" and uncheck the "automatically detect and install my Plug and play printer". 

4. When prompted for a port, scroll down and find the port labeled "Carbon_Copy_Printer" and select "Next"

5. Select the correct printer manufacturer and printer and select next.

6. As a printer name, enter "Carbon Copy Printer Only", since this printer can only be used when the PC at the property is being controlled via carbon copy from the remote PC.

7. Share the printer.  The default share name of "CARBONCO" will work fine.

8. Do not print a test page

9. Select finish and exit the printer wizard.

Configure A Windows Shared Printer with RDP096

The printer that was installed and shared in the previous section must now be setup in RDP as a windows shared printer (printer number 5-99).  This procedure is document in the RDP Printing Setup.

Testing Remote Printing

To test remote printing with Carbon Copy 32, follow these steps:

1. Establish a CC32 connection between the PC at the property and the Remote PC.  For best performance, a fast TCP/IP connection should be used, however a modem connection will also work. 

2. On the remote PC, bring up CC32 and select Remote Printing, located on the Options menu. In the Remote Printing dialog box, select the destination printer you want to use from the drop-down list.  This printer must be physically connected to an LPT port on the remote computer.  

3. On the remote PC, start CC32 remote Control and CC32 Remote Printing

4. From the remote PC, start the RDP system.  To print from RDPDOS, select the Windows shared printer created with RDP096.  

5. To print from Crystal Reports, RDPWin, or any Windows application, select the printer "Carbon Copy Only Printer".

The techniques described above work, but are tricky to implement.  Please call RDP support at 970-845-7108 if you need additional help. 

Troubleshooting - Windows XP Slow Printing

With Windows XP, Microsoft made a change that delays all DOS print jobs by 15 seconds. To accelerate printing, every computer using any version of Windows XP will need the changes described in the link below. This includes the Windows 2003 data server.  If using Citrix or terminal services, the changes must also be implemented on the Windows 2003 server running Citrix/Terminal Services, as well as each workstation that uses the Windows XP operating system.

• Change LPT_Timeout for faster printing on all Windows 2000/XP Workstations and Servers.

Links to documents related to printing with RDP
Installing and troubleshooting printers.
Remote printing with Terminal Services.
Remote printing with Carbon Copy 32.
USB printing with RDP.
Installing TCP/IP shared printers.
Basic Error 64 Line: 32939 Module: Menu-SrchPath-OutPut-PrScr.
Basic Error 75 Line: 33022 Module: Menu-OutPut-PrScr.

Windows XP Users Must Be a Member of Local Administrator Group

Microsoft added significant local security to Windows XP.  A user with minimal rights does not have access to write files to the "C" drive or to re-direct printing to shared network printers, both of which are required for RDP software to function properly.  To solve this problem, each user of a Windows 2000 or XP workstation must be a member of the administrator group on the workstation, which gives the user complete access and all rights for the local workstation.  Please note that network security is not compromised, since the user must only be a member of the local administrator group on Windows XP workstations.  All RDP users should not be a member of the domain administrator group.  To add a user to the local administrator group, see the link below:

• Windows 2000/XP Users Must Be a Member of Local Administrator Group.

Home	RDPWin	RDP-DOS	IRM/IRM.Net	Open A  Web Support Ticket
	Version 2.xxx	Upgrade to RDPWin	Link to Marketing Site	Contact Us
	Training	Vendor Interfaces	Troubleshooting	RDP Sales Website