question: How does File Transfer work over Remote Desktop Connections?
comment: the rdp listening server on the target pc and the rdp client on the host pc establish communications. then when this connection is established it opens up another port for file transfers. as long as you are connected to the RDP server from a RDP client, it can do file transfers regardless of where the pc's are located. you are limited by the internet speeds of the server pc and the client pc.
passages: Section::::History.:Version 5.0.
  
  This version was introduced with Windows 2000 Server, added support for a number of features, including printing to local printers, and aimed to improve network bandwidth usage.
  
  Section::::History.:Version 5.1.
  
  This version was introduced with Windows XP Professional and included support for 24-bit color and sound. The client is available for Windows 2000, Windows 9x, Windows NT 4.0. With this version, the name of the client was changed from "Terminal Services Client" to "Remote Desktop Connection"; the heritage remains to this day, however, as the underlying executable is still named "mstsc.exe".
  
  Section::::History.:Version 5.2.
   To share files, CFT must be installed on each platform. A platform that wants to send a file to a remote partner sends a request over the network by specifying the remote platform through its partner name. When the remote partner receives the request, it verifies that it is the correct destination and creates a record in its local catalogue that lists all requests (treated FIFO). 
   BULLET::::- Writing: When all the replicas have received the data, the client sends a write request to the primary chunk server, identifying the data that was sent in the sending phase. The primary server will then assign a sequence number to the write operations that it has received, apply the writes to the file in serial-number order, and forward the write requests in that order to the secondaries. Meanwhile, the master is kept out of the loop.
   BULLET::::- Sending: First, and by far the most important, the client contacts the master to find out which chunk servers hold the data. The client is given a list of replicas identifying the primary and secondary chunk servers. The client then contacts the nearest replica chunk server, and sends the data to it. This server will send the data to the next closest one, which then forwards it to yet another replica, and so on. The data is then propagated and cached in memory but not yet written to a file.
   Key to FirstClass's operation was the underlying FCP (FirstClass Protocol). FCP was a transport layer networking protocol that all FirstClass communications used. The protocol guaranteed error-free communications for all activities, not just file transfers. FCP could run on several different physical layers, starting with modems and AppleTalk, and later adding Novell's IPX and TCP/IP. Both the client and server could communicate over any of these links, allowing a user to move from office to home and have access to the same server.
   Zinstall Easy Transfer transfers the user workspace from one computer to another. The transfer is done over some form of network connection - router, network, direct cable or a wireless connection. In order to initial the transfer, the user should run the software on old and new computers, which then auto-locate each other on the network. The transfer is then initiated on the new computer. The old computer is not changed and nothing is removed from it.
   Microsoft has a long-standing agreement with Citrix to facilitate sharing of technologies and patent licensing between Microsoft Terminal Services and Citrix XenApp (formerly Citrix MetaFrame and Citrix Presentation Server). In this arrangement, Citrix has access to key source code for the Windows platform, enabling its developers to improve the security and performance of the Terminal Services platform. In late December, 2004 the two companies announced a five-year renewal of this arrangement to cover Windows Vista.
  
  Section::::Architecture.
   In this scenario, the transfer is done directly from one "live" machine to another "live" machine. The transfer is done over some form of network connection - router, network, direct cable or a wireless connection. In order to initial the transfer, the user should run the software on old and new computers, which then auto-locate each other on the network. The transfer is then initiated on the new computer. The old computer is not changed and nothing is removed from it.
  
  Section::::Operation.:Transfer scenarios.:Transfer directly from old PC's hard drive.
   Windows Easy Transfer does not support transferring installed applications. For transferring certain supported applications from Windows XP to Windows Vista, Microsoft had planned to release a supplementary "Windows Easy Transfer Companion" application, but the application remained as a perpetual beta during development, and a final version was never released.
  
  Section::::Transfer methods.
  
  Several transfer methods can be used:
  
  BULLET::::- An Easy Transfer Cable (not supported on Windows 8.1)
  
  BULLET::::- A computer network
  
  BULLET::::- A CD recorder or DVD recorder and sufficient number of CDs or DVDs
   CFT is a licensed product. It is used with a software key that limits the use of CFT to a type of machine and a maximum number of simultaneous transfers. 
  
  In the case of a UNIX Sun Solaris box, the CFT should be installed on both the sender and the receiver machines. There are two main config files for XFB (AXway File Broker) namely locpart.smp and chkusr.txt. locpart.smp stores the destination server's IP address, protocol intended, port to be used and other such information. TCP and FTP are the basic protocols used here. 
   BULLET::::2. Remote Desktop Connection (RDC)
  
  BULLET::::3. Fast User Switching
   Copies of files accessed over MTP may remain on the host computer even after reboot, where they will be accessible to the user account which accessed them, as well as any other user accounts able to read that user account's files, including any administrative users. Windows 7's sensor platform supports sensors built into MTP-compatible devices.
  
  Section::::MTP support.:Unix-like systems.
  
  A free and open-source implementation of the Media Transfer Protocol is available as libmtp. This library incorporates product and device IDs from many sources, and is commonly used in other software for MTP support.
  
  Section::::MTP support.:Unix-like systems.:Graphical.
   Windows Easy Transfer
  
  Windows Easy Transfer is a specialized file transfer program developed by Microsoft which allows users of the Windows operating system to transfer personal files and settings from a computer running an earlier version of Windows to a computer running a newer version.
   Remote desktop sharing is accomplished through a common client/server model. The client, or VNC viewer, is installed on a local computer and then connects via a network to a server component, which is installed on the remote computer. In a typical VNC session, all keystrokes and mouse clicks are registered as if the client were actually performing tasks on the end-user machine.
  
  The target computer in a remote desktop scenario is still able to access all of its core functions. Many of these core functions, including the main clipboard, can be shared between the target computer and remote desktop client.
   Once a client initiates a connection and is informed of a successful invocation of the terminal services stack at the server, it loads up the device as well as the keyboard/mouse drivers. The UI data received over RDP is decoded and rendered as UI, whereas the keyboard and mouse inputs to the Window hosting the UI is intercepted by the drivers, and transmitted over RDP to the server. It also creates the other virtual channels and sets up the redirection. RDP communication can be encrypted; using either low, medium or high encryption. With low encryption, user input (outgoing data) is encrypted using a weak (40-bit RC4) cipher. With medium encryption, UI packets (incoming data) are encrypted using this weak cipher as well. The setting "High encryption (Non-export)" uses 128-bit RC4 encryption and "High encryption (Export)" uses 40-bit RC4 encryption.
   A preliminary version of Windows Easy Transfer was demonstrated during the Windows Hardware Engineering Conference by Jim Allchin in 2004 as the successor to the "Files and Settings Transfer Wizard", and was scheduled for the next client version of the Windows operating system, Windows Vista, then known as Windows "Longhorn". As with the final release, this version of the application was intended to optionally use a specialized USB cable to transfer data between personal computers.
  
  Section::::Items transferred.
  
  For all supported versions of Windows, Easy Transfer can transfer:
  
  BULLET::::- Data files and folders
   Windows Easy Transfer was introduced in Windows Vista and is included in the Windows 7, Windows 8, and Windows 8.1 operating systems. It replaces the "Files and Settings Transfer Wizard" included with Windows XP and offers limited migration services for computers running Windows 2000 Service Pack 4 and Windows XP Service Pack 2. It does not transfer applications, only files and most settings.
   BULLET::::2. BWFS client sends an operating request to MDC through LAN
  
  BULLET::::3. MDC processes this request and responds to the client for which disk blocks can be read in data through LAN.
  
  BULLET::::4. BWFS client directly writes data in file system at line speed.
   Once the final hop accepts the incoming message, it hands it to a mail delivery agent (MDA) for local delivery. An MDA saves messages in the relevant mailbox format. As with sending, this reception can be done using one or multiple computers, but in the diagram above the MDA is depicted as one box near the mail exchanger box. An MDA may deliver messages directly to storage, or forward them over a network using SMTP or other protocol such as Local Mail Transfer Protocol (LMTP), a derivative of SMTP designed for this purpose.
   BULLET::::- Raw UDP socket connection: For use with UDP based applications, terminal servers can convert serial equipment data for transport across UDP packets on a point-to-point basis or shared across multiple devices.
   BULLET::::2. Then the office PC logs into a file server where the needed information is stored.
  
  BULLET::::3. The remote PC takes control of the office PC's monitor and keyboard, allowing the remote user to view and manipulate information, execute commands, and exchange files.
  
  Many computer manufacturers and large businesses' help desks use this service widely for technical troubleshooting of their customers' problems. Therefore you can find various professional first-party, third-party, open source, and freeware remote desktop applications. Which some of those are cross-platform across various versions of Windows, macOS, UNIX, and Linux. Remote desktop programs may include LogMeIn or TeamViewer. 
   Section::::Serial protocols.
   File transfer
  
  File transfer is the transmission of a computer file through a communication channel from one computer system to another. Typically, file transfer is mediated by a communications protocol. In the history of computing, a large number of file transfer protocols have been designed for different contexts.
  
  Section::::Protocols.
   The file chkusr.txt contains information specific to authorization and proxy. If a user is sending files to a receiver, the latter should have an A entry in its chkusr.txt file to authorize the user to send files. It should also contain the landing directory to which the files should be written in the receiving system. The sending machine also has an agent file named filename.perm, where the file name to be sent is configured and which contains the node name.
  
  Section::::Supported operating systems and platforms.
   BULLET::::- on the local machine, open a terminal window
  
  BULLET::::- use ssh with the X forwarding argument to connect to the remote machine
  
  BULLET::::- request local display/input service (e.g., export DISPLAY="[user's machine]":0 if not using SSH with X forwarding enabled)
  
  The remote X client application will then make a connection to the user's local X server, providing display and input to the user.
  
  Alternatively, the local machine may run a small program that connects to the remote machine and starts the client application.
  
  Practical examples of remote clients include:
  