Do you have that port forwarded on your router for your BBS machine?
Jeff

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Hello Sparky.

08 May 21 09:59, you wrote to TheMadGamerMan:

Do you have that port forwarded on your router for your BBS machine? Origin: Communicatin Connection 21:100/192 (21:1/192)

^^^^^^^^^^ ^^^^^^^^
wut? :)



Daniel

--- GoldED/2 3.0.1
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

Origin: Communicatin Connection 21:100/192 (21:1/192)

wut? :)

I'll have to check that out, I am just getting set up to carry USENET feeds so I might have fat fingered something somewhere.
Jeff

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Hi,

I seem to be having an issue with my Bell Internet and Mystic. I can poll all my networks, for mail but I cannot receive any incoming connections. My BBS uses port 2323, I use noip as my dns client, it tells me all is ok. The client points to my WAN IP address not sure why.

Mark

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Help please
By: TheMadGamerMan to All on Sat May 08 2021 02:35 pm

I seem to be having an issue with my Bell Internet and Mystic. I can poll all my networks, for mail but I cannot receive any incoming connections. My BBS uses port 2323, I use noip as my dns client, it tells me all is ok. The client points to my WAN IP address not sure why.

Your DNS service should point to the IP where your BBS is running. You may also need to open or forward those incoming calls on your router or firewall. My router calls it port forwarding. Adjust the setup to send those incoming calls on the ports you want to your BBS machine.

A typical BBS will need that for port 23 for the BBS and 24554 for the mailer and there could be others also.

Ttyl :-),
Al

... Math problems? Call 1-800-10*(24+13)-(64-16)/2^14E2.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

That sounds like a port forwarding issue. Are you certain you've
forwarded the ports on your router? Opening the firewall /= setting NAT.

Positive. I think I fixed it.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Point Of No Return (21:2/102)

Connecting via the local IP address locally is a good suggestion, some (many?) routers don't support hairpin(?) nat, so while the outside world will get forwarded via your outside IP to the internal BBS, machine on
the inside wont.

I *think* I may have solved it.

Mark

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Point Of No Return (21:2/102)

Do you have that port forwarded on your router for your BBS machine?
Jeff

Yes, even tried changing it a few times.

Mark

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Point Of No Return (21:2/102)

Your DNS service should point to the IP where your BBS is running. You
may also need to open or forward those incoming calls on your router or firewall. My router calls it port forwarding. Adjust the setup to send those incoming calls on the ports you want to your BBS machine.

I have that open in Bells firewall in the modem (port 2323/24554 for
binkp) the port utility on Noip's app see's it open. This is why I am scratching my head.

Mark
TheMadGamerMan

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Help please
By: TheMadGamerMan to Al on Sat May 08 2021 11:06 pm

I have that open in Bells firewall in the modem (port 2323/24554 for binkp) the port utility on Noip's app see's it open. This is why I am scratching my head.

Is your router directing traffic on those ports to your BBS machine?

Ttyl :-),
Al

... Always remember to pillage BEFORE you burn.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

I seem to be having an issue with my Bell Internet and Mystic. I can
poll all my networks, for mail but I cannot receive any incoming connections. My BBS uses port 2323, I use noip as my dns client, it

1: make sure all your nodes are not locked up with ghost users .
2: If testing this your self make sure your IP is not in the black list
3: if connection to test locally from with in the same home network dont use the boards addy , if internally test use the internal IP addess . So if using netrunner instead for using Error1202bbs.DDns.net:1202 I would use 192.167.1.79:1202 .

Hope that helps

Sysop SolaRis
Error 1202 and Error 404 BBS !
FSXnet HuB 2 Tholian AdmiN !

--- Mystic BBS v1.12 A46 2020/08/25 (Windows/64)
* Origin: Error 1202 BBS (21:2/1202)

Is your router directing traffic on those ports to your BBS machine?

I think I resolved it.

Mark

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

1: make sure all your nodes are not locked up with ghost users .
2: If testing this your self make sure your IP is not in the black list 3: if connection to test locally from with in the same home network dont use the boards addy , if internally test use the internal IP addess . So if using netrunner instead for using Error1202bbs.DDns.net:1202 I would use 192.167.1.79:1202 .

Ok, will give all the above a go.

Mark

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Point Of No Return (21:2/102)

On Sat, 8 May 2021 23:06:52 +1200
"TheMadGamerMan" <themadgamerman@21:1/101> wrote:

Your DNS service should point to the IP where your BBS is running. You may also need to open or forward those incoming calls on your router or firewall. My router calls it port forwarding. Adjust the setup to send those incoming calls on the ports you want to your BBS machine.

I have that open in Bells firewall in the modem (port 2323/24554 for binkp) the port utility on Noip's app see's it open. This is why I am scratching my head.

That sounds like a port forwarding issue. Are you certain you've forwarded the ports on your router? Opening the firewall /= setting NAT.
--- SBBSecho 3.14-Linux
* Origin: The Undermine - bbs.undermine.ca (21:4/103)

Ok, will give all the above a go.

Connecting via the local IP address locally is a good suggestion, some
(many?) routers don't support hairpin(?) nat, so while the outside world
will get forwarded via your outside IP to the internal BBS, machine on
the inside wont.

So, while No-Ip can see your port open, you locally connecting to the
outside IP (or hostname) wont work, if you have a router like that.

If you want to use a hostname that resolves to your outside IP, to get
around it on your LAN, you can edit the hosts file to resolve the
hostname to the lan ip locally - it's not necessary if you're good at remembering IP addresses, or have it bookmarked I suppose :P

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.21-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)