From: this@ddress.is.invalid   
      
   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.   
      
     The point isn't that you have only one workgroup, but whether the   
   workgroup is correctly set on all systems, especially on the two Windows   
   11 laptops, which "don't work" and are apparently relatively new.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)