Error 0x80070043: Fix Network Name Not Found

Error code 0x80070043 (“The network name cannot be found”) appears when Windows cannot reach a shared folder, drive, or printer on your local network. This guide explains the most common causes and walks you through the fixes that resolve it in most cases, starting with the quickest checks.

What Does Error 0x80070043 Mean?

This error is a Windows networking error. The full message usually reads: “An unexpected network error occurred. Error 0x80070043: The network name cannot be found.” It means your computer sent a request to a network resource (like a shared folder on another PC, a NAS drive, or a network printer), but the device hosting that resource either didn’t respond, rejected the request, or no longer exists at the address you used.

It is different from a simple “network path not found” (error 0x80070035), which usually means the host computer itself is unreachable. Error 0x80070043 specifically points to the named resource (the share) not being found on a host that is otherwise reachable.

Why Does This Error Happen?

Several distinct issues can produce the same error code. Understanding the likely cause helps you pick the right fix:

Incorrect share name or path: A typo in the folder name, or using the wrong computer name, is the most common cause. Windows share names are case-insensitive but must match exactly in spelling.
The shared folder was removed or renamed: If someone deleted or renamed the shared folder on the host PC, your shortcut or mapped drive will point to a resource that no longer exists.
Network discovery and file sharing are turned off: Windows may block incoming share requests if the network profile is set to “Public” or if discovery is disabled.
SMB protocol mismatch: Older devices (or older Windows versions) may use SMB 1.0, which is disabled by default on modern Windows for security reasons. A device that only supports SMB 1 will not be found.
Firewall or security software blocking: A third-party firewall or antivirus can silently block SMB traffic (ports 445 and 139).
DNS or NetBIOS name resolution failure: Your PC may not be able to translate the computer name (like \\OFFICE-PC) into an IP address.
Credential or permission problems: Sometimes the error appears when you have the wrong username/password cached, even though the share is valid.

How to Fix Error 0x80070043

Work through these steps in order. Most users find the fix in the first few steps.

1. Verify the Share Path and Name

Open File Explorer and type the UNC path directly into the address bar. For example, if the computer name is DESKTOP-ABC and the share is Documents, type \\DESKTOP-ABC\Documents.

Try using the IP address instead of the computer name: \\192.168.1.50\Documents. If that works, the problem is name resolution.
On the host PC, open File Explorer, right-click the folder, select Properties > Sharing tab, and confirm the exact share name (it may be different from the folder name).
If you are using a mapped drive, disconnect it and re-map it with the correct path.

2. Turn On Network Discovery and File Sharing

On both PCs (or the device) go to Control Panel > Network and Sharing Center > Advanced sharing settings. For your current network profile (Private or Guest/Public):

Turn on Network discovery.
Turn on File and printer sharing.
In the All Networks section, ensure Public folder sharing is on if you use that folder, and turn off Password protected sharing only if you are on a trusted home network and want to allow access without a password.

3. Check the Network Profile Type

Windows treats “Public” networks more strictly. Go to Settings > Network & Internet > Wi-Fi (or Ethernet) and click your connection. Set the network profile to Private if you trust it. This is required for file sharing to work smoothly.

4. Enable SMB 1.0 (If Needed for Older Devices)

If the target is an old NAS, a legacy printer, or an old Windows PC, it may only support SMB 1.0. On the client Windows 10/11 PC, open Control Panel > Programs > Turn Windows features on or off, and check SMB 1.0/CIFS File Sharing Support. Restart your PC. Security note: SMB 1.0 is outdated and has known vulnerabilities. Enable it only temporarily to test, and disable it again after you confirm the connection works, or better, update the old device’s firmware to support SMB 2/3.

5. Reset the Network Stack

Open Command Prompt as Administrator and run these commands one by one, pressing Enter after each:

ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh int ip reset
netsh winsock reset

Restart your PC. This clears corrupted network settings and DNS cache.

6. Check Firewall and Security Software

Temporarily disable your third-party firewall/antivirus and try the connection again. If it works, add an exception for File and Printer Sharing (SMB) in that software. Also ensure Windows Defender Firewall allows inbound SMB traffic: go to Control Panel > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall, and make sure File and Printer Sharing is checked for Private networks.

7. Map the Drive Using IP Address and Different Credentials

If you still get the error, try mapping the drive with the IP address and explicit credentials:

Open Command Prompt (not as admin) and type: net use Z: \\192.168.1.50\ShareName /user:ComputerName\Username *
Enter the password when prompted.
If that works, you can make the mapping persistent with /persistent:yes.

Common Misconceptions

“It’s a virus.” While some malware can cause network errors, 0x80070043 is almost always a configuration issue. Running a full antivirus scan is not a bad idea, but focus on the network settings first.

“Reinstalling Windows will fix it.” Rarely necessary. The error is usually caused by a simple setting or a stale cache. A reboot often helps, but a full reinstall is overkill.

“It only affects Windows 10.” The error appears in Windows 7, 8, 10, and 11. The fixes are essentially the same, though the Settings menus differ slightly.

When the Error Persists

If you have tried all the above and still see the error, consider these advanced checks:

Check the host’s shared folder permissions: On the host, right-click the folder > Properties > Sharing > Advanced Sharing > Permissions. Ensure “Everyone” or the specific user has at least “Read” permission.
Check the NTFS permissions: On the Security tab, ensure the user account has read/write permissions.
Look at the Windows Event Viewer: Open Event Viewer > Windows Logs > System, and look for errors with source “SMBClient” or “MRxSmb” around the time of the failure. The details may give a more specific error code.
Try accessing the share from another device: If a phone or another PC can access the share, the problem is on your PC. If no device can, the problem is on the host.

Frequently Asked Questions

Why does error 0x80070043 happen when I try to open a mapped drive?

Mapped drives store the network path. If the share was removed, the host computer name changed, or the network connection was interrupted, Windows cannot find the resource and throws this error. Reconnect the drive by going to This PC > Map network drive and entering the current path.

Is error 0x80070043 the same as error 0x80070035?

No. 0x80070035 (“Network path not found”) means the host computer is unreachable (wrong IP, offline, or firewall blocking). 0x80070043 means the host is reachable but the specific share name is not found. The fixes overlap, but the diagnosis differs.

Can I fix this error by changing my IP address?

Sometimes. If the error is due to a stale DNS cache or an incorrect static IP, releasing and renewing your IP (or setting a correct static IP) can help. But if the share name is wrong, changing your IP won’t help.

Does this error affect network printers?

Yes. If you try to add a network printer and Windows cannot find the printer share, you may see 0x80070043. Check the printer’s IP address and share name, and ensure the printer is turned on and connected to the network.

Is it safe to enable SMB 1.0 to fix this?

It is safe only temporarily. SMB 1.0 is vulnerable to ransomware attacks like WannaCry. Enable it only to test if an old device needs it, then disable it. Prefer updating the old device to support SMB 2/3.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →