How to fix Error Code 0x80070035 The Network Path was Not Found

Anonymous
2024-05-10T10:22:34+00:00

Hello all,

I’m using windows server 2022 azure portal

I have got Error network and it shows me massage saying;

Windows cannot access \servername\share folder

Check the spelling of the name. Otherwise, there might be a problem with your network.

So please guide me how to fix it.

Thank you in advance.

Windows for business | Windows Server | Networking | Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

17 answers

Sort by: Most helpful
  1. Anonymous
    2024-09-18T16:34:58+00:00

    For a fairly fresh windows 11 / server 2022 and later on,

    The working solution for a "universal samba share access" is as following:

    (Be careful, this will reduce the security of the local network. Not directly risky, but reduced by MS standard)

    1, The normal network share settings, private, public all goes, change to 40-56 bit, and password protected off;

    2, Samba 1.0 in features adding from the windows features;

    3, gpedit.msc, Computer Configuration > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logon;

    4, gpedit.msc Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level;

    5, gpedit.msc Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always) Disabled;

    After these, your computer can pretty much access any "network shares" made by whatever (windows 7, linux, nas etc.etc.)

    If still fails, you must have lower-level network issues, like no network, wrong IP or firewall block etc.

    9 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-11-06T19:01:42+00:00

    Zunhui,

    Thank you for that detailed answer. I implemented all three suggestions. Unfortunately, none helps. I still get that  error message. I have two machines running Windows 11. They shared files just fine until an operating system update about a month or so ago. Now, although I can see the desktop machine (ANGEL) that holds the files and all the virtual drives set up when things worked, when I click on ANGEL I get a message telling me that:

    Windows cannot access \ANGEL

    Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.

    with the 0x80070035 error message under "See details"

    If I click on one of the virtual network drives, I see (for example)

    An error occurred while reconnecting X: to

    \ANGEL\Diane

    Microsoft Windows Network: The local device name is already in use.

    This connection has not been restored.

    What might cause this?

    Thank you for any help you can give.

    --Bob R.

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-11-06T19:27:14+00:00

    This is a screenshot from the second machine. I couldn't get the first message to accept it. The green/red virtual drive icons seem to random and irrelevant--none of them works.

    Thanks again.

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-12-10T19:48:06+00:00

    Huge thanks mate. Though in my case it is a bit odd;

    I have PC A and B. PC B had always been running filesharing to other devices in LAN just fine, until I accidentally flipped firewall setting on PC A off and back on entirely.

    Now we are looking at PC B which is still sharing files alright to iOS devices in LAN, but when it comes to PC A, the error of 80070035 persists. Ran through all your remedies above also.

    Any suggestions?

    Many thanks,

    B

    0 comments No comments
  5. Anonymous
    2024-12-17T20:45:59+00:00

    I have an Asustor NAS which I was having issues with logging in and had tried all of the above as well with no success. I had a PC that was able to log in just fine (Windows 10), but my Windows 11 machine was receiving the same error code.

    I found out what the issue is and was able to access my server shares.

    Go to - Control Panel - User Accounts - Manage your credentials - Windows Credentials

    Click on "Add a Windows credential"

    Put in the network share address (ex. \Angel) or IP address of that machine if it has a static address.

    Put in the username and password that has access to that share.

    Hope that works!

    18 people found this answer helpful.
    0 comments No comments