How can I transfer local files over the Internet if I'm using Windows 2000 Server Terminal Services and the Web-based Terminal Services Advanced Client (TSAC)? Use the <I>Microsoft Windows 2000 Server Resource Kit</I>'s Rdpclip utility?

A. Traditionally, the lack of support for file transfers between a Win2K or Windows NT terminal server and RDP clients has been a major shortcoming of Microsoft's terminal services. Most organizations with these kinds of needs have turned to Citrix MetaFrame, which provides a much more powerful and flexible solution than Microsoft's terminal services solutions provide.

Although Citrix still provides a far more robust feature set for client-to-server data exchange, the Rdpclip utility (aka the File Copy utility) levels the playing field a bit by enhancing the existing support for clipboard transfers, thereby giving Win2K terminal servers and their clients the ability to exchange files. To use Rdpclip, you need to install the utility on every terminal server and terminal server client on which you want to use it.

On the terminal servers, run the fxfrinst.bat file, which resides in the resource kit's main installation folder. (This folder's default name is C:\program files\resource kit.)

On the clients, perform the following steps:

  1. Copy the fxfr.dll file to the Terminal Server Client installation folder. By default, this folder is named C:\program files\terminal server client.
  2. Copy the rdpdr.dll file to the Terminal Server Client installation folder. This file replaces the rdpdr.dll that the Terminal Services client installed. (You might want to back up this file before you replace it.)

After you complete these steps, reboot both the servers and the clients. When you view folders or files in Windows Explorer, you'll be able to use standard cut, copy, and paste features (or their Ctrl+X, Ctrl+C, and Ctrl+V keyboard-shortcut equivalents) to copy files between servers and clients. This feature takes advantage of the Terminal Services Virtual Channel architecture by using virtual channels to stream file data between the source and destination system.

Discuss this Article 5

Erik Swenson (not verified)
on Apr 9, 2001
I tried the above suggestion to no avail. I have found the only way to transfer files/folders is to have the full Terminal Services Client software loaded on the workstation and employ the above mentioned Server piece. If anyone knows how to accomplish file/folder transfer without the full TS Client, please enlighten me.
Shean (not verified)
on Nov 19, 2002
There is a third party utility that solves the file transfer problem for both the regular and the web based client(TSAC). Its called WtsFtp and it lets you see your client drives and transfer files between the server and the client. You can find it at http://www.ibexsoftware.com/wtsftp.asp
Jon Snyder (not verified)
on Apr 12, 2001
I tried using the instructions within this article and they may work under a Win 9X environment. However, I am running a Win2K network and all of my terminal clients are windows 2000 professional. In order to copy the rdpdr.dll over the existing file I had to search for it using windows explorer. The Steps to perform for all of trhe clients under Windows 2000 are as follows: 1. Copy the fxfr.dll file to the Terminal Server Client installation folder. By default, this folder is named C:\program files\terminal server client. 2. Copy the rdpdr.dll file to the Terminal Server Client installation folder or c:\WINNT\system32 (if the c:\ drive is the windows 2000 boot partion). This file replaces the rdpdr.dll that the Terminal Services client installed. (You might want to back up this file before you replace it.) This works and is very cool, this surely makes the remote administration easier to use.. Thanks for the info.

Please or Register to post comments.

Upcoming Training

Mastering System Center 2012

During over 6 hours of training you can join John Savill from your computer as he will walk you through the key components and capabilities of System Center 2012, what’s involved in using the components, and the benefit they can bring to your environment.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.