HOW TO: Securely Copy and Paste Files Between the Terminal Services Client and the Terminal Server in Windows 2000

Article translations Article translations
Article ID: 309825 - View products that this article applies to.
This article was previously published under Q309825
Expand all | Collapse all

On This Page

Summary

When you use Windows 2000 Terminal Services, you can run your own dedicated sessions on a Terminal server. You can run the Terminal Services client software to connect to Terminal servers and to run line-of-business programs. If you are an administrator, you can use Terminal Services to manage remote computers more easily. This article describes how to securely copy and paste files between the Terminal Services client computer and Terminal server.

Terminal Services Configuration

You can configure Terminal Services network security to use one of the following settings:
  • Low: When you use this setting, data that is sent from the client to the server is protected. The main purpose for this setting is to encrypt sensitive data that moves from the client to the server, such as the user password.
  • Medium: When you use this setting, data that is sent from the client to the server is encrypted, and display information that is sent from the server to the client is encrypted. Both the Low setting and the Medium setting use the Microsoft-RC4 56-bit encryption algorithm.
  • High: When you use this setting, 128-bit encryption is supported after you install the Windows 2000 High Encryption Pack on the Terminal Services client and the Terminal server. You can download the Windows 2000 High Encryption Pack from the following Microsoft Web site:
When you use the default Terminal Services configuration, you cannot copy and paste files between the Terminal Services client and the Terminal server. However, when you use the Rdpclip (Rdpclip.exe) utility that is included in the Windows 2000 Server Resource Kit, you can copy and paste files between the Terminal Services client and the Terminal server.

Install the Rdpclip Utility

To use the Rdpclip utility, complete the following two procedures:
  1. Install the Rdpclip utility on the Terminal server.
  2. Configure the Terminal Services client.
NOTE: These procedures do not work with Terminal Services Advanced Client (TSAC).

Install the Rdpclip Utility on the Terminal Server

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

On the Terminal server, follow these steps:
  1. Install the Windows 2000 Server Resource Kit.
  2. Download the Rdpclip hotfix from the following Microsoft Web site, and then install it:
    http://download.microsoft.com/download/win2000platform/rdpclip/1.0/NT5/EN-US/rdpclip_hotfix.exe
  3. Start Microsoft Windows Explorer, and then locate the Resource Kit folder.
  4. Right-click each of the following files, click Properties, and then click the Version tab to confirm the file version:
    Collapse this tableExpand this table
    FileVersion
    C:\Program Files\Resource Kit\Rdpclip.exe5.0.2205.1
    C:\Program Files\Resource Kit\Fxfr.dll5.0.2064.1
    C:\Program Files\Resource Kit\Rdpdr.dll5.0.2205.1
    NOTE: If you use version 5.1 or later of the Remote Desktop Protocol (RDP) client, the end user will not be able to use the Rdpclip utility to copy and paste files between the user's computer and the Windows 2000 Server-based computer that is running Terminal Services.
  5. Start Registry Editor (Regedt32.exe).
  6. Locate and click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\Clip Redirector
  7. Double-click the Name value, and then type fxrdpclp in the Value data box to replace "rdpclip."
  8. Locate and click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd
  9. Double-click the Startup Programs value, and then type fxrdpclp in the Value data box to replace "rdpclip."
  10. Rename the Rdpclip.exe file in the Resource Kit folder to "Fxrdpclp.exe".
  11. Copy both the Fxrdpclp.exe file and the Fxfr.dll file that are located in the Resource Kit folder to the Windows_folder\System32 folder.
  12. Restart the Terminal server.

Configure the Terminal Services Client

On Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows NT, and Windows 2000 Terminal Services clients, follow these steps:
  1. Copy the Fxfr.dll file from the Resource Kit folder to the Program Files\Terminal Services Client folder.
  2. Rename the Rdpdr.dll file in the Program Files\Terminal Services Client folder to "Rdpdr.pss".
  3. Copy the Rdpdr.dll file in the Resource Kit folder to the Program Files\Terminal Services Client folder.
  4. Start a Terminal Services client session with the updated Terminal server.
  5. Right-click a file in the Terminal Services dialog box and click Copy.
  6. Right-click a location on the desktop of the Terminal Services client and click Paste.



References

For additional information about Rdpclip and TSAC, click the article number below to view the article in the Microsoft Knowledge Base:
278139 Rdpclip and Drmapsrv Are Unsupported with Terminal Services Advanced Client

Properties

Article ID: 309825 - Last Review: September 5, 2012 - Revision: 4.0
Applies to
  • Microsoft Windows 2000 Server
Keywords: 
kbhowto kbhowtomaster KB309825

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com