Home Windows

Use Windows Explorer to Share Files and Verify Access

Share a file or folder from Windows File Explorer, set who can open or edit it, then verify access from Windows, macOS, Linux, or phones. Includes quick and Advanced Sharing steps, a verification checklist, and fixes for the top networking failures.

11 min read
A laptop screen displaying Windows 11 File Explorer with the Share menu open beside a selected file.

You can share a file or folder from Windows File Explorer and verify access from other devices on the same network. Before you begin, confirm the host PC is on a Private or Domain profile, network discovery is enabled, and firewall rules allow SMB (TCP 445 and 139). The steps below cover Quick Share, Advanced Sharing, cross-platform connections, verification tests, common failures with fixes, and safety advice so you can complete the share and confirm it works.

What you must check before you start

Answer: Verify Windows edition, network profile, host account availability, firewall rules for SMB, and whether SMB versions meet your needs. Do these checks before enabling any share.

  • Windows edition and build: confirm the PC runs Windows 10, Windows 11 or a later consumer/business edition that includes local file sharing. If a corporate policy manages the device, check Settings > System > About and ask IT if policies block sharing.
  • Network profile: set the host to Private or Domain. Public blocks discovery and sharing by default.
  • Host accounts and credentials: decide which host account(s) will get access. Use a local account, a Microsoft account tied to the PC, or a domain account. Create a dedicated local account if you need persistent access for specific people.
  • Firewall and SMB ports: allow the feature named File and Printer Sharing in Windows Defender Firewall or your third-party firewall; these rules open SMB ports TCP 445 and 139. If a router blocks SMB, sharing fails regardless of host settings.
  • SMB version caution: Explorer uses SMB for network shares. Windows defaults to SMBv2/v3; SMBv1 is insecure and usually disabled. Only enable SMBv1 when you have a documented need and follow current Microsoft guidance.

Quick prechecks:

  • Verify the host IP address:
Command Prompt
ipconfig
  • Confirm the firewall rule is allowed:
Settings path
Windows Security > Firewall & network protection > Allow an app through firewall

Quick Share (one-off link or specific people) — exact Explorer clicks

Answer: Quick Share gives a fast, short-lived share or a link for named users. Use it when you want to grant access quickly without creating a persistent SMB share.

  1. In File Explorer, right-click the file or folder you want to share. On Windows 11, choose Show more options then Share or Give access to.
  1. In the Share pane, pick Specific people or the Copy link / contact option shown by your build.
  1. If you choose Specific people, select or type the user, choose Read or Read/Write if available, and click Share.

Expected immediate result:

Expected output
Explorer shows a confirmation and may display the network path (e.g., \\HOSTNAME\SharedFolder) or present a link to copy. The person you added should appear in the share dialog.
Close-up photo of a laptop screen with Windows 11 File Explorer showing the Share submenu and 'Specific people' option.

Advanced Sharing (persistent network share) — exact Explorer steps

Answer: Advanced Sharing creates a persistent SMB share with a defined share name and share-level permissions. Use it when you need a stable network path users can map or browse.

  1. Right-click the folder and choose Properties.
  1. Click the Sharing tab, then click Advanced Sharing....
  1. Check Share this folder.
  1. In Share name, accept the default or type the name users will see on the network (do not use backslashes). Optionally set Limit the number of simultaneous users.
  1. Click Permissions, add the users or groups who should access the share, and select Read, Change (read/write) or Full Control as needed. Click OK.
  1. Back on the Sharing tab, click Close or OK to apply the share.
  1. Use the Security tab on the folder's Properties to confirm NTFS permissions. Adjust NTFS permissions if intended users lack access.

Expected immediate result:

Expected output
The share is available at the UNC path \\HostName\ShareName. The folder's Sharing tab lists the network path and the users or groups with access.
Laptop screen displaying a folder's Properties > Advanced Sharing tab on Windows 11, showing share name and permissions settings.

How share permissions differ from NTFS permissions and how to check Effective Access

Answer: Share permissions control network access; NTFS permissions control disk access. The user gets the most restrictive result when both apply. Check Effective Access to confirm what a specific account can actually do.

  • To change share permissions: Properties > Sharing tab > Advanced Sharing > Permissions.
  • To change NTFS permissions: Properties > Security tab > Edit.
  • To check Effective Access for an account:
  1. Properties > Security tab > Advanced.
  1. Click Effective Access (or Effective Permissions).
  1. Click Select a user, enter the account, then click View effective access.

Recommended pairings:

  • Read-only network access: Share permission = Read; NTFS = Read & execute.
  • Read/write network access: Share permission = Change (or Full Control if you will change permissions); NTFS = Modify or Full control depending on the need.

How to connect to the share from other devices and which credentials to use

Answer: Use the UNC path on Windows, smb:// on macOS and mobile, and SMB tools on Linux. Always supply credentials for a host account that has the permissions you set.

From another Windows PC:

  1. Open File Explorer and type the UNC path in the address bar:
\\HostName\ShareName
  1. If prompted, enter credentials for a host account. Use HostName\User for a local account, or Domain\User / user@domain for domain accounts.

To map a drive:

  1. Right-click This PC > Map network drive... and enter the UNC path. Choose a drive letter and enable Reconnect at sign-in if desired.

From macOS:

  1. In Finder, choose Go > Connect to Server.
  1. Enter:
smb://HostName/ShareName
  1. When prompted, select Registered User and enter Windows account credentials.

From Linux:

  • Using smbclient:
Linux shell
smbclient //HostName/ShareName -U username
  • Using mount.cifs (root required):
Linux shell
mount.cifs //HostName/ShareName /mnt/share -o user=username

From iOS/Android:

  • Use a file manager app that supports SMB. Enter smb://HostName/ShareName and supply the Windows account credentials when prompted.

Credential guidance:

  • Use a host account with the permissions you assigned. Create a local host account or use a domain account if needed. For Quick Share cloud links, the required credentials depend on the cloud feature used; check the share dialog.

Verification checklist and simple tests

Answer: Test listing, reading, writing, modifying, and denied actions from a client device. Also confirm the host shows the share in its Sharing tab.

  1. List files: open \\HostName\ShareName and confirm you see the expected files.
  1. Read test: open a file from the share to confirm read permission.
  1. Write test (if intended): create and save a new file in the share to confirm write permission.
  1. Modify test (if intended): rename or delete a file to confirm modify permission.
  1. Denied-action test: attempt an action that should be blocked (for example, editing when the share is read-only). You should receive a permission denied message.
  1. Confirm host view: on the host, open the Sharing tab for the folder; the path should be listed. On the client, mapped drives should connect or show an authentication prompt if credentials are wrong.

What success looks like:

Expected output
The client lists files, opens files, and performs allowed operations without permission errors. Forbidden actions return `Access denied` or a similar message. The host's Sharing tab shows the share path.

Six common failures and specific fixes

Answer: These six failures cover the most frequent causes and their precise fixes. Follow the listed settings and paths to resolve each issue.

  1. Network profile is Public
  • Fix: Settings > Network & internet > Properties > set Network profile to Private.
  1. File and Printer Sharing is disabled
  • Fix: Control Panel > Network and Sharing Center > Advanced sharing settings > turn on Network discovery and File and printer sharing for Private networks.
  1. Firewall blocking SMB
  • Fix: Windows Security > Firewall & network protection > Allow an app through firewall > enable File and Printer Sharing for Private networks. For third-party firewalls, allow TCP 445 and 139 and any related SMB rules per vendor instructions.
  1. SMB client or server disabled or version mismatch
  • Fix: Turn Windows features on or off and confirm necessary SMB client/server components are available. Do not enable SMBv1 unless you have a documented need and verify current security guidance.
  1. Credential mismatch or cached wrong credentials
  • Fix: Control Panel > Credential Manager > Windows Credentials — remove stored credentials for the host, then reconnect and supply the correct username and password.
  1. NTFS Deny or wrong group membership
  • Fix: Properties > Security tab > Advanced > check for Deny entries and group memberships. Use Effective Access to test a specific account and adjust NTFS or share permissions accordingly.

If the client still shows a removed share, clear cached network connections, disconnect mapped drives, or reboot the client and host as needed.

How to remove or revoke a share and confirm access is revoked

Answer: Unshare the folder, optionally remove permissions, then verify clients cannot connect to the UNC path. Disconnect mapped drives on clients if needed.

  1. Stop sharing the folder: right-click the folder > Properties > Sharing tab > Advanced Sharing > uncheck Share this folder, then OK.
  1. Remove share permissions (optional): Security tab > Edit > remove the users or groups you previously added.
  1. Confirm revocation from a client: attempt \\HostName\ShareName — the response will vary (for example, Network path not found or Access denied).
  1. If mapped drives persist on clients, instruct them to disconnect the mapped drive or reboot. To clear name resolution issues, flush DNS/NetBIOS caches or reboot the host.

Expected result:

Expected output
Clients can no longer access the share. Mapped drives appear disconnected or return an error when accessed.

When to use OneDrive, SharePoint or third‑party sharing instead of Explorer shares

Answer: Use cloud or third‑party services when you need remote access beyond the local network, link expirations, co-authoring, version history, or centralized auditing and management. Migrate when those features matter more than a local SMB share.

Transition checklist:

  1. Copy or move files into OneDrive, SharePoint, or the third‑party service.
  1. Use the cloud UI to create links with expiration or to grant access to specific users.
  1. Revoke the local SMB share once clients have the cloud link to avoid duplicate copies and access confusion.

Safety tips for sharing sensitive files and what to audit

Answer: Prefer per-user access, encrypt sensitive files, use expirations for external shares, and enable auditing when required by policy. Audit only after you plan for log volume and retention.

  • Prefer per-user access instead of Everyone on a local network.
  • Encrypt sensitive files before sharing: use a password-protected archive (ZIP/7z) or platform-recommended encryption. For whole volumes, consider BitLocker. Share passwords by a separate secure channel.
  • Use cloud links with expiration and access controls when sharing with external users.
  • Audit access: enable object access auditing in Local Security Policy or via group policy on Pro/Enterprise systems and review Security logs in Event Viewer. This requires policy configuration and can generate large logs; check current guidance before enabling.

Frequently Asked Questions

What credentials should I use when a client prompts for a username and password?

Answer: Use a host account that has permission to the shared folder. For a local account, use `HostName\User` or just `User` in the same workgroup. For domain accounts use `Domain\User` or `user@domain`. If no suitable account exists, create a local host account or use a cloud sharing alternative.

How do I make a shared folder available only to specific people on the network?

Answer: Create or choose specific Windows accounts on the host, grant only those accounts share permissions, and set matching NTFS Security rights. Then verify Effective Access for each account to confirm they have the intended permissions.