1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • Telnet in problem

    From Ric743256@1:103/705 to All on Tue Jan 19 07:25:03 2021
    So I'm getting pinged ok it looks like, but am unable to get into my system with telnet. I've opened the telnet port on my router and windows 10, but no luck. Does anyone have any ideas why I'm having this problem?

    Rick

    ---
    þ Synchronet þ File Cabinet BBS - 192.168.0.246
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Ric743256 on Tue Jan 19 10:09:53 2021
    Re: Telnet in problem
    By: Ric743256 to All on Tue Jan 19 2021 07:25 am

    So I'm getting pinged ok it looks like, but am unable to get into my system with telnet. I've opened the telnet port on my router and windows 10, but
    no
    luck. Does anyone have any ideas why I'm having this problem?

    $ host filecabi.synchro.net
    filecabi.synchro.net has address 73.242.87.217
    $ nmap filecabi.synchro.net
    Starting Nmap 7.70 ( https://nmap.org ) at 2021-01-19 10:07 PST
    Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
    Nmap done: 1 IP address (0 hosts up) scanned in 3.18 seconds

    Is 73.242.87.217 your correct public IP address?

    "opening" a port may not be enough, you may need to actually "forward" the port to the internal/private IP address of your BBS computer.

    Your current QWKnet tagline has a private IP address listed (which nobody outside of your network can reach):
    þ Synchronet þ File Cabinet BBS - 192.168.0.246

    So you should fix that too.
    --
    digital man

    Synchronet/BBS Terminology Definition #64:
    SBBS = Synchronet Bulletin Board System
    Norco, CA WX: 57.9øF, 22.0% humidity, 10 mph SE wind, 0.00 inches rain/24hrs --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Bob Roberts@1:103/705 to Ric743256 on Tue Jan 19 10:14:45 2021
    Re: Telnet in problem
    By: Ric743256 to All on Tue Jan
    19 2021 07:25 am

    So I'm getting pinged ok it looks like, but am unable to get into my system with telnet. I've opened the telnet port on my router and windows 10, but no luck. Does anyone have any ideas why I'm having this problem?

    Some ISPs block inbound on the default Telnet port (23). Have you tried moving your Telnet port to something like 2323? This can help you avoid script bots as well.

    Bob Roberts

    ---
    þ Synchronet þ Halls of Valhalla =San=Francisco= hovalbbs.com:2333
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)