ECHOLINK cannot be connected

[OK2SBT]

Probably before 2 for years there was no problem connecting to all nodes. As time progresses, nothing works anymore - UDP ports 5198-5199 TCP 5200, firewaly atp. all right . The time trial passes and that's it. For example, TRACERT writes 5 lines to some node, then there is a line from NIX followed by another line with the starting address. So it goes back to the beginning. Concretely 213.29.20.145 OK0BAB-R .
So far I have not been able to get any information about what is happening on Echolink and the network. I'm not the only one who doesn't like Echolink. Chat advice, ICQ atd. they are useless - it needs to be done verbally via SKYPE - if there is someone who controls the issue and is willing to advise, he will be happy. My SKYPE nick name = pfname .

Thank you for the positive response.

[IVULIK]

All Echolink converters work.(Now it is only being repaired by Echolink in Žatec).So the fault must be with your Internet provider).
OK1IVU

[OK2SBT]

If I look at the communication between my PC and the echolink I can see, from the effort of a TCP packet 5200 projit ended up on some secure server, from where the packets are returned to me again. I like these things, but it seems to me as if the secure server won't let it go. Intuitively, I relate it to PAYPAL users. I can't say since when it doesn't work, because I haven't used it in a while, but I only have such a feeling. Na zadneho sysopa shown echonodu, who would be willing to communicate about things, I have no contact. He wants it via Skype, because via chats and e-mails it is long-winded and unusable. It needs someone who knows the sitar well. And I don't get such contacts. I take it as a sport and an impulse to increase my social skills.
Thanks for any message.

[OK2SBT]

Thanks to the willingness of OK1IVU and his knowledge, it was confirmed, that the unavailability on Echolink in my case causes the use of PAYPAL, which affects the secure server so, that to me through the TCP port 5200 won't let go. This makes it impossible to connect to Echolink.

[Anonymous]

You don't happen to have UDP packets blocked by the provider ?
This is exactly what I was dealing with.
I have mobile internet from T-Mobile ( Flarion ) if I connect through this internet, nacita node list, but cannot connect to any.
At the first launch, a firewall test was performed and it said that, that there is a problem with UDP.
The second attempt followed on the connection from UPC (hello) and everything works without problems.

[Anonymous]

That contribution about UDP was from me, if you happen to have any other questions 🙂

[OK2SBT]

I follow UDP and after the TCP packet help connection, because it doesn't work.
Here is an extract from SNIFFER.
1–nine packets TCP ip-68-178-144-151.ip.secureserver.net SYN pfamd 5200 => 1156 62
2–he packet TCP pfamd SYN ip-68-178-144-151.ip.secureserver.net 1156 => 5200 62
This is repeated several times and the port 1156 depends on the value 1183. This means that secureserver is scanning my TCP ports in the range 1156-1183 and as I observe it also gave if I leave the echolink running.
Cili this ip-68-178-144-151.ip.secureserver.net does not enable echolink connection. Please note that this is my layman's view.
I add to that, that according to me, I have everything correctly set and checked in the PC. I tried it without firevalue from the advice center with uninstalled AVASTE and it's still the same. Echolink doesn't work. It's probably a poltergeist.

[OK2SBT]

My administrator made some changes and that's why it doesn't work, that the secure server does not yet have the proserver domain indexed, so echolink won't let go. They say it's being worked on.

[Author]

Posts