MSGID: 1:282/1031.0 ecd8c320   
   REPLY: 1:129/215 87990918   
   TZUTC: -0600   
   CHARSET: PC-8   
   Hello g00r00,   
      
   >> + 02.19.2021 21:05:34  1-RB Socket read status 113   
   >> + 02.19.2021 21:05:34  1-Connection lost   
   >> + 02.19.2021 21:05:34  1-Authorization failed   
      
   > If you Google read status 113 you get this:   
   > The problem is triggered by the EHOSTUNREACH error (113) while reading the   
   dat   
   > from the socket.  Normally, the EHOSTUNREACH error is given when writing to a   
   > socket, however, for some reason, LINUX socket implementation returns that   
   > error when reading from the socket under some unknown conditions. Since we   
   > don't how to handle such error  (i.e.retry later or close the socket), it was   
   > returned as an 'unknown' network error.   
   > In translation, it sounds like something that could be firewall related?   
      
   That was my understanding also and I had already relayed that information and   
   made the suggestion that his firewall or router may need checking. Also since   
   I can ping his FQDN ok. But both his BinkP and telnet ports are closed to   
   incoming connections.    
      
   Jeff   
      
   --- BBBS/Li6 v4.10 Toy-5   
    * Origin: Fidonet: The Ouija Board - Anoka, MN - bbs.ouijabrd.net (1:282/1031)   
   SEEN-BY: 1/123 90/1 105/81 120/340 123/131 129/305 226/30 227/114   
   SEEN-BY: 227/702 229/101 424 426 452 550 664 700 981 1016 1017 240/1120   
   SEEN-BY: 240/1634 1895 5411 5832 5853 6309 8001 8002 8005 249/206   
   SEEN-BY: 249/307 317 400 261/38 280/464 5003 292/854 313/41 317/3   
   SEEN-BY: 320/219 322/757 335/364 342/200 371/52 382/147 633/280 2452/250   
   SEEN-BY: 2454/119   
   PATH: 282/1031 261/38 240/1120 5832 229/426