Use these Microsoft-supported checks to separate network-path failures, sign-in errors and Access denied problems while protecting your files and network.
Identify The Error Before You Change Settings
A missing network share is not the same problem as an access-denied message. First note whether File Explorer says the network path cannot be found, asks for a password, shows the host but not the folder, or allows reading while preventing edits. Each symptom identifies a different point of failure: discovery, reachability, authentication, authorization, or file locking. Write down the exact wording and whether the issue happens on one PC or every client. This prevents an unnecessary factory reset or a risky change to Windows security.
Try the same known share from another authorized PC, if available, without modifying the folder. If every user fails, the host or network may be responsible. If only one user fails, compare accounts, stored credentials, and permissions. A new failure after a security update deserves a compatibility review, not an immediate rollback of protection. Use the owner’s approved support channel when the share is maintained by an organization.
Check The UNC Path And Actual Share Name
Windows uses a universal naming convention, or UNC, for ordinary network-share paths. In File Explorer’s address bar, type the two leading backslashes, hostname, another backslash, and share name, for example \\HOME-PC\Projects. Do not replace the share name with an assumed folder location such as C:\Projects. The public name assigned to a folder can differ from the folder’s name on the disk.
Check spelling, spaces, and the correct host computer. If entering only \\HOME-PC displays available shares but the target share fails, focus on that specific share. If the host cannot be reached, work through local connectivity and name resolution first. Microsoft’s File Sharing Over A Network instructions describe how normal Windows sharing is configured.
Verify Both Computers Are On The Intended Network
Two computers can both have internet access without being allowed to communicate with each other. A guest Wi-Fi network may isolate clients by design. A corporate VPN may route company resources through a different network, and a laptop may have switched between a home access point and a phone hotspot. Compare the network each machine is actually using before changing any folder rights.
Where you manage the home network, check its normal router or access-point settings, including whether the guest network isolates other clients. Do not weaken isolation on a hotel or public hotspot. Our Computer Network Guide explains network boundaries, while What Is A Router explains why routing and same-LAN discovery are separate concepts. A trustworthy connection is a prerequisite for sensible home sharing.
Use A Private Profile Only On Trusted Networks
Windows distinguishes Public and Private network profiles. Microsoft describes Private as appropriate where you trust devices on the network, such as a home network you administer. On Windows 11, inspect Settings > Network & internet, select the active Ethernet or Wi-Fi connection, and check the Network profile type. Managed PCs can have policies that limit changes.
If the network is genuinely trusted and local sharing is intended, Private can be appropriate. Do not make an airport, cafe, hotel, or unknown network Private just to make other devices visible. Microsoft’s Essential Network Settings explains the security distinction. Changing the profile does not give an account permission to open a protected folder, so test access again afterward.
Enable Discovery And File Sharing On The Host
On Windows 11, open Settings > Network & internet > Advanced network settings > Advanced sharing settings. Within the Private networks section, review Network discovery and File and printer sharing. Enable them where you intend trusted local sharing. Microsoft’s current sharing guide includes these steps. The labels may vary somewhat by Windows release.
These switches affect sharing and discoverability, not the permission of every individual file. After confirming them, inspect the folder’s actual sharing configuration. On organization-managed machines, follow your IT policy instead of enabling features you are not authorized to use. A network device appearing under File Explorer’s Network section does not itself prove an SMB share is accessible or correctly authenticated.
Confirm The Folder Is Still Shared
On the host computer, locate the original folder, open its Properties, and inspect the Sharing tab and the established share name. Check whether the shared directory was moved, renamed, or stored on an external drive that is no longer attached. A shortcut that points at an unavailable folder is not a reliable substitute. Windows also offers standard sharing controls through File Explorer that may differ across editions.
Avoid creating a second broadly accessible share merely to make a network error disappear. Confirm which users should have access, whether access is read-only or editable, and whether the drive is online. For a NAS, the manufacturer controls the share configuration. Its firmware and account settings may be unrelated to Windows File Explorer’s host-side Sharing tab. Document the existing configuration before changing it.
Distinguish Share Permissions From NTFS Permissions
A Windows shared folder can impose two distinct types of restrictions. Share permissions govern access over the network; NTFS permissions govern the underlying files and directories. Even if an account is permitted at one layer, a restrictive rule at the other can prevent editing or opening a file. This often explains why a share appears in a list but gives Access denied when selected.
On the host, compare the account or group listed in the Sharing controls with the Security tab on the same folder. Grant only the actual access needed, such as Read for a viewer or Modify for an authorized editor. Do not set Everyone to Full Control as a universal workaround. Microsoft’s Effective Permissions Guidance discusses Windows access evaluation and its limits. Ask an administrator before editing access rules on a managed server.
Use The Credentials Recognized By The Server
A Microsoft account, Windows local account, domain identity, and Windows Hello PIN are not interchangeable in every file-sharing dialog. A PIN used to unlock the local PC is not automatically a network password recognized by another host. If the server asks for credentials, use the account identity its administrator has authorized. On a managed domain, obtain the correct username format from IT rather than guessing repeatedly.
Never share passwords through an untrusted troubleshooting website. Confirm the account’s permissions and whether a password was changed recently. If authentication succeeded earlier but now fails only for one person, inspect account status and stored credential entries. A correct username cannot overcome a disabled server, and an accessible server does not grant access to a person who lacks folder permissions.
Remove Only Relevant Stale Credentials
Credential Manager can store information used for network destinations. An old password associated with the host may trigger repeated prompts or sign-in errors. On a Windows PC you administer, open Credential Manager and inspect Windows Credentials for an entry that clearly relates to the failed server. Update or remove only that entry when you have the correct account credentials available.
Clearing all credentials may disrupt unrelated services, especially on a work computer. After a targeted change, attempt the legitimate UNC path again and sign in through the standard Windows dialog. Do not confuse authentication failure with a missing network route. If the account has been locked by too many attempts, further guessing can worsen the situation; ask the owner to review the sign-in records.
Test The Host Name Separately From The IP Address
If the hostname fails to resolve, a share can appear unreachable although the host is online. Where an administrator provides the trusted local address, try the authorized UNC share using that address, for example \\192.168.1.20\Projects. This is an example only; do not assume this address belongs to your device. If the numeric path works but the host name does not, investigate local name resolution or changed host naming.
Check ipconfig for local connection details, but avoid posting complete network configurations publicly. A basic ping HOSTNAME test may show whether ICMP replies are allowed, yet no response does not prove file sharing is blocked. Our Default Gateway Guide and Network Latency Guide clarify routing and diagnostic probe limitations.
Check Port 445 Without Exposing It Publicly
Modern Windows SMB file sharing ordinarily uses TCP port 445. PowerShell’s Test-NetConnection -ComputerName HOME-PC -Port 445 can test reachability to an intended host, when you have permission to test it. A successful result does not prove the folder exists or that the account has access. An unsuccessful result may be explained by host availability, routing, or a firewall rule.
Do not forward port 445 through a home router to the public internet. That exposes a sensitive service unnecessarily. If you need remote access, choose an approved secure VPN or supported remote-file-sharing approach instead. Our NAT Explanation clarifies why internal devices are not automatically public services. Document the test and the exact host before escalating a connection issue.
Inspect The Firewall Narrowly
Windows Defender Firewall applies rules according to the connection’s network profile. An authorized home-share setup may require the built-in File and Printer Sharing rules on the Private profile. If you administer the host, inspect the relevant controls rather than disabling the entire firewall. A managed environment may intentionally block peer-to-peer SMB and require an approved file server.
A temporary firewall-off workaround is not suitable as a final solution. It makes the PC less protected and can mislead you about a credential or permissions issue. Check official Microsoft or your security vendor’s instructions for the exact Windows edition. Record any narrow change, retest the share, and confirm that the host remains protected on Public networks and unrelated destinations.
Understand SMB Signing And Modern Security
Windows 11 security requirements have evolved, and modern releases may require SMB signing or restrict insecure guest authentication. Older NAS appliances that rely on anonymous access can fail to connect even when their folder still exists. Microsoft explains the relevant behavior in its SMB Security Hardening Guide and SMB Signing Documentation. Exact requirements vary by Windows version and edition.
Do not turn off signing or allow insecure guest logons simply because a search result promises a quick fix. Guest access lacks protections required by authenticated signed sessions. Prefer updating NAS firmware and configuring authenticated SMB2 or SMB3 access. If the appliance cannot support modern security, consult its vendor or an administrator about migration to compatible storage. A security refusal is not necessarily a software defect.
Avoid Enabling SMB1 For A Legacy Share
Some old tutorials suggest enabling SMB1 through Windows optional features to restore connection to an outdated server. SMB1 is obsolete and carries substantial security limitations. It is not a responsible general fix for Windows 11 home sharing. A modern share should use appropriate supported SMB dialects, authentication, and protection of traffic.
Check the server’s model and supported protocol versions through its official documentation. Update its firmware where safe and supported. If it cannot operate securely with a current Windows client, transfer data through a controlled migration plan rather than making the entire household network depend on weak protocols. Microsoft’s security hardening guidance outlines the reasons these defaults are intentional.
Read Network Path Not Found And Access Denied Differently
The message Network path was not found, sometimes accompanied by 0x80070035, commonly points toward a wrong target name, absent server, or unavailable path. A repeated username prompt suggests an identity or credential problem, while Access denied to a visible folder often indicates authorization. These are starting hypotheses, not guarantees about every Windows installation or network environment.
Record the exact error rather than applying generic instructions to all conditions. A share mounted on a disconnected external drive can produce a different outcome from a server that rejects the account. The next action should isolate one failure: host reachability, share existence, authentication, or permissions. Avoid random registry edits that modify all network connections when only one documented share is affected.
| Symptom | First Safe Check | Avoid |
|---|---|---|
| Path Not Found | Host And Share Name | Random Registry Changes |
| Repeated Sign-In | Account And Credentials | Guest Logon Workarounds |
| Access Denied | Share And NTFS Permissions | Everyone Full Control |
| Legacy NAS Fails | Modern SMB Compatibility | Enabling SMB1 |
Diagnose A Share That Is Readable But Not Writable
If the folder opens and files can be viewed but nothing can be saved, do not start by changing network discovery. The network and authentication probably worked far enough to access the data. Check whether the folder is intentionally read-only for that user, whether the file is locked by another editor, or whether the host’s disk is full. Saving errors are sometimes application-specific rather than share-level.
Test writing a harmless new document only in a designated test location where you are authorized. If one file cannot be edited but other test files work, inspect its properties and whether it is in use. When no files can be created, ask the owner to review effective permissions. The File System Guide explains storage-level concepts distinct from network delivery.
Differentiate A NAS From Another Windows Computer
A network-attached storage appliance can provide SMB shares, but its user accounts, firmware, encryption options and logs may be administered through the manufacturer’s interface rather than Windows. Check that the device is powered, connected, and reachable through a trusted local network. Verify its configuration through official support and avoid unsupported firmware images.
A NAS that worked with an older operating system may not meet current authenticated SMB requirements. When compatibility is the issue, change the server configuration to support secure connections instead of weakening the Windows client. On corporate networks, IT should decide whether a service is authorized and whether a replacement server or migration is required. Keep the actual file copy backed up before altering storage equipment.
Use A Three-Branch Troubleshooting Decision Tree
If the host cannot be reached, work from the physical connection and correct name through local routing and allowed SMB reachability. If the host can be reached but rejects your sign-in, focus on the permitted account, password and stale credentials. If the sign-in works but the folder denies access, inspect the share and NTFS permissions. This branching prevents wasting time changing controls unrelated to the symptom.
Make only one reversible change at a time, then repeat the same test. If a rule adjustment has no effect, restore the previous setting rather than leaving uncertain exposure in place. The following diagram is a conceptual troubleshooting aid, not a diagnosis of the reader’s particular hardware. A clear record helps support staff replicate the failure safely.
Map A Verified Share Without Confusing It With A Backup
After an authorized share opens successfully, File Explorer may offer a Map network drive option through This PC. Enter the validated UNC path and choose a drive letter if useful. Follow organization policy concerning persistent connections and stored credentials. A mapped drive makes access convenient, but it does not make a separate local copy of the files.
If the server is unavailable, the mapped drive may also be unavailable. Preserve important documents with an independent recovery strategy. Our Incremental Backup Guide explains one way backup software can protect changed content. Never assume synchronization or direct network sharing alone guarantees the ability to recover a deleted or corrupted document.
Confirm The Fix And Preserve Security
Close File Explorer and open the share again using the intended account. Check a harmless read operation, and perform a test write only if the account is supposed to edit data. Where feasible, repeat after a normal reconnect or restart to confirm the behavior persists. The result should satisfy both requirements: authorized users have the access they need and unrelated users remain restricted.
Review whether Network discovery applies only to trusted profiles and whether the firewall, SMB signing and authentication remain enabled. Do not leave broad Everyone Full Control access as a hidden side effect of troubleshooting. For the surrounding network, our Home Wi-Fi Router Security Guide covers complementary protection. Record what worked so future incidents do not repeat risky guesses.
When To Ask IT Or The Storage Vendor
Escalate if the computer is domain-joined, policy-managed, or configured with an unfamiliar NAS or Samba server. Provide a concise report with the approximate time, sanitized UNC path, exact error, Windows release, whether the host is accessible by name or address, and which controlled tests you performed. Never include passwords, private files or authentication tokens in a public support ticket.
If a problem started following a security update, verify the affected server’s supported protocols before reversing any protections. Microsoft and vendor support documentation may describe a secure interoperability remedy. An effective repair restores the intended limited access while preserving authentication, signing, and backups rather than merely suppressing the error dialog.
Frequently Asked Questions
Why Does Windows Say It Cannot Access A Shared Folder?
Common causes include incorrect share paths, unavailable hosts, network isolation, blocked SMB traffic, rejected credentials and insufficient share or NTFS permissions.
Where Is Network Discovery In Windows 11?
On a trusted Private network, check Settings > Network & internet > Advanced network settings > Advanced sharing settings.
Can I Access A Share With The Server IP Address?
An authorized UNC path using a known local address can help distinguish a name-resolution problem from another failure, but do not invent an address.
What Is The Difference Between Share And NTFS Permissions?
Share permissions apply to network access; NTFS permissions apply to the files and folders on disk. Both can affect effective authorization.
Should I Disable Windows Firewall To Fix SMB?
No. Investigate narrowly scoped File and Printer Sharing rules on the correct trusted profile while leaving the firewall enabled.
Should I Turn On SMB1 To Connect An Old NAS?
Avoid enabling obsolete SMB1 as a routine fix. Prefer supported authenticated SMB2 or SMB3 and updated vendor firmware.
Why Does A Shared Folder Keep Asking For Credentials?
The server may need a recognized username and password, or Windows may be using a stale saved credential. A Windows Hello PIN is not always the relevant password.
What Does Error 0x80070035 Mean?
It often indicates a network path could not be found. Confirm the hostname, actual share, network reachability and supported SMB service.
Can Guest Wi-Fi Prevent Windows File Sharing?
Yes. Guest networks can isolate clients by design. Do not remove isolation on an untrusted network merely to make sharing easier.
Is It Safe To Forward Port 445 To The Internet?
No. Do not expose ordinary SMB file sharing directly. Use an approved secure remote-access solution instead.


