How to Share Files Between Two Windows Computers on a Network

How to share files between two Windows computers on a network is genuinely straightforward — enable Network Discovery on both machines, share a folder through File Explorer's right-click menu, and the second machine can access it within minutes. Our team at PalmGear has configured this setup across dozens of home and small-office environments, and the process rarely requires anything beyond built-in Windows tools. For anyone building out a well-connected home workspace, our tech tips section covers a wide range of practical Windows guides worth exploring alongside this one.

Windows has included peer-to-peer file sharing through the Server Message Block (SMB) protocol since the early days of networked computing, and the implementation in Windows 10 and 11 is polished enough that most home users can complete a working setup in under fifteen minutes. The process touches three areas: network hardware configuration, Windows sharing settings, and folder-level permissions — each one straightforward when approached in order.

Understanding all the available methods before diving in prevents the most common configuration mistakes. Our team recommends reading through the full picture first, since choosing the right method from the start saves significant troubleshooting time later, particularly for setups where multiple people need different levels of access to the same shared folders.

Hardware and Software Requirements for Network File Sharing

Network Hardware Essentials

The physical foundation of any file sharing setup between two Windows computers is a shared local network, and the quality of that connection directly determines transfer performance. Our team consistently recommends a wired Gigabit Ethernet connection for anyone transferring large files regularly — a Cat 5e or Cat 6 cable between each PC and the router delivers real-world speeds of 90–115 MB/s, which makes moving a 10 GB folder feel nearly instant compared to wireless alternatives. Both machines must connect to the same router or network switch, and the local IP addresses assigned by the router must fall within the same subnet range for Windows discovery to work correctly.

• A router or network switch connecting both PCs to the same local network segment
• Ethernet cables (Cat 5e or Cat 6) for wired connections, or a Wi-Fi 5/Wi-Fi 6 access point for wireless setups
• Both machines running Windows 10 or Windows 11 — mixing versions works but occasionally introduces SMB compatibility quirks
• Windows Defender Firewall configured to allow SMB traffic on port 445 through the Private network profile
• Both computers powered on and connected to the network simultaneously during any active file transfer

Knowing each machine's local IP address is essential during initial setup and troubleshooting — our guide on how to find an IP address on Windows covers every method available in modern Windows, including the Settings app, Command Prompt, and PowerShell approaches. Confirming that both machines sit on the same subnet (typically 192.168.1.x or 192.168.0.x) before touching any sharing settings eliminates the most frustrating early-stage configuration dead ends.

Windows Settings and Prerequisites

Before any files can move between machines, Windows requires three specific settings to be active on both computers simultaneously: Network Discovery must be enabled, File and Printer Sharing must be turned on, and the active network profile must be set to Private rather than Public. Our team frequently encounters setups where one machine is correctly configured but the other remains on a Public profile — a state that silently blocks all sharing without producing a meaningful error message.

Pro tip: Always verify that both PCs display the same network name in Settings → Network & Internet before adjusting any sharing settings — machines on different networks will never see each other regardless of any other configuration changes made.

The complete sequence for enabling sharing on each machine:

1. Open Settings → Network & Internet → Advanced network settings
2. Click Advanced sharing settings and expand the Private profile
3. Enable both Network discovery and File and printer sharing
4. Save changes and repeat the identical process on the second machine
5. Confirm both machines appear in File Explorer under Network within a few minutes of making changes

For environments where printer sharing accompanies file sharing as part of a broader home office setup, our detailed walkthrough on how to share a printer over WiFi on a home network covers the additional printer-specific configuration steps that run in parallel with standard file sharing.

How to Share Files Between Two Windows Computers: Methods for Every Skill Level

The Beginner-Friendly Approach

The fastest method for most home users involves nothing more than right-clicking a folder in File Explorer and working through the Share wizard — no command-line knowledge required, and the entire process takes under five minutes once both machines have Network Discovery enabled. Our team considers this the correct starting point for any new setup because it produces a working result immediately and makes the underlying permission model visible through a clean graphical interface.

• Right-click the folder to share → select Properties → navigate to the Sharing tab
• Click Share, then add the user account that will access the folder from the second machine, or select Everyone for unrestricted local network access
• Set the permission level to Read for view-only access or Read/Write when the second machine needs to save files back to the shared location
• Note the network path shown (e.g., \\DESKTOP-ABC123\SharedDocuments)
• On the second machine, open File Explorer, type the network path directly into the address bar, and press Enter to connect

Mapping the shared folder as a persistent network drive makes it reappear automatically after every reboot, accessible from File Explorer exactly like a local drive. Right-clicking the shared folder in File Explorer on the second machine and selecting Map network drive assigns it a drive letter and handles the automatic reconnection. Our team recommends this step for any setup where file transfers happen more than occasionally, since it removes the friction of re-entering network paths each session.

Advanced Options for Power Users

The Advanced Sharing dialog — accessible through the Sharing tab's Advanced Sharing button — exposes granular permission controls that the standard Share wizard abstracts away, including the ability to set distinct SMB-level permissions that layer on top of the underlying NTFS filesystem permissions. Our experience with small business environments confirms that this dual-layer permission model provides significantly tighter access control when multiple users need different levels of access to the same shared directory structure.

For workflows that extend beyond two Windows machines to include Android devices on the same network, our guide on how to transfer files from PC to Android wirelessly covers the complementary methods that work alongside Windows SMB sharing. Securing sensitive shared folders against unauthorized local network access is a natural next step — our walkthrough on how to password protect a folder in Windows covers the most reliable methods for adding credential-based access gates to any shared directory.

Free vs. Paid: What File Sharing Actually Costs

Built-In Windows Features

Every license of Windows 10 and Windows 11 includes full SMB file sharing capability at no additional cost — there are no premium tiers, no subscription requirements, and no feature gates separating Home from Pro editions when it comes to basic two-machine sharing. Our team has never found a scenario where a home user or small office with two Windows machines needed to spend money to achieve reliable, fast file transfers between those machines. The built-in tooling handles the overwhelming majority of real-world use cases without any gaps.

Third-Party and Cloud-Based Solutions

Third-party tools earn their place when the built-in Windows approach doesn't fit the workflow — specifically when automatic two-way synchronization between machines is the goal rather than simple on-demand folder access. SyncThing is the free open-source option our team recommends most often for this use case, since it handles continuous folder synchronization across two Windows machines with minimal configuration and no cloud routing of data. Resilio Sync is the paid alternative with a more polished interface and slightly faster sync speeds in our testing.

Warning: Cloud sync solutions like OneDrive route traffic through external servers even when both machines sit on the same local network, meaning transfer speeds depend entirely on internet bandwidth — a significant bottleneck when moving files larger than a few gigabytes between two PCs in the same room.

For anyone whose network connectivity situation involves forgotten or misplaced Wi-Fi credentials across multiple devices, our guide on how to find a saved WiFi password on Windows resolves the most common connectivity prerequisite that comes up before any network sharing configuration can begin.

Fixing Common File Sharing Problems on Windows

Network Discovery and Visibility Problems

The single most common problem our team encounters in file sharing setups is one machine failing to appear in the other machine's Network view in File Explorer — a visibility problem with several distinct root causes, each with a clear fix. Windows 10 and 11 both rely on the Function Discovery Provider Host service to populate the Network browser, and this service stops running reliably after some system updates, requiring a manual restart to restore network visibility.

• Function Discovery service stopped: Open services.msc, locate Function Discovery Provider Host and Function Discovery Resource Publication, set both to Automatic startup, then start each service manually
• Wrong network profile: Switch from Public to Private in Settings → Network & Internet — the Public profile blocks discovery by design as a security measure
• Firewall blocking discovery: In Windows Defender Firewall → Allow an app through firewall, confirm that File and Printer Sharing is checked specifically for Private networks
• Mismatched workgroup names: Both PCs must share the same workgroup name (default: WORKGROUP) — verify and align through System Properties → Computer Name on each machine
• SMB 1.0 disabled: Modern Windows installs disable SMB 1.0 by default, which occasionally causes older machines to become invisible — enabling SMB 2.0/3.0 on the older machine resolves this

When network visibility problems coincide with broader performance issues on either machine — sluggish response times, delayed network requests, or services failing to start — our troubleshooting guide on how to fix a laptop that keeps overheating addresses the underlying hardware performance issues that frequently interfere with background networking services on thermally constrained machines.

Permission and Access Errors

Access denied errors during file sharing almost always trace back to one of three causes: the shared folder's NTFS permissions exclude the accessing user account, the SMB share permissions are set to Read when Write access is needed, or Windows Password Protected Sharing is enabled on the host machine without matching credentials available on the second machine. Our team resolves most cases by checking both the SMB Share permissions AND the NTFS Security tab independently — both permission layers must grant access, and the more restrictive of the two always wins.

Tip: When an access error appears during connection, switching from \\ComputerName\ShareName to \\192.168.1.x\ShareName (using the actual IP address) immediately confirms whether the problem is DNS/name-resolution-related or a genuine permission issue — two completely different fixes.

For households or small offices where shared folder access needs to be restricted by user account type — limiting what children or guest accounts can reach across the network — our guide on how to set up parental controls on Windows covers the account-level restrictions that layer cleanly on top of a properly configured file sharing setup.

Advantages and Limitations of Windows Network File Sharing

What Works Exceptionally Well

Windows' built-in SMB file sharing is a genuinely capable solution for the scenarios it was designed to handle, and our team consistently recommends it as the starting point for any two-machine Windows environment before exploring third-party alternatives. The transfer performance over Gigabit Ethernet is essentially wire-speed, the integration with the existing Windows user account system makes permission management intuitive, and the shared folder appears in File Explorer exactly like a local drive once mapped — zero learning curve for daily use.

• No additional software or subscriptions required — complete functionality from built-in Windows components
• Full Gigabit Ethernet speeds achievable — our team regularly records 100+ MB/s transfers on properly configured wired setups
• Mapped network drives persist across reboots and appear seamlessly in File Explorer alongside local drives
• Granular permission control through the combined SMB and NTFS permission system
• Works reliably when mixing Windows 10 and Windows 11 machines on the same network
• Compatible with Windows scheduled tasks and backup utilities that can point to network paths directly

Where Windows Sharing Falls Short

The limitations of Windows' native file sharing become apparent in specific workflows that SMB wasn't designed to handle gracefully, and understanding those gaps helps set realistic expectations before committing to the built-in approach for a production environment. The most significant gap is the absence of automatic synchronization — shared folders provide on-demand access, but files don't stay automatically in sync between machines without a third-party sync layer added on top. Both machines must also be powered on and network-connected simultaneously for any file access to work, which rules out the built-in approach for any workflow requiring always-available storage.

• No automatic synchronization — files must be manually copied or moved between shared locations
• Requires both machines to be powered on and network-connected during any active file access or transfer
• Transfer performance degrades meaningfully on wireless connections when moving files larger than several gigabytes
• Sharing configuration occasionally resets after major Windows feature updates, requiring brief reconfiguration
• Cross-platform access from macOS or Linux requires additional SMB configuration steps on those platforms
• No built-in file access logging — auditing who accessed or modified shared files requires third-party tools

Final Thoughts

Knowing how to share files between two Windows computers on a network is one of the most immediately useful skills in any Windows-centric home or office setup, and our team's consistent recommendation is to start with the built-in SMB sharing method today — enable Network Discovery on both machines, share one test folder, confirm the connection works end-to-end, and build from there. Anyone who completes that first working connection will have the foundation to expand into mapped drives, granular permissions, and more sophisticated sync workflows as their needs grow, and our tech tips section has the companion guides to support every step of that progression.