Backups & Storage

Windows network share not accessible

Troubleshoot a Windows file share in order: path, host, network profile, discovery, credentials, permissions, firewall, and SMB safety.

Problem summary

A Windows share is a path plus a reachable host plus credentials plus permissions. The useful fix is to prove which layer failed before changing broad sharing or firewall settings.

Operator snapshotEvidence first

First proof

Try the exact UNC path and write down the error text.

Screen to open

ipconfig /all

Expected signal

\\HOST\Share either opens, prompts for credentials, says access denied, or says the path cannot be found.

Stop boundary

Stop here for work-managed or domain-joined devices.

Layer path

1A Windows share is a layered path: client PC, share path, reachable host, SMB port 445, credentials, share permissions, NTFS permissions, and firewall profile.

2Browsing under Network is convenience. The direct UNC path by hostname or IP is the evidence path.

3Permissions only matter after the host and SMB service are reachable.

4SMBv1, anonymous sharing, public-network sharing, and router port forwarding are safety boundaries, not normal fixes.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Record the exact path and error

Check: Open File Explorer and test the exact path, such as \\OFFICE-PC\Backups. Write down the full error text.

Expected result: You know whether the issue is not-found, credential prompt, access denied, or read-only behavior.

If not: Do not continue from memory. Confirm the host name from Settings > System > About and the share name from folder Properties > Sharing.

Bypass discovery

Check: Try both \\HOST\Share and \\192.168.x.x\Share.

Expected result: A working IP path proves the share is reachable and points to name discovery or name resolution.

If not: If both fail, continue to host reachability and port 445.

Test SMB before permissions

Check: Run the "Test SMB reachability" command below from the client PC.

Expected result: TcpTestSucceeded is True before you troubleshoot permissions.

If not: Check host power, subnet, Private profile, firewall rules, VPN, and guest isolation first.

Safe stop: Stop here for work-managed or domain-joined devices.

Fix the narrow account path

Check: Remove only the stale Windows Credential for the host, then reconnect with the intended account.

Expected result: Windows prompts once and accepts the current account.

If not: Verify account format and move to share plus NTFS permissions.

Safe stop: Do not enable anonymous or passwordless sharing to bypass this.

Verify permissions with a harmless write test

Check: Check Sharing permissions and Security permissions, then create and delete one temporary file if write access is needed.

Expected result: The intended user can perform the exact read or write action needed by the job.

If not: Grant the narrowest required account or group, then retest.

Safe stop: Stop if this share holds the only current copy of important files.

Decision tree

If: Direct IP path works but hostname path fails.

Then: The share is reachable; name resolution or discovery is weak.

Action: Use the stable IP temporarily, check router DHCP/reservation, and inspect discovery services only after the direct path is proven.

If: Test-NetConnection HOST -Port 445 fails.

Then: SMB is not reachable from this client.

Action: Check host power, subnet, Private profile, File and Printer Sharing firewall rules, and VPN/guest isolation before permissions.

If: Windows prompts repeatedly or rejects a known-good password.

Then: Credential Manager or account format is likely wrong.

Action: Remove only the saved credential for that host and reconnect with HOST\username or the exact account type used on the sharing PC.

If: The share opens read-only or says access denied.

Then: Network reachability is solved; share and NTFS permissions are the active layer.

Action: Check folder Properties > Sharing > Advanced Sharing > Permissions and Properties > Security together.

If: A legacy NAS appears to require SMBv1.

Then: This is a legacy compatibility and security decision.

Action: Check vendor firmware and SMB settings first.

Safe stop: Stop before enabling SMBv1 on a daily-use Windows PC.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
Network browsing is empty, but direct path works.	\\HOST\Share or \\IP\Share opens while Network view stays blank.	Discovery or name resolution	Use the direct path and stabilize IP/hostname before touching permissions.
The path cannot be found.	Ping or Test-NetConnection fails, router client list lacks the host, or host is asleep.	Host, subnet, firewall, or SMB reachability	Wake/connect the host, confirm subnet, then test port 445.
Access denied.	Port 445 works and credentials are accepted, but folder access fails.	Share permissions or NTFS Security	Compare share and folder Security for the exact account or group.
Credentials keep reappearing wrong.	Credential Manager contains old HOST or IP entries.	Saved Windows Credentials	Remove only that host credential, reconnect once, and retest.
Backup app cannot write to the share.	File Explorer opens read-only or cannot create a harmless test file.	Write permission or backup account mismatch	Fix the narrow backup account permission before running real jobs.

Reference

Commands and settings paths

Confirm client IP and DNS

ipconfig /all

Where: PowerShell or Command Prompt on the client PC.

Expected: The client has a private IPv4 address, gateway, and DNS for the trusted home network.

Failure means: A guest network, stale adapter, VPN adapter, or wrong subnet may be active.

Safe next step: Reconnect to the trusted LAN and retest before editing sharing settings.

Test SMB reachability

Test-NetConnection HOST -Port 445

Where: PowerShell on the client PC, replacing HOST with the sharing PC name or IP.

Expected: TcpTestSucceeded is True.

Failure means: SMB is blocked or the host is unreachable; permissions are not the next layer yet.

Safe next step: Check host power, Private profile, firewall File and Printer Sharing rules, guest Wi-Fi, and VPN state.

Inspect an active SMB session

Get-SmbConnection

Where: PowerShell on the client after a successful connection.

Expected: The server, share, user name, and SMB dialect match what you intended.

Failure means: You may be connected to the wrong host, wrong account, or a legacy dialect.

Safe next step: Disconnect only the wrong mapping and reconnect to the correct path.

Review mapped drives

net use

Where: Command Prompt or PowerShell on the client PC.

Expected: Mapped drives point to the current host/share and do not show stale credentials.

Failure means: A stale mapping can keep sending the wrong path or account.

Safe next step: Remove only the affected mapping after recording it; avoid broad deletes unless you know every mapping.

Check saved credentials

Control Panel > User Accounts > Credential Manager > Windows Credentials

Where: On the client PC.

Expected: There is no stale entry for the old host name or IP.

Failure means: Windows may keep sending the old password even when you type a new one elsewhere.

Safe next step: Remove only the stale host credential, then reconnect once.

Hardware boundary

Hardware and platform boundary

Change only when

Replace or retire a NAS only after modern SMB settings, firmware, account permissions, and direct-IP access are all proven insufficient.
Upgrade router or switch hardware only after same-subnet, cable, port, and firewall checks show repeated local reachability failure.

Evidence that matters

Supported SMB versions, ongoing firmware updates, stable Ethernet, documented backup-app support, and clear user/group permission controls.
For replacement networking, managed features matter only if you can maintain them; a stable consumer router may be safer than complex VLANs.

Evidence that does not matter

Marketing throughput numbers do not fix credential or permission failures.
More drive bays do not solve a broken local account model.

Avoid

Avoid old storage boxes that require SMBv1 for daily use.
Avoid exposing SMB, NAS admin pages, or Windows sharing to the public internet.

Related tool/checklist

Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.

Backup plan builder

Last reviewed

2026-05-07 · Reviewed by HomeTechOps. Reviewed for Windows 11 private-network sharing, SMB reachability, Credential Manager, permissions, and SMBv1 safety boundaries.

Sources/assumptions

Assumes Windows 11 or a currently supported Windows release on a trusted private home LAN.
Assumes the goal is local SMB/file sharing, not remote access from the internet.
Business domains, VPNs, and managed devices may enforce different policies and should be handled by the device owner or IT.
Legacy NAS devices may require vendor-specific SMB settings; this page does not recommend enabling SMBv1 as a normal fix.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Microsoft Support: File sharing over a network in WindowsUsed for share-path format, mapped-drive checks, and the reminder that the host may be off or permissions may be wrong.Microsoft Support: Essential network settings in WindowsUsed for the Public vs Private network-profile decision before enabling sharing on a trusted home LAN.Microsoft Support: Turn on Network discovery and File and printer sharingUsed for the Windows 11 path to Advanced sharing settings and the rule that sharing belongs on trusted Private networks.Microsoft Support: Credential Manager in WindowsUsed for removing stale Windows Credentials when a share keeps prompting or rejects a known-good account.Microsoft Learn: Network Discovery cannot be turned onUsed for the dependency-service and firewall escalation path when browsing or discovery stays broken.Microsoft Learn: SMB file and printer sharing firewall portsUsed for the narrow firewall check around File and Printer Sharing rules instead of turning the firewall off.Microsoft Learn: SMBv1 is not installed by defaultUsed for the legacy-device warning: do not enable SMBv1 as a normal fix for a modern Windows share.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Avoid unsafe electrical or data-loss steps.
4. Stop when the evidence says the risk moved.

FAQ

Should I turn off the firewall?

No. Keep the firewall on and check the specific File and Printer Sharing rules for the Private profile after path, profile, credentials, and permissions are checked.

Why did my share break after a router change?

The PC may now be on a Public profile, a new local IP, guest Wi-Fi, or a different subnet. Reconfirm the direct path before changing permissions.

Should I enable SMBv1 for an old network drive?

Treat that as a legacy-device problem, not a normal Windows fix. Check the device vendor's SMB support and avoid enabling SMBv1 on a daily-use PC unless you fully understand the security tradeoff.