Understanding the Error Code
The error code 0x80070043 translates to "The network name cannot be found." This specific message indicates that the client computer has successfully reached the network but failed to identify the specific shared resource requested. Unlike general connectivity issues, this error suggests a problem with naming resolution or access permissions rather than a complete loss of network connection.
This situation frequently arises when users attempt to map a new drive or insert a shortcut to a network location using an invalid Universal Naming Convention (UNC) path. The system expects a format like \\ServerName\ShareName, and any deviation in syntax can trigger this failure. Additionally, modern versions of Windows have tightened security defaults, which may block automatic discovery of network shares if the appropriate services are not explicitly enabled.
Verify Network Profile Settings
One of the most common causes for this error is the network adapter being configured as a Public network. Windows treats Public networks as untrusted environments, automatically disabling network discovery and file sharing features to protect the device. When you try to access a network share from a Public profile, the operating system blocks the request before it even attempts to resolve the name.
To correct this, navigate to the Settings application and select the Network & Internet section. From there, choose the status page for your active connection, whether it is Wi-Fi or Ethernet. Look for the Network profile type setting and change it from Public to Private. This action signals Windows to allow the device to be discoverable by other computers on the local area network.
Check Essential Services
Even with the correct network profile, the underlying services required for network sharing must be active. If the Computer Browser service or the Function Discovery Provider Host service is stopped, Windows cannot enumerate available shares on the network. This leads to the "network name cannot be found" error because the lookup mechanism is effectively blind.
Open the Services management console by pressing Win + R and typing services.msc. Locate the following services in the list:
- Function Discovery Provider Host
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
Ensure that each of these services is set to Automatic startup and is currently Running. If they are stopped, right-click each one and select Start. This step is crucial for maintaining the visibility of network resources in the File Explorer sidebar.
Validate Firewall and Sharing Rules
Windows Defender Firewall may be blocking the necessary ports for Server Message Block (SMB) communication. SMB typically uses TCP port 445, and if this port is restricted, the client cannot establish a session with the server. You must ensure that File and Printer Sharing is allowed through the firewall for both Private and Public networks, although focusing on Private is sufficient if your profile is correctly set.
Access the Windows Defender Firewall settings via the Control Panel. Navigate to Allow an app or feature through Windows Defender Firewall. Click the Change settings button to unlock the options, then scroll down to find File and Printer Sharing. Ensure the checkbox next to Private is selected. If you are accessing a share across different subnets, you may also need to enable it for Domain profiles depending on your organization's setup.
Use Direct UNC Paths Instead of Shortcuts
When inserting a new drive, avoid relying on the "Network" folder in File Explorer, which relies heavily on network discovery protocols that can be unstable. Instead, use the direct UNC path in the address bar. Type \\IP_Address_of_Server\ShareName directly into the navigation bar. Using the IP address bypasses DNS resolution issues that might contribute to the error.
If the direct IP method works, the issue is likely related to NetBIOS or DNS configuration on the client side. You can then troubleshoot name resolution separately without the pressure of the drive mapping failing. For persistent issues, consider reviewing our guide on Troubleshooting Network Issues on Windows to diagnose deeper connectivity problems.
Clear Credential Manager Entries
Stale credentials can sometimes cause the system to reject a valid share path, resulting in a generic network error. If you previously accessed this share with different permissions, Windows may be holding onto outdated authentication tokens. Clearing these entries forces the system to request fresh credentials, which can resolve hidden permission conflicts.
Open the Credential Manager from the Control Panel. Select Windows Credentials and look for any entries related to the target server IP or hostname. Remove these entries from the list. Afterward, attempt to reconnect to the share. You will be prompted to enter the username and password again, ensuring that the current account has the necessary rights to access the resource.
Frequently Asked Questions
Why does the error happen only on some computers?
This usually happens because the affected computer has its network profile set to Public or lacks the necessary discovery services. Other machines on the same network may have Private profiles enabled, allowing them to see the share while others cannot.
Can I fix this error by restarting the router?
Restarting the router refreshes the DHCP lease and network topology, which might help if the issue is related to IP conflicts. However, since 0x80070043 is a naming resolution error, it is more likely caused by local Windows settings than router connectivity issues.
What if I can ping the server but still get the error?
Ping tests basic ICMP connectivity, which does not guarantee that SMB ports are open or that the share exists. You should use the telnet command or Test-NetConnection in PowerShell to verify that TCP port 445 is accessible from the client to the server.
Does disabling antivirus software help resolve this?
Third-party antivirus suites often include their own firewalls that may block SMB traffic. Temporarily disabling the antivirus firewall can help determine if it is the culprit. If the connection succeeds, add an exception for the file sharing ports in your antivirus settings.
How do I check if the share name is correct?
You can verify the share name by logging into the server machine and opening the Properties of the folder intended for sharing. Check the Sharing tab to see the exact Share Name displayed. Even a single character difference in case sensitivity or spelling can trigger this error.