A second FIDOnet connection alternates between a timeout error
and a no route to host error.
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.
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.
DNS is setup incorrectly perhaps. You cannot solve either of these errors.
The third is for another network, and consistently gives a notHotdoged requires an MD5 handshake. If your host has an option for
authorized error, even though my host an I have verified all the
information is correct.
MD5 (like Mystic) ask your host to turn it on for your point.
Hello, All.
I asked about this problem here a year or so ago, bit still am having the same issue, only different.
I have 3 connections I am setting up on HotdogEd. This one, obviously is working with no issue.
A second FIDOnet connection alternates between a timeout error and a no route to host error.
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.
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.
Amy ideas?
...
--- Hotdoged/2.13.5/Android
* Origin: The Oasis, Houston, Texas, USA (2:240/1120.976)
Hello, Charles Pierson. On 11/06/2020 17.36 you wrote:
Do you need fourth one? :)
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.
Do you need fourth one? :)
2 are FIDOnet, the 3rd is another network.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 577 |
Nodes: | 10 (1 / 9) |
Uptime: | 56:14:53 |
Calls: | 9,294 |
Calls today: | 2 |
Files: | 16,016 |
Messages: | 1,046,582 |