Not sure what this binkd log means or tells me maybe some else or g00r00 does?

Apparently I've been having a connection issue for survnet and just now
noticed it. This is what's showing in my BinkD logs.

+ 04 Jul 20:34:33 [1304] call to 9:91/1@survnet
04 Jul 20:34:33 [1304] trying fluph.darktech.org [74.194.189.150]...
04 Jul 20:34:33 [1304] connected
+ 04 Jul 20:34:33 [1304] outgoing session with 74-194-189-150.chstcmtk03.res.dyn.suddenlink.net [74.194.189.150]
? 04 Jul 20:34:33 [1304] recv: {W32 API error 10054} An existing connection
was forcibly closed by the remote host
+ 04 Jul 20:34:33 [1304] done (to 9:91/1@survnet, failed, S/R: 0/0 (0/0
bytes))

Sometimes it's that API error, sometimes it's this one instead.

? 04 Jul 20:35:33 [2812] recv: connection closed by foreign host

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: flupH | fluph.darktech.org (21:1/105)

On 07/18/17, Skuz said the following...

? 04 Jul 20:34:33 [1304] recv: {W32 API error 10054} An existing connection was forcibly closed by the remote host

Check to make sure your IP isn't listed in the BADIP.TXT file in
\mystic\data\. I've seen that a couple times, and that has been the issue.


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS (RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 07/18/17, Black Panther said the following...

? 04 Jul 20:34:33 [1304] recv: {W32 API error 10054} An existing connection was forcibly closed by the remote host

Check to make sure your IP isn't listed in the BADIP.TXT file in \mystic\data\. I've seen that a couple times, and that has been the
issue.

Nice guess, but that is not the reason. His IP is only in my goodip.txt and whitelist.txt His system is madness.synchro.net and that matches with a amazonaws.com domain name. When I try to do a simple ping on the node domain name I get...

PING madness.synchro.net (54.83.145.1) 56(84) bytes of data. --- madness.synchro.net ping statistics ---
packets transmitted 9
received 0
packet loss 100 %
time 8014 ms

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: flupH | fluph.darktech.org (21:1/105)

Hello Skuz,

Nice guess, but that is not the reason. His IP is only in my goodip.txt and whitelist.txt His system is madness.synchro.net and that matches with a amazonaws.com domain name. When I try to do a simple ping on the node domain name I get...
PING madness.synchro.net (54.83.145.1) 56(84) bytes of data. --- madness.synchro.net ping statistics ---
packets transmitted 9
received 0
packet loss 100 %
time 8014 ms

I tried that FQDN from here also and got:

PING madness.synchro.net (54.83.145.1) 56(84) bytes of data.
-+- 54.83.145.1 ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 13001ms

It would seem that although the domain name resolves to an IP the destination is not responding.

Jeff


--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

Hello Jeff!

18 Jul 17 23:20, you wrote to me:

Hello Skuz,

Nice guess, but that is not the reason. His IP is only in my
goodip.txt and whitelist.txt His system is madness.synchro.net and
that matches with a amazonaws.com domain name. When I try to do a
simple ping on the node domain name I get... PING
madness.synchro.net (54.83.145.1) 56(84) bytes of data. ---
madness.synchro.net ping statistics --- packets transmitted 9
received 0 packet loss 100 % time 8014 ms

I tried that FQDN from here also and got:

PING madness.synchro.net (54.83.145.1) 56(84) bytes of data.
-+- 54.83.145.1 ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 13001ms

It would seem that although the domain name resolves to an IP the destination is not responding.

It would seens that is the case, I've been processing mail/files+tic with other

binkd systems (1:261/38@filegate.net) for example with know issues or problems, on this Mystic system for many years now. I have know clue why this amazonaws.com domain from the synchronet system is having binkd problems with my mystic survnet node. When others do not.. anyway his binkd log shows the ? Date and time [1304] recv: {W32 API error 10054} An existing connection was forcibly closed by the remote host done to 9:91/1@survnet (me) failed, S/R: 0/0

(0/0 bytes)) He says that sometimes it's that API error, and sometimes it's this one instead. ? Date time [2812] recv: connection closed by foreign host.

-Les

--- GoldED+/W32-MSVC 1.1.5-b20160201
* Origin: flupH * fluph.darktech.org (21:1/105)

On 07/18/17, Skuz said the following...

On 07/18/17, Black Panther said the following...

Nice guess, but that is not the reason. His IP is only in my goodip.txt and whitelist.txt His system is madness.synchro.net and that matches
with a amazonaws.com domain name. When I try to do a simple ping on the node domain name I get...

PING madness.synchro.net (54.83.145.1) 56(84) bytes of data. --- madness.synchro.net ping statistics ---
packets transmitted 9
received 0
packet loss 100 %
time 8014 ms

The reason you can't ping it is most likely because there is nothing running
on that IP address to respond to a ping (stale hostname/dns) most likely

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)