There appears to be a bug in the PC-Micro "Net2bbs"
program, where after long
periods of operation it just randomly decides to refuse
Telnet connections
coming from the website... the Flash operation on port 843.
I understand that the author is busy with real-life, so the
only workaround I
can think of is to script something that restarts Net2bbs.
The issue you describes sounds like a recently reported issue with the AntiScanner feature, which has been fixed in the current beta.
In the last few release versions of Net2BBS blocking sockets were used by default which caused that AnsiScanner feature to sometimes make a false-positive and thus add the IP address of the offending client to it's temporary block-cache.
I suggest you just edit your net2bbs.ini to include "AntiScanner=0" to avoi the false positive, or join the NetFoss mailing list to get the latest beta am planning to put out a release version shortly.
The issue you describes sounds like a recently reported issue with the AntiScanner feature, which has been fixed in the current beta....
I suggest you just edit your net2bbs.ini to include "AntiScanner=0" to avoid the false positive, or join the NetFoss mailing list to get the latest beta. I am planning to put out a release version shortly.
They are already set at zero. The program is still unstable.
You didn't mention which version you are running, but if it's the latest public beta version 1.20b11 then I suggest you try version 1.16 which had n known issues. You can download it from Netfoss.com
Check your net2bbs log file to see if it shows the IP address of your web server next to a "Connection Refused" message, and it should list a reason the refusal next to it. Feel free to email me about it.
This was with 1.14. I just upgraded to 1.16 now.
When Net2BBS refuses to answer/accept connections, nothing is written
in the log showing an explanation why. It is totally random and again
it appears only happen after weeks or a months of continuous operation.
I understand that the author is busy with real-life, so the only workaround I can think of is to script something that restarts
Net2bbs.
Ah ok, I thought it was only blocking your web server IP. It sounds like the socket is no longer listening for incoming connections for some reason. Let me know if you see it occurring in version 1.16.
By the way, are you running Net2BBS as a Desktop app or as a service?
I understand that the author is busy with real-life, so the only
workaround I can think of is to script something that restarts
Net2bbs.
Mike's an active member of my BBSing 2.0 group on Facebook; I'll
pass this on to him.
Apparently he is an active member here, too! :)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,056 |
Nodes: | 17 (1 / 16) |
Uptime: | 06:24:30 |
Calls: | 501,030 |
Calls today: | 17 |
Files: | 109,384 |
D/L today: |
9,931 files (1,217M bytes) |
Messages: | 304,942 |
Posted today: | 2 |