On 06/24/17, Wilfred van Velzen pondered and said...
Wv> Hi All,
Wv>
Wv> When I try to connect to a particular "Mystic/1.12A34 binkp/1.0" system,
Wv> all I get is this:
Wv>
Wv> + 24 Jun 20:57:40 [30502] call to ***
Wv> 24 Jun 20:57:40 [30502] trying ***...
Wv> 24 Jun 20:57:40 [30502] connected
Wv> + 24 Jun 20:57:40 [30502] outgoing session with ***
Wv> ? 24 Jun 20:57:41 [30502] recv: Connection reset by peer
Wv> + 24 Jun 20:57:41 [30502] holding *** (2017/06/24 22:57:41)
Wv> + 24 Jun 20:57:41 [30502] done (to ***, failed, S/R: 0/0 (0/0 bytes))
Wv> 24 Jun 20:57:41 [30502] session closed, quitting...
Wv>
Wv> Is this a known problem maybe? Or what could it be?
Wv>
Wv> When he polls mine it seems to work...
Check with the admin that your IP address has not ended up in badip.txt in
the data dir of Mystic. If it has he should remove it and restart his MIS.
If you are on a static IP let him know what it is and get him to add it to
goodip.txt in the mystic data dir.. he may need to create the txt file from
scratch.
Best, Paul.
--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)
|