Error received when trying to share folder/file on another computer on the same home Wi-Fi network

Question

Two new laptops that were set up the same way out of the box cannot access each other’s shared files.

From file explorer, I scroll to Network, and one can see the other computer name, but double clicking/selecting the target computer name results in error “Windows cannot access that computer.  Details reflect, “error code 0x80070035, the network path was not found”.

Attempting to connect via a command line also results in an error, that indicates “You can’t access this shared folder because your computer is configured to require SMB signing”.

What is SMB signing and how do I use it to access another computer?

The devices share the same home Wi-Fi network, so I set Network Type to Private.  I have also configured sharing with Network Discovery ON, File and Print Sharing ON, and Advance Sharing Settings for All networks to reflect that Public folder sharing is ON and Password protected sharing is OFF.

This approach to share a folder across devices used to work, but apparently something has changed.  What is the best way to proceed to share folders?

Both machines are an HP OmniBook 5 Laptop 16-af1173cl, model B88BOUA#BA.  They run the current version of Windows 11 Home (Version 25H2, OS build 26200.7171) that was installed on 11/23/2025.  No third-party antivirus software is installed.  Disabling the VPN makes no difference either. 

Answer 1

To turn SMB signing back on, you just reverse the settings with these two PowerShell commands:

Set-SmbServerConfiguration -RequireSecuritySignature $true -Confirm:$false
Set-SmbClientConfiguration -RequireSecuritySignature $true -Confirm:$false

Run them as Administrator, then restart your machine. This makes signing mandatory again, which is the default for newer Windows builds. If you want to go even further and enable signing (not just require it), you can also run:

Set-SmbServerConfiguration -EnableSecuritySignature $true -Confirm:$false
Set-SmbClientConfiguration -EnableSecuritySignature $true -Confirm:$false

That ensures both the client and server actively sign SMB traffic.

Answer 2

Great question. If you make SMB signing optional, your computer will accept unsigned SMB traffic on any network, including public ones. That does increase risk because someone on the same public network could potentially tamper with SMB packets. SMB signing isn’t tied to a specific network—it’s a global setting for your system. So if you travel often and connect to public Wi-Fi, you might want to either keep signing enabled or avoid using file sharing on those networks.

Here are the two PowerShell commands to make signing optional:

Set-SmbServerConfiguration -RequireSecuritySignature $false -Confirm:$false
Set-SmbClientConfiguration -RequireSecuritySignature $false -Confirm:$false

Run these in PowerShell as Administrator, then restart both laptops. This keeps signing available but not mandatory, so your home network shares will work again.

Do you want me to also give you the commands to disable signing completely (for maximum compatibility) or keep it at optional for better security?

Answer 3

Hi Dave, I can see how this would throw you off when everything looks set up right.

The issue comes from a recent Windows update that enforces SMB signing, which is a security feature that makes sure file-sharing traffic is verified. Great for security, but it can block access if both laptops aren’t aligned on this setting.

Let’s start simple: confirm both devices are on a Private network and that Network Discovery and File Sharing are still on. If that checks out, the next step is to adjust SMB signing so it’s optional instead of required. You can do this by running a quick PowerShell command as admin.

Ican give you the exact steps for that, or do you prefer a way to handle it through the settings menu? Also, are you planning to share files without passwords, or should we keep password protection on?

Regards,

Rez

Answer 4

Great, thanks for confirming those details. Password protection isn’t a limiting factor here. It just changes how Windows authenticates, so turning it off is fine for a home setup. The reason Microsoft enforced SMB signing is to prevent tampering and man-in-the-middle attacks, which are bigger concerns on public or corporate networks. On a private home network, it’s more about security best practices than necessity. If you want the easiest path without PowerShell, there’s no direct toggle in Settings for SMB signing, so the command line is usually the way to go. That said, once you run those two commands to make signing optional, everything should work like before. If you’d rather avoid that, another option is using OneDrive or a shared cloud folder for quick transfers, but if you prefer the classic network share, adjusting SMB signing is the fix.

Answer 5

The error code 0x80070035 indicates that the network path was not found, which can occur due to several reasons related to network configuration and sharing settings. Since both laptops are on the same home Wi-Fi network and you have set the network type to Private, here are some steps you can take to troubleshoot and resolve the issue:

1. Ensure SMB Signing is Configured: The error message about SMB signing suggests that your computers may require SMB signing for shared access. To enable SMB signing:
   • Open the Local Group Policy Editor by typing gpedit.msc in the Run dialog (Win + R).
   • Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
   • Find the policy named "Microsoft network client: Digitally sign communications (always)" and set it to Disabled. Do the same for "Microsoft network server: Digitally sign communications (always)".
2. Check Network Discovery and Sharing Settings: Make sure that both laptops have network discovery and file sharing enabled:
   • Go to Control Panel > Network and Internet > Network and Sharing Center > Change advanced sharing settings.
   • Ensure that Turn on network discovery and Turn on file and printer sharing are selected for the Private network.
3. Verify Firewall Settings: Sometimes, the Windows Firewall can block file sharing. Ensure that the firewall settings allow file and printer sharing:
   • Go to Control Panel > System and Security > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall.
   • Check if File and Printer Sharing is allowed on both private and public networks.
4. Check Permissions on Shared Folders: Ensure that the folders you are trying to share have the correct permissions set:
   • Right-click the folder you want to share, select Properties, go to the Sharing tab, and click on Advanced Sharing.
   • Ensure that Share this folder is checked and that Everyone has the necessary permissions.
5. Restart the TCP/IP NetBIOS Helper Service: Ensure that the TCP/IP NetBIOS Helper service is running:
   • Press Win + R, type services.msc, and press Enter.
   • Locate TCP/IP NetBIOS Helper, right-click it, and select Properties. Set the Startup type to Automatic and start the service if it is not running.
6. Use Command Prompt to Test Connection: You can also use the Command Prompt to test the connection to the other laptop:
   • Open Command Prompt and type ping <IP address of the other laptop> to check connectivity.

By following these steps, you should be able to resolve the issues with accessing shared folders between the two laptops. If the problem persists, consider checking for any Windows updates or further network configuration issues.

---

References:

• Can't access shared folders from File Explorer in Windows 10
• Access Denied when you access an SMB file share in Windows