From: this@ddress.is.invalid   
      
   Fokke Nauta  wrote:   
   > On 18/12/2025 20:08, Frank Slootweg wrote:   
   [...]   
   > Whatever you try to say, the laptop is next to my pc. I use them both.   
   > The laptop was active when I tried to connect. So sleep is no option.   
      
     Good. But I didn't *only* mention sleep, did I!?:   
      
   [Rewind/repeat:]   
   > >    That is, because, as Paul said *and* the actual error message says,   
   > > there is a *network* problem which *precedes* the authentication (name   
   > > and password) phase. See the next two lines of the error message:   
   > >   
   > >>> Otherwise, there might be a problem with   
   > >>> your network. To try to identify and resolve network problems, click   
   > >>> Diagnose.   
   > >   
   > >    So even if there was no sleep problem, you should check for a network   
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   
   > > problem, which apparently gives the exact same error message and code as   
   ^^^^^^^^^^^^ ....   
   > > when the remote is sleeping.   
   > >   
   > >    I think the 'nbtstat' command which I mentioned, can probably help   
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   
   > > with that, but given your uncooperative attitude, I'm not going to hold   
   > > your hand.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)