This error 0x80070035 occurs when you cannot access network resources. It is a somewhat confusing error because you may still be able to ping the resource, indicating that it is online, and establish a remote desktop connection, suggesting there is some access. However, before you proceed, make sure you can ping the resource to ensure that it is online. Once you have confirmed that the resource is online, follow the methods listed below and stop at the one that resolves the issue for you. Show
Usually, the most common reasons for this error revolve around firewalls, anti-virus software, or DNS. Method 1: Disabling the Firewall.Disable the firewall and also temporarily disable the antivirus. Once they have been disabled, return to the Network & Sharing Center and check if you can access the resource. If not, delete the share, re-add it, and test. If it works, the issue is with your firewall, which needs configuration; if it doesn’t, keep the firewall disabled and proceed to Method 2. Method 2: Checking Network DiscoveryEnsure that network discovery is enabled on the computer attempting to access the resource. Method 3: Reinstalling Network Adapter Drivers.First, try to update your network drivers and see if that solves the issue for you. If not, then uninstall and reinstall the drivers for your network adapter. You can do so by following the steps below.
Method 4: Check the Device Manager.1. Go to the Device Manager and expand the Network Adapters. 2. Click ‘View from Top’ and select ‘Show Hidden Devices‘. Show Hidden Devices3. Examine the adapters; if you notice a long list of 6to4 Adapters, right-click on them and delete all except for one. 4. Once you have only one of these adapters left, reboot the PC and test. Method 5: Enable NetBIOS over TCP/IP.1. Hold the Windows key and press R. Type ‘ncpa.cpl‘ and click ‘OK‘. Opening Networking Settings in Control Panel2. Right-click on the connection, and choose Properties. 3. Click “Internet Protocol (TCP/IP) Version 4” in the list. IPv4 Properties4. Click “Properties,” and then click “Advanced 5. On the Advanced TCP/IP Settings window, go to the “WINS” tab. 6. Under the NetBIOS settings, click on “Enable NetBIOS over TCP/IP,” and then click “OK. Method 6: Using the Correct IP Address Command.In some cases, if you are trying to connect to a specific IP address on the computer or are attempting to connect using the hostname, you need to be certain that you are using the correct command. Make sure to use the following command format to prevent any miscommunications. \(IP Address)\i Method 7: Sharing a FolderIt is possible that the “network path not found” error is being triggered because the network path you are trying to access has not been shared. Therefore, in this step, we will check the path properties to see if it has been shared on the network. To do this:
Method 8: Enabling the ServiceThere are some services that enable file sharing on a network by facilitating communication between two computers. If these services are disabled, the network path might not be detected. Therefore, in this step, we will enable these services. To do so:
Method 9: Deleting the Registry FolderIt is very important that you back up your registry before proceeding with this step. This step is necessary because, in some cases, the registry folder we are going to delete is filled with incorrect or outdated configurations that prevent the network path from being found. To do so:
Method 10: Changing Security PoliciesIn certain situations, local security policies may prevent your computer from functioning properly. Therefore, in this step, we will open the policy manager and define a policy for our local security. To do so:
Method 11: Editing the Hosts FileIn certain cases, you will need to edit your host file to resolve the hostnames of your machine. This host file can be found in the System32 folder and is used by the operating system as an instruction manual to resolve hostnames. In order to edit the hosts file, follow these steps:
Note: If you are trying to access the network on a Virtual Machine, try using an older boot image and see if that resolves the issue. Method 12: Use SMB1.In some cases, the SMB3 protocol might be the reason behind the occurrence of this error on Windows Server. Therefore, in this step, we will enable the use of SMB1. To do so:
Method 13: Flush the DNS.If all else fails, flush your DNS and enter ‘ncpa.cpl’ in the Run prompt; then, disable and enable your network adapter. This should fix the issue as a last resort. |