Windows 10: The network path was not found error - usual fixes not working

My Dev computer (Win 10 Pro) cannot get to any shares on my DBServer (Win 10 Pro) anymore.

I have tried the usual (SMB installed, NetBIOS over TCP/IP, typos in share, both on Private network, network discovery turned on, reset TCP/IP, disabling firewall and antivirus) and still I cannot get it working.

This started happening after moving to a new office with a new router (Comcast Cable, though the old office was also Comcast)

Here are the specific symptoms:

• DBServer can see and interact with all Dev shares just fine.
• Dev can see DBServer in Network, but when I try to go into it to see its shares I get a 0x80070035, The network path was not found error
• DBServer cannot even interact with its own shares - it can see its own shared folders in Network, but I get the same error if I try to enter a shared folder from Network.
• Same thing if I make a brand new share.
• I can get to my Postgres database from Dev's PgAdmin and via Access through ODBC just fine.
• I can ping DBServer.

Anything else I can try other than wiping and reinstalling Windows?

:)

 

Error 0x80070035 The Network Path Was Not Found

I've had this for some weeks now. Tried all sorts - NetBIOS over TCP/IP on/off, IPV6 enable/disable, changing workgroup, creating new Windows credentials etc etc ad nauseam.

This fixed it:Telling my AV software that the local network (my home LAN) is trusted.

Somehow when I first set up the LAN, Windows decided that my LAN was 'Public' and the firewall in my AV software (KIS) flagged it as public (ie untrusted). Changing the network type to Private in Windows didn't migrate to KIS, but actively telling the firewall
in KIS that my LAN is trusted solved this 'unable to map drive' problem.

Hope that helps some people.

 

Error 0x80070035 The Network Path Was Not Found

Hi Jason,

Thank you for getting back to us. We are sorry that you are still facing the issue.

I suggest you to follow the steps provided below and check if it helps.

1. Press Windows key + X and select Control Panel.

2. Click on Network and Sharing.

3. In the left navigation pane, click on change advanced sharing settings.

4. Click and expand Private.

5. If network discovery is off, under Network discovery, click
Turn on network discovery, and then click save changes. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

Also, check if the issue persists in Safe Mode with Networking.

Start your PC in safe mode in Windows 10

http://windows.microsoft.com/en-in/windows-10/start-your-pc-in-safe-mode

Hope this helps. Keep us posted on the status for further assistance.

 

Hi,

Have you tried any of these fixes?

Look here: -

 

Yes, I found that page and tried them all.

 

Which pc is master browser? run this on all pcs do they all state the right pc for master browser NetBScanner - NetBIOS scanner

 

Samuria,

Thanks for helping! Ok, all agree that the master browser is my new co-worker's computer, Chris-Work-Pc.

- Brad

 

When you look for a share windows doesnt look it asks the MB for details if the MB is not up to date it can give problems you can sometime force it by stop and starting browser service or pinging all othe rpc from MB to force an update

 

That sounded so good! But rebooting the MB did not fix it. *Sad Gotta head out, but back in the office on Monday to try again.

 

@Samuria

Back to debugging this. So I changed my Dev computer to be the MB (and verified with NetBIOS Scanner). I also re-pinged DBServer for good measure and I am still unable to connect. All other computers on the network ask for credentials when I attempt to connect to them, but DBServer just hangs and then returns the network path not found error. DBServer can still see all of the network resources without problems.

Any other recommendations for debugging this? Thanks for your help!

 

Ok, I feel stupid,
I still had "Allow Windows to manage homegroup connections" set on my Dev computer. Changing to "Use user accounts and passwords to connect to other computers" fixed it. (this in Control Panel...Network and Sharing Center...Advanced sharing settings for those who need to know where to change the setting)
I had changed this setting on the DBServer, but that was the wrong side of the communication line and hence the forehead slapping.
I think the reason this became a problem when moving to the new network is that one of the laptops here is a homegroup "server" and there were no homegroups on my last network.