re: connection time out even on echotest

[KC7BYP]

My internet connection is via a Sprint USB cell phone type modem. I have Zone Alarm pro installed. All ports in ZA are set. I have setup Echolink before with a dialup modem and a cable modem. This is the 1st time with this Sprint modem. The Sprint modem works fine for everything else. I have tryed shutting down ZA and run the computer completly naked to the internet and Echolink sees the list but I still get connection time out on every connection, even on echotest.
Bellow is the resultes of the Echolink troubleshooter prog.

IP: 192.168.1.150
TCP Test: Succeeded.
UDP Test (5198): Succeeded.
UDP Test (5199): Receive failed (10060).
Tests complete

I have a question. My printers are connected to this computer via an ethernet router. My primary isp is Charter cable modem. Echolink works just fine on the cable modem. The cable modem is disabled untill the bill is caught up so I am running the portable usb modem right now.
Question Is echolink getting confused as to which modem to use?

Steve kc7byp

[K1RFD]

The 192.168.1.x address does look suspiciously like your LAN rather than the cell modem. EchoLink itself doesn't choose the network interface if your computer has more than one; this is controlled by the Windows routing table. I suppose it's possible that the Firewall Test is showing you the wrong IP.

If you want to verify which interface is being used by EchoLink, one way to check is to find yourself in the Station List after the software starts, then mouse over your call (or right-click) to see your public IP address or host name.

Some cell modems give you a true public IP address, while others give you a private address that is mapped to a public address shared by other users, similar to a coffee shop or hotel. If that's the case, your only option in this version of EchoLink is to choose a public proxy.

[KJ4VKC]

Try disabling your ethernet connection and any other ones (right click the connection and choose "disable". It's the icons that look like a sheet of paper with a computer monitor and either an antenna or a T-connector coming out from it. Titled Network Connections on XP.) before starting Echolink so that the only enabled one is the modem. This should force Echolink to use it.

[KD8DEY]

Echolink uses 3 ports 5198 5199 5200
I had to add exceptions to all 3 ports in windows firewall manually to make sure every thing worked ok not just the exception for the program itself

echolink only adds the exception

echolink
C:\Program Files\K1RFD\EchoLink\EchoLink.exe

I added the exceptions below to windows firewall to make sure all the needed ports were open as well

Echolink1 port 5198 UDP
Echolink 2 port 5199 UDP
Echolink3 port 5200 TCP

[K1RFD]

Echolink uses 3 ports 5198 5199 5200

Echolink1 port 5198 UDP
Echolink2 port 5199 UDP
Echolink3 port 5200 TCP

Note that only the first two are necessary for inbound routing. The 5200 TCP is used outbound only. Most firewalls and routers will allow outbound TCP connections without additional configuration.

[N0WYO]

Note that only the first two are necessary for inbound routing. The 5200 TCP is used outbound only. Most firewalls and routers will allow outbound TCP connections without additional configuration.


Also, if you are using a router, disable windows firewall. The router has it's own firewall, and port forwarding can get a bit confusing running through two firewalls.

[N0IU]

I still haven't resolved this problem so I just gave up, but this certainly doesn't mean you have to give up on EchoLink because you can always connect through a proxy server.

Open EchoLink, go to Tools then Setup... (or press Alt + E) then select the Proxy tab. Select the Choose Public Proxy option. Click the dropdown arrow and you will see a list of several proxy servers from which to chose. Be aware that the proxy you choose this time may not be available next time. If that happens, you will get a pop-up like this.

http://i676.photobucket.com/albums/vv124/scottaschultz/proxy.jpg

All you do is go back into Setup and pick another proxy server.

Good luck!

[KE7VLC]

My internet connection is via a Sprint USB cell phone type modem. I have Zone Alarm pro installed. All ports in ZA are set. I have setup Echolink before with a dialup modem and a cable modem. This is the 1st time with this Sprint modem. The Sprint modem works fine for everything else. I have tryed shutting down ZA and run the computer completly naked to the internet and Echolink sees the list but I still get connection time out on every connection, even on echotest.
Bellow is the resultes of the Echolink troubleshooter prog.

IP: 192.168.1.150
TCP Test: Succeeded.
UDP Test (5198): Succeeded.
UDP Test (5199): Receive failed (10060).
Tests complete

I have a question. My printers are connected to this computer via an ethernet router. My primary isp is Charter cable modem. Echolink works just fine on the cable modem. The cable modem is disabled untill the bill is caught up so I am running the portable usb modem right now.
Question Is echolink getting confused as to which modem to use?

Steve kc7byp

Well if it works by using your cable modem but not through your Sprint Cell modem then perhaps it's not an issue on your end but rather something that Sprint wont allow through.

It's like that old Sesame street song....."One of these things are not like the other". So when you look at your computer what has changed? The only thing that I can tell has changed is the modem. So if you don't change any settings and go back to the cable modem and everything works then it's got to be an issue with the new item.

Sir Authur Conan Doyle once said "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. "

So if something doesn't go right, go back to the last time it was working and then elliminate anything that has changed.

I would say it has something to do with Sprint.

[KH6OWL]

I still haven't resolved this problem so I just gave up, but this certainly doesn't mean you have to give up on EchoLink because you can always connect through a proxy server.

Open EchoLink, go to Tools then Setup... (or press Alt + E) then select the Proxy tab. Select the Choose Public Proxy option. Click the dropdown arrow and you will see a list of several proxy servers from which to chose. Be aware that the proxy you choose this time may not be available next time. If that happens, you will get a pop-up like this.

http://i676.photobucket.com/albums/vv124/scottaschultz/proxy.jpg

All you do is go back into Setup and pick another proxy server.

Good luck!

Thanks for the tip. After setting up my wireless router with the security my echolink stopped working. It was fine util I secured it. I did the port forwarding and all but nothing worked. I can use the public proxy and connect again. Thanks