How to Fix Error Code 0x80070043 on Windows

Error code 0x80070043 appears when Windows cannot reach a network share or a shared folder. The full message reads “The network name cannot be found.” You see it most often when you open a shared folder on another PC, connect to a network share, or reach a folder on a NAS box.

This error is almost always a settings problem, not broken hardware. A wrong share path, a turned-off sharing option, or a stale saved login is usually behind it.

What Error Code 0x80070043 Means

The 0x8007 part marks this as a standard Windows error. The 0043 part is decimal error 67, which Windows defines as “The network name cannot be found.”

In plain terms, your PC asked for a network name and got no answer. That name could be a share path like \\Office-PC\Documents or a saved network link. Windows asked, nothing replied, and it raised this error.

This is a client-side problem in most cases. Your computer failed to find the resource, so start fixing things on your own PC first. Here is why that matters: you can waste an hour changing settings on the other machine when the real problem sits on yours.

What Causes Error 0x80070043

Several common things trigger this error. Let’s break it down.

• • Wrong share path. You typed the computer name or folder name wrong, or the share was renamed or removed.
  • Network discovery turned off. Windows cannot see other computers on the network when this is off.
  • SMB file sharing turned off. Newer Windows builds turn off the old SMB1 protocol by default, but some older NAS boxes still need it.
  • Saved credentials gone stale. Windows saved an old password for the share, and the password changed since.
  • Firewall blocking the connection. File and Printer Sharing rules got blocked by a firewall.

• Dead mapped link. A saved network link still points to a share that no longer exists.

Fix 1: Check the Share Path and Computer Name

Typos cause more of these errors than anything else. Start here before you touch any setting.

1. Read the path you typed. A share path looks like \\COMPUTER-NAME\SharedFolder. The two backslashes at the start matter.
2. On the other computer, press Win + R, type cmd, and run hostname. Compare the result with what you typed. Every letter must match.
3. On the other computer, check that the folder is still shared. Right-click the folder, open Properties, then the Sharing tab.
4. If you use an IP address, run ipconfig on the other computer and confirm the address has not changed.

If the path checks out, move to the next fix.

Fix 2: Turn On Network Discovery and File Sharing

Your PC needs network discovery on to find other devices. File and printer sharing must be on for your PC to talk to them.

1. Open Settings and go to Network & internet.
2. Click Advanced network settings, then Advanced sharing settings.
3. Expand your current network profile. Turn on Network discovery and File and printer sharing.
4. Do the same on the computer hosting the share.

Use the Private profile on trusted home and office networks. The Public profile locks sharing down on purpose. If your PC cannot reach the network at all, the problem is bigger than sharing. Our guide to fixing WiFi that connects with no internet covers that case.

Fix 3: Turn On SMB File Sharing Support

Windows talks to shared folders over the SMB protocol. Windows 10 and 11 ship with the old SMB1 turned off because it is insecure. Some older NAS boxes, printers, and PCs still speak only SMB1. If your share lives on old hardware, this is often the fix.

1. Press Win + R, type optionalfeatures, and press Enter.
2. Find SMB 1.0/CIFS File Sharing Support in the list.
3. Check the box for SMB 1.0/CIFS Client.
4. Click OK and restart your computer.

A word of caution: only turn on SMB1 if an old device needs it. Modern devices use SMB2 or SMB3, which already run by default. Try the share again after the restart.

Fix 4: Clear Stale Saved Credentials

Windows saves the username and password you used for a share in Credential Manager. When that password changes, Windows keeps sending the old login. The share rejects it, and you get error 0x80070043.

1. Press Win + S, type Credential Manager, and open it.
2. Click the Windows Credentials tab.
3. Under Generic Credentials, find any entry that names the other computer or the share, and click Remove.
4. Try the share again. Windows will ask for a fresh username and password.

If the prompt never appears, open Command Prompt and run net use * /delete. This drops all saved network connections at once.

Fix 5: Check the Firewall on Both PCs

File sharing needs several firewall rules open. A firewall update or a new security suite can block them without warning.

1. Open Windows Security, then Firewall & network protection.
2. Click Allow an app through firewall.
3. Find File and Printer Sharing. Make sure it is checked for your network type.
4. Repeat these steps on the computer hosting the share.
5. If you run a third-party firewall, add your local network to its trusted zone.

To test whether the firewall is the problem, turn it off for one minute and try the share. If it works, turn it back on right away and add the proper rule.

Fix 6: Reconnect the Dead Network Link

Old saved network links often cause this error. A link saved last year may point to a share that moved.

1. Open File Explorer and look under This PC. A red X on a network icon means the link is dead.
2. Right-click the dead link and choose Disconnect.
3. Use the Map option in the toolbar to create a fresh link. Type the full share path, using the verified path from Fix 1.
4. Check Reconnect at sign-in if you want the link to survive restarts.
5. Check Connect using different credentials if the share needs a different account than your Windows login.

Use the IP address instead of the computer name if name lookups keep failing. A path like \\192.168.1.50\Documents skips the name lookup step entirely.

How to Stop Error 0x80070043 Coming Back

Give the host computer a static IP address or a DHCP reservation in your router so the path never shifts. Keep one set of share credentials, and update Credential Manager the same day you change a password.

If the share lives on a NAS, update its firmware and use SMB2 or SMB3 in its settings. Old SMB1-only devices cause repeat trouble. Damaged system files can reak network features too. Run sfc /scannow, and if the scan itself errors out, our guide to fixing the Windows Resource Protection error shows what to do next.

For more step-by-step Windows fixes, see our guides on how to fix a white screen of death and the ntoskrnl.exe blue screen error. You can also read more about Axeetech and how we test every fix before we publish it.

Frequently Asked Questions

What does error code 0x80070043 mean?

It means “The network name cannot be found.” Windows tried to reach a network share or a shared device and got no answer. The cause is usually a wrong path, turned-off sharing, stale saved logins, or a blocked firewall rule.

Is error 0x80070043 a virus or malware?

No. This is a normal Windows networking error, not a sign of infection.

Why does the error appear only for one shared folder?

Other shares work because their paths and permissions are fine. The failing folder was likely renamed or unshared on the host computer. Check the Sharing tab on that exact folder first.

Can a VPN cause error 0x80070043?

Yes. A VPN routes your traffic through a different network, so your PC cannot see local shares while it is on. Disconnect the VPN or add the share’s network to the split-tunneling list, then try again.

Should I turn on SMB1 to fix this error?

Only if the share lives on an old device that speaks nothing newer. Modern PCs and current NAS boxes use SMB2 or SMB3, which are already on. Turning on SMB1 for no reason adds security risk.

Does this error affect shared printers too?

Yes. A shared printer on the network is also a network name. The same fixes apply: check the path, turn on discovery, and clear stale credentials.