From: fnauta@solfon.nl   
      
   On 17/12/2025 05:16, Paul wrote:   
   > On Tue, 12/16/2025 2:47 PM, Fokke Nauta wrote:   
   >> On 16/12/2025 17:22, Frank Slootweg wrote:   
   >>> Paul  wrote:   
   >>> [...]   
   >>>> Since the error at the moment, is one of Network Path Not Found,   
   >>>> I don't think it is getting tested on credentials just yet. First   
   >>>> it has to connect, before it can be rejected on credentials :-)   
   >>>   
   >>>     I agree [1]. Coming to think of it, could it be something simple as   
   >>> the workgroup being inconsistent accross his network? I.e. the computer   
   >>> name and share name could be correct, but in the wrong workgroup.   
   >>>   
   >>> [1] The error *message* is actually "The network path was not found."   
   >>   
   >> We have only one workgroup. One private network with 3 W10 pc's and 2 W11   
   laptops. All W10 pc's can see eachother and open their shares. We can see the   
   2 W11 laptops, but can't open them.   
   >>   
   >> Fokke   
   >   
   > This is the Copilot response so far:   
   >   
   > Question:   
   >   
   > If one windows 11 desktop, can see the icon for a file sharing second   
   windows 11 laptop over Wifi,   
   > what reason would there be for a 0x80070035 "The network path was not found"   
   error ? The workgroup   
   > settings are the same. The computers can successfully use the ping command.   
   >   
   > Answer:   
   >   
   > You’ve already ruled out some basics (same workgroup, successful ping,   
   >   visible icon), which narrows the causes of **0x80070035 "The network path   
   was not found"**   
   >   quite a bit. This error usually means that while name resolution and basic   
   connectivity   
   >   work, the **SMB (file sharing) protocol traffic** is being blocked or   
   misconfigured.   
   > Here are the most common reasons:   
   >   
   > ###  Likely Causes   
   > - **Firewall blocking SMB traffic**   
   >    - Windows Defender Firewall (or third-party firewalls) may allow ICMP   
   (ping) but block SMB ports (TCP 445, 139).   
   >   
   > - **SMB protocol disabled**   
   >    - Windows 11 sometimes has **SMB1 disabled by default**. If the target   
   machine requires SMB1  <=== not relevant   
   >     (older devices or misconfigured shares), connection fails.   
   >   
   > - **Network profile mismatch**   
   >    - If one PC is set to **Public network** instead of **Private**, file   
   sharing rules won’t apply.   
   >   
   > - **Credential / permission issues**   
   >    - Even if the icon is visible, if the share requires authentication  <===   
   it should put up a dialog box   
   >      and credentials aren’t accepted, you may see this error   
                   if this was the case (which is not happening)   
   >   
   > - **Name resolution vs. direct path**   
   >    - The icon may appear via cached discovery, but the actual UNC path   
   >      (`\\LaptopName\Share`) may fail if NetBIOS or DNS resolution isn’t   
   consistent.   
   >   
   > - **Services not running**   
   >    - Required services like **Function Discovery Resource Publication**,   
   >      **Server**, or **Workstation** may be disabled.   
   >   
   > - **Network isolation**   
   >    - Some Wi-Fi routers/APs have **client isolation** enabled (devices can   
   ping but not access each other’s shares).   
   >   
   > ### Steps to Diagnose   
   > 1. **Check firewall rules**   
   >     - Ensure File and Printer Sharing is allowed on both machines (Control   
   Panel → Windows Defender Firewall → Allowed apps).   
   >   
   > 2. **Verify SMB settings**   
   >     - Run `optionalfeatures.exe` → confirm **SMB 1.0/CIFS File Sharing   
   Support** if needed.  [Not Relevant, not a NAS or WinXP]   
   >     - Ensure **SMB Direct** is enabled.   
   >   
   > 3. **Confirm network profile**   
   >     - Settings → Network & Internet → Wi-Fi → Properties → set to   
   **Private**.   
   >   
   > 4. **Test UNC path directly**   
   >     - Try `\\LaptopName\C$` or `\\LaptopIP\ShareName` in File Explorer.   
   >   
   > 5. **Check services**   
   >     - Run `services.msc` → ensure **Server** and **Workstation** services   
   are running.   
   >   
   > 6. **Router settings**   
   >     - Disable client isolation if enabled.   
   >   
   > ###  Quick sanity check   
   > The most common culprit is **firewall blocking SMB ports** or **network   
   profile set to Public**. Fixing those usually resolves 0x80070035.   
   >   
   >     Paul   
      
   Thanks,   
      
   I already checked most of these things. Settings are OK and the router   
   is OK as well.   
   The contacts between the 3 W10 pc's are ok. It's only the W11 laptops.   
      
   Fokke   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)