TZUTC: -0800   
   MSGID: 53087.sync@1:103/705 2bad0be1   
   REPLY: 53086.sync@1:103/705 2bad0bde   
   PID: Synchronet 3.20a-Linux master/57c2367a5 Sep 18 202 GCC 10.2.1   
   TID: SBBSecho 3.23-Linux master/0dc160f0e Nov 25 2024 22:03 GCC 12.2.0   
   COLS: 132   
   BBSID: LUNAROUT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: Re: Help with FidoNet setup   
     By: bbsing to Grease on Tue Nov 26 2024 22:45:54   
      
    >   Re: Re: Help with FidoNet setup   
    >   By: Grease to bbsing on Tue Nov 26 2024 10:06:15   
    >   
    >  >   Re: Re: Help with FidoNet setup   
    >  >   By: bbsing to Grease on Mon Nov 25 2024 11:19 am   
    >  >   
    >  >  bb> What are some of the issues you are experiencing?   
    >  >  bb> What have you tried?   
    >  >  bb> I'm trying why I'm not getting communication back from the NC. The   
   issue I'm having is, I don't know if the NC has   
    >  >  bb> received   
    >  >  bb> my messages.   
    >   
    >  > Pretty much the same as you. I was NC of 1:170 back in the 90's. Five   
   years ago I had a node number and was fine. The guy for   
    >  > R19, I know and have had  several messages and netmails to, basically   
   has me   
    >  > set up, ready to go. It's theNC of 1:106 that I can't get ahold of. So,   
   1:396/45 will help if he or I can't get through to   
    >  > him.   
    >  > It just seems that there is an attitude of "We're FidoNet and you need   
   us, not the other way around". When other networks I'm   
    >  > in is easier to join and just as busy.   
    >   
    > Thanks for the response Grease.   
    >   
    > In my case I don't understand the hold up, specifically after reading   
   policy4 doc, and the regqion 17 guide.   
    >   
    > I'll try again, i probably didn't do something correctly.   
      
   I'm responding to my message, because after doing some more research I see   
   partly why I'm having troubles.   
      
   NC for 1:138 system has my IP on a blacklist, connections from my IP address   
   are being rejected/blocked.   
   NC for 1:340 system requires a password.   
   NC for 1:105 system bink port doesn't appear to be on. Might be a push only   
   system.   
      
   So when trying to send a netmail to these systems via binkp ... fails are what   
   happens.   
      
   If you or anyone else is attempting to follow proceedures by sending a netmail   
   like policy4 states, I cant see how this process is supposed to work.   
      
   -------------------------------------------------------------------   
      
   Once you have located the network or region in your area, send a message   
   containing a request for a node number to node zero of that network or   
   region.  The request must be sent by netmail, as this indicates that your   
   system has FidoNet capability.   
      
   You must set up your software so that the from-address in your message does   
   not cause problems for the coordinator who receives it.  If you pick the   
   address of an existing system, this will cause obvious problems.  If your   
   software is capable of using address -1/-1, this is the traditional address   
   used by potential sysops.  Otherwise use net/9999 (e.g. if you are applying   
   to net 123, set your system up as 123/9999).  Many nets have specific   
   instructions available to potential sysops and these procedures may indicate   
   a preference for the from-address.   
      
   --------------------------------------------------------------------   
      
   ---   
    þ Synchronet þ Lunar Outpost BBS   
    * 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 203/0 218/700 221/0 226/30 227/114 229/110 114 206   
   SEEN-BY: 229/317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 310/31   
   SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 460/256 1124 467/888 633/280 712/848 770/1 902/26 5020/400   
   SEEN-BY: 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426