Surfboard router with telnet inbound setup
Synchronet's terminal log shows no incoming telnet on port 23.
I'm about to give up on running this system I cannot get it to accept incoming calls.
Running Windows 10
Latest version of SSBS for Windows
Surfboard router with telnet inbound setup
Synchronet's terminal log shows no incoming telnet on port 23.
I've tried a diff port and still no luck.
I've turned off the windows firewall and no luck.
I even call comcast to see if there blocking it, and they said no.
I'm about to give up on running this system I cannot get it to accept incoming calls.
Running Windows 10
Latest version of SSBS for Windows
Surfboard router with telnet inbound setup
Synchronet's terminal log shows no incoming telnet on port 23.
I've tried a diff port and still no luck.
I've turned off the windows firewall and no luck.
I even call comcast to see if there blocking it, and they said no.
Does anyone have any idea what could be wrong?
Re: Incoming calls
By: Richard Vonzel to All on Sun Jan 24 2021 08:56 am
Surfboard router with telnet inbound setup
Synchronet's terminal log shows no incoming telnet on port 23.
Can you access it from another device behind the router over the local LAN, ie 192.168.x.x address? I think that'd narrow down the culprits pretty well and give us somewhere to focus
----------------------
United Kingdom BBS: ukbbs.zapto.org:64 (40cols) ukbbs.zapto.org:128 (80cols)
Can you access it from another device behind the router over the local LA ie 192.168.x.x address? I think that'd narrow down the culprits pretty we and give us somewhere to focusI am able to access as a localhost. Works great thay way.
Synchronet's terminal log shows no incoming telnet on port 23.
I've tried a diff port and still no luck.
I couldn't say just what is up there but it sounds like a port forwarding or firewall issue. If you keep at it I think you'll get to where you want to go.
Internally, does your BBS respond on port 23? From another computer in the house, go to a command prompt and test.
I've heard that Comcast blocks port 23. My recommendation is to create a
The only option is to use a non standard port with that router. I had to do the same with the ssh port for the same reasons.
At some point I'll get a new router and revisit all that.
I couldn't say just what is up there but it sounds like a port
forwarding or firewall issue. If you keep at it I think you'll get to
where you want to go.
I've heard that Comcast blocks port 23. My recommendation is to create a port forward from external to internal on something like 2023 or 2323 to translate to 23. Try again.
Can you access it from another device behind the router over the local LA ie 192.168.x.x address? I think that'd narrow down the culprits pretty we and give us somewhere to focusI am able to access as a localhost. Works great thay way.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 409 |
Nodes: | 16 (3 / 13) |
Uptime: | 47:05:34 |
Calls: | 8,570 |
Calls today: | 10 |
Files: | 13,222 |
Messages: | 5,929,003 |