Windows Cannot Access \\PCNAME — Error Code 0x80070043 (Fix)

What This Error Means

Windows cannot access \PCNAME\ShareName Error code: 0x80070043 The network name cannot be found.

This error is distinct from 0x80070035. The key difference:

• 0x80070035 — Windows cannot find the machine at all (path resolution failed)
• 0x80070043 — Windows found the machine but cannot reach the specific share name

The host machine is on the network. The path to it resolves. But when Windows attempts to connect to the named share on that machine, the share either does not exist, is not responding, or is being blocked.

Root Cause 1 — The Share Name Does Not Exist

The most straightforward cause: the share name in your path does not match any share on the host machine. This happens when:

• The folder was renamed or the share was deleted
• The path has a typo (\\HOSTNAME\Project when the share is named Projects)
• The share was on a different machine

Fix — Verify the exact share names on the host: On the host machine, open PowerShell and run:

Get-SmbShare | Select-Object Name, Path

This lists every share and its exact name. Match it against what you are typing.

Or browse directly: On the connecting machine, type just \\HOSTNAME (without a share name) in the File Explorer address bar. If any shares exist and are accessible, Windows shows them as a folder list.

Root Cause 2 — SMB Service Is Not Running on the Host

The SMB Server service (LanmanServer) must be running for any shares to be accessible.

Fix: On the host machine, open PowerShell as Administrator:

Get-Service LanmanServer

If it shows Stopped:

Set-Service LanmanServer -StartupType Automatic
Start-Service LanmanServer

Root Cause 3 — Windows Firewall Blocking Port 445

SMB uses TCP port 445. If the host machine's firewall blocks incoming connections on port 445, shares are unreachable even though the machine itself is visible on the network.

Fix: On the host machine:

1. Control Panel → Windows Defender Firewall → Advanced Settings
2. Inbound Rules → look for "File and Printer Sharing (SMB-In)"
3. If it shows a red circle (disabled): right-click → Enable Rule
4. Confirm the rule applies to the Private profile

Test the port from the connecting machine (PowerShell):

Test-NetConnection -ComputerName HOSTNAME -Port 445

If TcpTestSucceeded shows False, port 445 is blocked.

Root Cause 4 — Host Machine Network Profile Is Public

Fix: Settings → Network and Internet → your active connection → Network Profile Type → Private network

With Public profile, the host machine does not accept incoming SMB connections regardless of firewall rules or share configuration.

Root Cause 5 — SMB2 or SMB3 Not Negotiating Correctly

In some configurations, the SMB version negotiation fails silently, causing 0x80070043. (SMB version negotiation is a minefield on modern Windows — what the SMB protocol is and why it keeps breaking on Windows 11 explains the background.)

Check SMB server configuration on the host:

Get-SmbServerConfiguration | Select-Object EnableSMB2Protocol

If EnableSMB2Protocol shows False:

Set-SmbServerConfiguration -EnableSMB2Protocol $true -Force

Root Cause 6 — Third-Party Security Software

Security suites with "network protection" features (Kaspersky Internet Security, Norton 360, ESET Smart Security) sometimes block incoming SMB even when Windows Firewall is correctly configured.

Test: Temporarily disable the third-party security suite on the host machine and retry. If connection succeeds, add a rule in the security suite to allow SMB traffic from the private network subnet.

Step-by-Step Diagnostic

1. Type \\HOSTNAME only (no share name) — if you see a list of shares, the host is accessible and the share name is the problem
2. Run Get-SmbShare on the host to confirm the share exists
3. Run Test-NetConnection HOSTNAME -Port 445 from the client — if TcpTestSucceeded is False, port 445 is blocked
4. Check network profile on the host — must be Private
5. Check LanmanServer service — must be Running

If you look after several machines, run through the Windows networking checklist for small offices once — it catches the settings behind most of these share errors before they bite. And if your office keeps adding PCs to the same share, see how many PCs can realistically share files on one local network before blaming the error on any single machine.

---

Done troubleshooting Windows?

Oxolan fixes file sharing permanently. Installs in 2 minutes — no Windows configuration required.

Get Oxolan for Windows

---

Related Guides

• Error 0x80070035 — network path not found
• Error 0x80004005 — unspecified error
• Access denied — error 0x80070005
• Computers not showing up in the network (Windows 11)
• Network discovery on Windows, explained
• LAN file sharing: the complete guide