MSGID: 2:221/6.50 024c6117
PID: Hotdoged/2.13.5/Android
TID: jNode/Android
CHRS: CP866 2
REPLY: 2:240/1120.976 37992b01
Hello, Charles Pierson.
On 11/06/2020 17.36 you wrote:

 CP> Hello, All.
 CP> I asked about this problem here a year or so ago, bit still am having the
same issue, only different.
 CP> I have 3 connections I am setting up on HotdogEd. This one, obviously is
working with no issue.

Do you need fourth one? :)
 
 CP> A second FIDOnet connection alternates between a timeout error and a no
route to host error.
 CP> The third is for another network, and consistently gives a not authorized
error, even though my host an I have verified all the information is correct. 
 CP> I used the same data with Aftershock on the last 2 as well. The 2nd still
times out, but the 3rd connects and I receive messages, but apparently have
nothing going out.
 CP> Amy ideas?
 CP> ...

I have seen a connetion problem when server has an AAAA record but doesnt
accept ipv6 connections. Even if there is a working ipv4 server, hotdog doesnt
try it.

 CP> --- Hotdoged/2.13.5/Android
 CP>  * Origin: The Oasis, Houston, Texas, USA (2:240/1120.976)

--
 Tommi
--- Hotdoged/2.13.5/Android
 * Origin: Point .50, Somewhere (2:221/6.50)
SEEN-BY: 1/123 90/1 120/340 601 123/131 203/0 221/0 1 6 360 226/30
SEEN-BY: 227/114 702 229/424 426 452 664 1014 230/0 240/77 1120 1634
SEEN-BY: 240/5138 5832 5853 8001 8002 8005 249/206 317 400 261/38
SEEN-BY: 280/5003 310/31 313/41 317/3 320/219 322/757 335/364 342/200
SEEN-BY: 423/81 633/280 2452/250 2454/119 2490/3045 4500/1 5020/1042
PATH: 221/6 1 240/1120 5832 229/426