Info2soft use cookies to help you have a superior and more admissible browsing experience on our website. Privacy Policy
By:
Remote Desktop lets you access and control another Windows computer over a network. But simply connecting isn’t always enough. You may also need to transfer documents, access local drives, or share folders between your local machine and the remote one.
Windows Remote Desktop has built-in options for this, including drive redirection, Clipboard sharing, and network folder access. Which method works best depends on how often you need to transfer files, what type of access is required, and what your security policies allow.
File sharing in Remote Desktop allows users to access or transfer files between a local computer and a remote Windows machine during an RDP session. Instead of uploading files to a cloud service or sending them by email, users can access local drives, copy files, or connect to shared network folders directly within the session.
Windows Remote Desktop supports three common methods for transferring files:
\\server\share) if network connectivity and permissions allow.Note that drive redirection and Clipboard sharing depend on both client settings and remote computer policies. If an administrator has disabled resource redirection through Group Policy, enabling these options on the local client will not restore access.
Windows Remote Desktop provides several ways to transfer files between local and remote computers. You can redirect local drives, enable Clipboard sharing, or access a shared network folder. The steps below cover how to configure each option.
Drive redirection allows a remote computer to access selected drives or folders on your local machine. Once enabled, redirected drives appear in File Explorer during the RDP session.
Step 1. Press Win + R, type mstsc, and press Enter.
Step 2. Enter the remote computer’s name or IP address, then click Show Options.
Step 3. Open the Local Resources tab.
Step 4. Under Local devices and resources, click More.
Step 5. Expand Drives and select the drives you want to share.
Step 6. Click OK, then connect to the remote computer.
After connecting, open File Explorer on the remote computer and go to This PC. The drives you selected appear under Redirected drives and folders. You can copy files between them and the remote computer’s local storage.
Drive redirection settings take effect before the session starts. If you change the selected drives, reconnect to apply the update. Access may also be restricted by Group Policy on the remote computer.
Clipboard sharing lets you copy and paste files and text between your local and remote computers. It is a quick option for transferring individual files without setting up drive redirection.
Step 1. Open Remote Desktop Connection by running mstsc.
Step 2. Click Show Options and go to the Local Resources tab.
Step 3. Make sure Clipboard is checked under Local devices and resources.
Step 4. Connect to the remote computer.
Step 5. Use Ctrl + C and Ctrl + V to copy and paste files or text between the two computers.
Clipboard sharing works for quick, one-off transfers. For larger or more frequent file transfers, drive redirection is a more practical choice.
rdpclip.exe process on the remote computer to restore Clipboard functionality.Network folder sharing gives you access to files from the remote computer without relying on RDP drive redirection. Windows uses SMB (Server Message Block) to allow authorized users to connect to shared folders over a network.
This method is useful when multiple computers need access to the same files, or when you want a shared location that stays available outside of a specific RDP session.
For more background on how SMB works, see our guide to SMB file sharing.
Step 1. Enable Network Discovery and File Sharing
On the computer that will host the shared folder:
Network and Sharing Center to open it directly.
Step 2. Share a Folder With Specific Users
Step 3. Access the Shared Folder From the Remote Computer
\\server\share.Step 4. Map the Network Folder as a Drive (Optional)
If you access the folder regularly, mapping it as a network drive makes it easier to find in File Explorer.
\\server\share.The folder now appears under This PC as a mapped network drive.
If you are deciding between file-sharing protocols, see our comparison of NFS and SMB.
Remote Desktop file sharing can stop working because of incorrect client settings, Group Policy restrictions, network issues, or permission problems. The sections below cover the most common causes and how to fix them.
Local Drives Are Not Showing in Remote Desktop
If your local drives do not appear under This PC on the remote computer, drive redirection may not be enabled or may be blocked by the remote computer’s policy.
First, check your RDP client settings:
mstsc on your local computer to open Remote Desktop Connection.If the drives are still missing, check the Group Policy setting on the remote computer:
gpedit.msc, and press Enter.Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirectiongpupdate /force or restart the remote computer, then reconnect.Copy and Paste Is Not Working
If you cannot copy files between your local and remote computers, Clipboard redirection may be disabled in the RDP client or blocked by policy.
Check the client settings first:
mstsc and click Show Options.If the issue persists, check the Do not allow Clipboard redirection policy under the same Group Policy path above. If it is set to Enabled, Clipboard sharing is blocked and requires an administrator to change it.
Remote Desktop Clipboard Stops Working During a Session
Clipboard sharing can sometimes stop responding mid-session even when it is properly configured. The most common cause is an unresponsive rdpclip.exe process on the remote computer.
To restart it without ending the session:
rdpclip.exe, right-click it, and select End task.rdpclip.exe and click OK.Test copy and paste again after the process restarts. If the problem continues, check whether Clipboard redirection is restricted by Group Policy or remote session settings.
File Transfer Is Slow or Keeps Failing
Large file transfers over RDP can be slow or interrupted due to network latency, limited bandwidth, or resource constraints. Clipboard-based transfers are particularly prone to this.
Try the following:
For frequent or large file transfers, a network shared folder is generally more reliable than Clipboard sharing.
Access to Shared Folders Is Denied
If you can locate a shared folder but cannot open it, the issue is usually related to account permissions, network credentials, or SMB connectivity.
Check the following:
Drive Redirection Is Disabled by Group Policy
In managed environments, administrators may disable drive redirection to prevent files from being copied between local devices and remote sessions. If redirected drives are consistently unavailable, Group Policy is likely the cause.
To check the policy:
gpedit.msc, and press Enter.Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource RedirectionIf it is set to Enabled, drive redirection is blocked. If it is set to Disabled or Not Configured, this policy is not preventing access.
RDP file sharing works well for occasional access within a session, but it was not designed as a long-term file management solution. Drive redirection is session-dependent, Clipboard transfers do not scale, and network folders require ongoing permission management across individual machines. For teams that share files regularly across locations or devices, the overhead adds up.
i2Share is an enterprise file sharing and collaboration platform that addresses these limitations through centralized management. Instead of configuring access machine by machine, administrators manage files, permissions, and sharing policies from a single interface.
A few capabilities worth noting:
If your team regularly transfers files through RDP sessions and finds the process cumbersome or difficult to control, i2Share provides a purpose-built alternative with the access management and security features that RDP file sharing lacks.
To learn more about Info2soft’s data protection and file management solutions, visit Info2soft.
Remote Desktop file sharing is convenient, but it also introduces security risks if not properly configured.
Unrestricted drive redirection, loose folder permissions, and exposed network ports can all create paths for unauthorized access or data loss.
The practices below cover the main areas worth locking down.
Restrict Access to Authorized Users
Drive redirection and shared network folders should only be accessible to users who genuinely need them. Overly broad permissions make it easy for sensitive files to reach the wrong people, even unintentionally.
A few practices that help:
Secure the Network Connection
RDP and SMB traffic exposed to the network without proper protection can be intercepted or exploited. A few measures significantly reduce that risk.
For a broader look at reducing access risk, see our guide on zero trust security.
Control Drive and Clipboard Redirection With Group Policy
Drive and Clipboard redirection are useful, but they can also be used to move files in and out of a remote session without visibility or control. In environments where data movement needs to be monitored or restricted, these features should be managed through Group Policy rather than left open by default.
Two policies to review:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection): Set this to Enabled to block local drive access from remote sessions.If users need to transfer files, consider providing an approved shared folder with defined permissions and access logging instead of relying on open redirection.
Do Not Expose RDP and SMB Ports to the Internet
Two ports are commonly targeted in attacks against Windows environments:
TCP 3389 — used by Remote Desktop ProtocolTCP 445 — used by SMB for Windows file sharingLeaving either of these open to unrestricted public access is a significant risk. Ransomware campaigns and brute-force attacks frequently target exposed RDP and SMB services. For a closer look at how these attacks work and how to prepare for them, see our guide on ransomware protection and data recovery.
To reduce exposure:
Q1: Can I Transfer Files Through Remote Desktop?
Yes. Windows Remote Desktop supports file transfers through drive redirection and Clipboard sharing. You can also access network-shared folders through an SMB connection.
Q2: Where Are Shared Drives Located in Remote Desktop?
Redirected local drives appear in File Explorer > This PC on the remote computer, usually under Redirected drives and folders.
Q3: Why Can’t I Copy Files From My Local Computer to Remote Desktop?
Clipboard redirection may be disabled in the RDP client or blocked by Group Policy. Check the Local Resources settings and the remote computer’s Clipboard redirection policy.
Q4: Can I Share a Folder Instead of an Entire Drive?
Yes. You can select specific folders under Local Resources > More when configuring drive redirection. Alternatively, share a folder over the network using SMB.
Q5: Does Remote Desktop File Sharing Work Over the Internet?
Yes. File sharing through Remote Desktop can work over the internet if the remote connection and required resource redirection settings are properly configured. A VPN or Remote Desktop Gateway is recommended for secure access.
Q5: Is File Sharing Through Remote Desktop Secure?
It can be secure when properly configured. Use authorized accounts, restrict drive and Clipboard redirection, enable secure connections, and avoid exposing RDP and SMB ports directly to the public internet.
Windows Remote Desktop offers three practical ways to share files between local and remote computers: drive redirection, Clipboard sharing, and network folder access. Each method suits different situations, and choosing the right one depends on how frequently files need to be transferred, how much access control is required, and what your network environment allows.
For most users, drive redirection is the most reliable option for session-based file access. Clipboard sharing works well for quick, one-off transfers. Network folders are a better fit when multiple computers need ongoing access to the same files.
Whichever method you use, security should not be an afterthought. Keeping RDP and SMB ports off the public internet, applying least-privilege permissions, and managing redirection policies through Group Policy all help reduce exposure without getting in the way of legitimate workflows.
If your team shares files regularly and finds RDP-based transfers difficult to manage or audit, a dedicated solution like i2Share gives you centralized control, granular permissions, and built-in data protection in one place.
For more on Info2soft‘s data protection and file management products, visit our website.
· Enterprise & Mid-market Customers Worldwide.
· Support team available to assist you throughout your trial.
· Start a 60-day free trial or view demo to see how Info2soft protects enterprise data.
