On 2017 Sep 30 22:06:10, you wrote to me:

 ml>> we also need to see what the other side's log looks like... also,
 ml>> make sure that CRAM-MD5 is not forced...
 TP> I have no idea how to export Aftershock's logfiles... ? It looks about
 TP> the same, but there's also a line that looks like this:

 TP> OPT MB CRAM-MD5-xxxxxxxx

that seems to indicate that the IREX system is looking for or requesting a
CRAM-MD5 session...

 TP> Then a minute after the "VER Internet Rex..." line, it says "session
 TP> timeout"

check if aftershock can do CRAM-MD5... if so, see if it is enabled for this
uplink system...

 TP>>> % 16:20:26  BinkP: 2:292/8125.1fidonet

 ml>> unless this is a typo, the above address is not a proper 5D FTN
 ml>> address... it is missing the '@' on "fidonet"...
 TP> In the Aftershock settings, I just put "2:292/8125.1" as the local
 TP> fidonet address. I guess the app adds the fidonet part. I just changed
 TP> it to the proper 5D notation, the log fine looks fine now, but the
 TP> session still times out..

ok... let's see what you find with the above information...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... I'm moving to Mars next week, so if you have any boxes...
---
 * Origin:  (1:3634/12.73)