home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   SYNCHRONET      Rob Swindell fetishistic worship forum      43,341 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 41,713 of 43,341   
   Digital Man to Rick V   
   TWGS Error   
   03 May 25 16:54:56   
   
   TZUTC: -0700   
   MSGID: 54195.sync@1:103/705 2c7cb683   
   REPLY: 1:154/110@fidonet.org 6816a836   
   PID: Synchronet 3.21a-Linux master/b8e2bbc11 May 03 2025 GCC 12.2.0   
   TID: SBBSecho 3.24-Linux master/b8e2bbc11 May 03 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: TWGS Error   
     By: Rick V to Digital Man on Sat May 03 2025 06:29 pm   
      
    > Hello Digital.   
    >   
    > 05 Sep 70 17:10, you wrote to me:   
    >   
    >  DM>   Re: TWGS Error   
    >  DM>   By: Rick V to All on Sat May 03 2025 08:55 am   
    >   
    >  >> Hello All.   
    >  >> I'm trying to get TWGS to work under SBBS. I have it setup just as   
    >  >> the wiki FAQ's say, but keep get the same error.   
    >  >>   
    >  >>  5/3  08:52:39a  Node 1  Node 1 RLogin gate to   
    >  >> filecabi.casacam.net port 2002 on socket 1772   
    >  >>   5/3  08:52:49a  Node 1  !TELGATE ERROR 10061 (0)   
    >  >> connecting to   
    >  >> server: filecabi.casacam.net   
    >   
    >  DM> https://windowsreport.com/winsock-error-10061/   
    >   
    >  >> My command line is "*rlogin filecabi.casacam.net:2002"   
    >   
    >  DM> That looks fine.   
    >   
    >  >> This works when I call it from SyncTERM directly from within my   
    >  >> network and from the outside. It also works on Mystic. Any thoughts   
    >  >> on my error?   
    >   
    >  DM> What about directly from the same computer as the RLogin server?   
      
    > I can use SyncTERM to get to it from within my home network, and also from   
    > outside my network.   
      
   That doesn't really answer the question. If the RLogin server and the client   
   are both behind a NAT and the public hostname resolves to a *public* hostname,   
   your NAT gateway will have to support "hairpinning" to be able to connect from   
   one to the other using the public IP address. So either enabling hairpinning   
   or use the private IP address (instead of the public hostname/IP address) on   
   the *rlogin command-line.   
   --    
                                               digital man (rob)   
      
   Breaking Bad quote #14:   
   First name of Emlio - that's at least half a beaner, let you off for $10 - Hank   
   Norco, CA WX: 60.5øF, 84.0% humidity, 5 mph SSE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.24-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 263/1   
   SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 310/31 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca