• Ports won't open for some reason

    From Nodoka Hanamura@21:1/101 to All on Sun Nov 24 12:36:31 2019
    Okay,

    I've run into a bit of a problem with NCBBS regarding getting it going again
    on my new internet provider. When I spool up MIS, it reports that it couldn't open BINKP, TELNET or FTP ports. I checked with netstat, lsof and another utility and those ports aren't in use. Anyone know why this is? It wasn't
    doing this before - Although I did switch to WIFI from Ethernet because the
    new router is farther away from where the old one used to be and I don't have any long ethernet cables. But that doesn't explain why it wouldn't just use wlan0 instead of eth0.

    ===================
    Born too late to experience the 90s.
    Born too early to go back in time.
    Born just right to see the comeback.
    NeoCinci BBS SYSOP

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Scarecrow@21:4/111 to Nodoka Hanamura on Sat Nov 23 20:15:05 2019
    On 24 Nov 2019, Nodoka Hanamura said the following...
    again on my new internet provider. When I spool up MIS, it reports that
    it couldn't open BINKP, TELNET or FTP ports. I checked with netstat,

    When I changed interfaces on the BBS machine DHCP assigned it a new IP based
    on the MAC address of the new interface. mis didn't complain on startup, but none of the configured servers were accessible until I reset the router's
    DHCP static addresses to give the BBS machine it's original address back. Someone else had mentioned that I could have also changed the servers adapter info in Mystic's Server Comfig to get it going on the new interface, but
    giving it it's original address saved having to reconfigure several other non-BBS things. Just a thought the left cornfield.

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
    * Origin: Blue Northern Software | bnsbbs.ddns.net:23000 (21:4/111)
  • From Nodoka Hanamura@21:2/106 to Scarecrow on Sun Nov 24 02:54:19 2019
    On 23 Nov 2019, Scarecrow said the following...

    When I changed interfaces on the BBS machine DHCP assigned it a new IP based on the MAC address of the new interface. mis didn't complain on startup, but none of the configured servers were accessible until I
    reset the router's DHCP static addresses to give the BBS machine it's original address back. Someone else had mentioned that I could have also changed the servers adapter info in Mystic's Server Comfig to get it
    going on the new interface, but giving it it's original address saved having to reconfigure several other non-BBS things. Just a thought the left cornfield.

    I figured out the problem, the IP Address for the services needed to be changed.

    Born too late to experience the scene.
    Born just in time to see it come back.
    Nodoka Hanamura - NeoCincinnati BBS SYSOP - neocinci.bbs.io

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
    * Origin: NeoCincinnati BBS - neocinci.bbs.io:23 (21:2/106)