file sharing error - Windows cannot access \\<Computer>

futbolfan · Feb 20, 2025

I know this topic has arisen many times and I've researched extensively to no avail. Here is my situation:

Computer B runs on Windows 10; computer A is a dual boot system (Windows 10/11)
File sharing works fine when computer A is booted into Windows 10.
However, when computer A is booted into Windows 11, attempts to access shared files on computer B generate a network path not found error message.
Computer B can see and open files shared on computer A.
Computer A can see computer B in file explorer but cannot access shared files on that computer (error code 0x800070035).
Computer A can ping computer B using its IPv4 address and by its name <Computer B>.mynetworksettings.com

Steps taken so far:
1. verified that all network sharing settings are enabled correctly
2. verified that "require password" is disabled
3. enabled SMB1 (I am uncomfortable leaving that enabled)
4. verified that all required services are running:
o Function Discovery Provider Host Running....Manual - changed to Automatic
o Function Discovery Resource Pub Running....Manual (Trigger Start) - changed to Automatic (Trigger Start)
o SSDP Discovery Running....Manual - changed to Automatic
o UPnP Device Host Stopped....Manual - Started and changed to Automatic
5. flushed DNS cache
6. ran nslookup by IPv4 address: correct name returned <Computer B>
7. entered \\<IPv4 address> in file explorer search bar: returned Windows cannot access \\<IPv4 address> error code 0x80004005
8. entered \\<Computer B> in file explorer search bar: returned Windows cannot access \\<Computer B> error code 0x80070035
9. tried using a local account rather than my Microsoft account but that did not work.

It shouldn't be this hard

I'm preparing to try Nearby Sharing but I first have to install Bluetooth adapters to these older Dell desktops.
Thanks in advance for any suggestions. In the meantime, my USB flash drives are being put to good use.

Regards,
John

Berton · Feb 20, 2025

For the Bluetooth [BT] part I have good success with IOGear USB dongles where the Wireless adapter does not include BT.

Amazon.com : iogear bluetooth

For file saving and sharing I have a Buffalo NAS attached to my Router and any Wired or Wireless/Wi-Fi attached to the Router can Map a folder on it and files in that folder. I have Win7, Win10 and Win11 Desktops attached via Ethernet cable plus some Wireless Notebooks at various times. I don't use dual-booting.

HTA · Feb 20, 2025

futbolfan said:
I know this topic has arisen many times and I've researched extensively to no avail. Here is my situation:

Computer B runs on Windows 10; computer A is a dual boot system (Windows 10/11)
File sharing works fine when computer A is booted into Windows 10.
However, when computer A is booted into Windows 11, attempts to access shared files on computer B generate a network path not found error message.
Computer B can see and open files shared on computer A.
Computer A can see computer B in file explorer but cannot access shared files on that computer (error code 0x800070035).
Computer A can ping computer B using its IPv4 address and by its name <Computer B>.mynetworksettings.com

Steps taken so far:
1. verified that all network sharing settings are enabled correctly
2. verified that "require password" is disabled
3. enabled SMB1 (I am uncomfortable leaving that enabled)
4. verified that all required services are running:
o Function Discovery Provider Host Running....Manual - changed to Automatic
o Function Discovery Resource Pub Running....Manual (Trigger Start) - changed to Automatic (Trigger Start)
o SSDP Discovery Running....Manual - changed to Automatic
o UPnP Device Host Stopped....Manual - Started and changed to Automatic
5. flushed DNS cache
6. ran nslookup by IPv4 address: correct name returned <Computer B>
7. entered \\<IPv4 address> in file explorer search bar: returned Windows cannot access \\<IPv4 address> error code 0x80004005
8. entered \\<Computer B> in file explorer search bar: returned Windows cannot access \\<Computer B> error code 0x80070035
9. tried using a local account rather than my Microsoft account but that did not work.

It shouldn't be this hard

I'm preparing to try Nearby Sharing but I first have to install Bluetooth adapters to these older Dell desktops.
Thanks in advance for any suggestions. In the meantime, my USB flash drives are being put to good use.

Regards,
John

I got this from Reddit. It fixed the problem for me.

https://www.reddit.com/r/sysadmin/comments/1hnas4d/windows_11_24h2_update_cannot_access_network

Powershell (as admin)

Set-SmbClientConfiguration -RequireSecuritySignature $false -Force

Has resolved various PCs with similar symptoms in the last two weeks. Devices could see the device hosting the share, had file and printer sharing turned on etc. Could see the folder but just couldn't open it. Think the error was 0x80070035 network path not found.

Control SMB signing behavior

Windows 11, version 24H2 Enterprise, Pro, and Education require both outbound and inbound SMB signing.

Guesing this was not the case for 23H2 and prior.

Maybe try these as well if first one doesn't do the trick:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force

Set-SmbClientConfiguration -RequireSecuritySignature $false -Force

Set-SmbServerConfiguration -RequireSecuritySignature $false -Force

futbolfan · Feb 20, 2025

To HTA...I will definitely try this fix

It makes more sense than some of the other purported remedies.
I am getting that same message you referenced:
Error code: 0x80070035
The network path was not found

flhthemi · Feb 21, 2025

futbolfan said:
To HTA...I will definitely try this fix It makes more sense than some of the other purported remedies.
I am getting that same message you referenced:
Error code: 0x80070035
The network path was not found

I had that same error. I opened the credential manager and created a windows credential entry for that device. Been working fine ever since. If there is already an entry for the device remove it and enter it again.

futbolfan · Feb 21, 2025

That's another excellent idea! Can the windows credential be created without including a user name and password?

flhthemi · Feb 22, 2025

futbolfan said:
That's another excellent idea! Can the windows credential be created without including a user name and password?

No.

Dru2 · Feb 22, 2025

flhthemi said:
I had that same error. I opened the credential manager and created a windows credential entry for that device. Been working fine ever since. If there is already an entry for the device remove it and enter it again.

futbolfan said:
That's another excellent idea! Can the windows credential be created without including a user name and password?

flhthemi said:
No.

Care to share how you did it then? Procedures?

flhthemi · Feb 22, 2025

Dru2 said:
Care to share how you did it then? Procedures?

I just gave the target device a login name and a password then set it up in credential manager. Had same thing happen another time but that device DID already have a login name and password. So I removed it and set it up again and it works fine.

futbolfan · Feb 23, 2025

"Internet or network address" for the new credential?
If I run nslookup <IPv4 address>, the name returned is <Computer B> which is correct. So, it makes sense to create a windows credential using that IPv4 address. If it doesn't work, I can delete that credential. Does that sound about right?

Dru2 · Feb 23, 2025

flhthemi said:
I just gave the target device a login name and a password then set it up in credential manager. Had same thing happen another time but that device DID already have a login name and password. So I removed it and set it up again and it works fine.

Still doesn't tell me (or anyone else) how you did it. You know - step by step procedures? Unless you just found the fix somewhere else, then Link?

flhthemi · Feb 24, 2025

Dru2 said:
Still doesn't tell me (or anyone else) how you did it. You know - step by step procedures? Unless you just found the fix somewhere else, then Link?

1) Give the device you want to connect to your workgroup a password and login name
2) Open the credential manager (Click Start>type Credential OR go to the Control Panel>Credential Manager)
3) Select Windows Credentials
4) Select Add Windows Credential
5) Enter the address i.e. \\device_name
6) Enter the User Name
7) Enter the Password for that user name

futbolfan · Feb 24, 2025

I don't think this solution will help me because I do not receive a prompt to enter network credentials like this...

Rather I receive this error message...

On prior attempts to enter a username and password, I received this message...

I've opened Secpol.msc but do not know what to look for or change.

file sharing error - Windows cannot access \\<Computer>

Member

My Computer

Ret. ATC

My Computers

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Member

Attachments

My Computer

Similar threads