"I see the list of stations, but every time
I try to connect to one, I get a "Connect attempt failed" message after 30
seconds. What's the problem?"
"My node is running fine, except that it seems that I can only initiate a connection to another
station; my node doesn't accept connection requests from others."
Most likely, a problem with your network set-up is preventing your node from
receiving messages from other stations over the Internet. This is a very
Please note that this is not a problem with the EchoLink
For this reason, the EchoLink Support team
will not be able to help you solve it. However, the information on this
page might help. It's also recommended that you first try the
Firewall/Router Test Page on this site.
The solution depends on what kind of hardware and software you are
using for your Internet connection. Unfortunately, many different
hardware and software products may be involved, so it is not possible to
document every solution. A few of the most common situations are listed
EchoLink requires that your router or firewall allow inbound and
outbound UDP to ports 5198 and 5199, and outbound TCP to port
5200. If you are using a
home-network router, you will also need to configure the router to "forward"
UDP ports 5198 and 5199 to the PC or device on which EchoLink is running. (Do not forward TCP 5200).
This can be summarized as:
Allow UDP destination ports 5198-5199 between Internet and EchoLink node in both directions
Forward UDP 5198-5199 to your EchoLink node
Allow TCP (source port any, destination port 5200) from EchoLink node to Internet
The information above applies to every situation, regardless of the
type of equipment and software you are using. If the information below
does not help you solve the problem, please consult your equipment's
documentation, or contact the manufacturer for support, and provide them with
the information above.
Note: If you are using Internet security software and have
recently upgraded to a newer version of EchoLink, you may need to re-apply the
special security settings you had established earlier.
DSL, Fiber, and Cable Modem Service
If you connect to the Internet using DSL, Fiber, or Cable Modem service,
there might be a router built into the equipment that the telephone company or cable company provided you.
For example, some of the equipment provided by Comcast and Verizon have built-in routers. Check the make and model of your modem or router, and then look for instructions
on one of the Web sites described below.
Cellular and Satellite Service
If you connect to the Internet using cellular or satellite service, such as T-Mobile or Starlink,
there are some special challenges due to the use of CGNAT. For more information, please see Internet Service Providers.
Learning About Port Forwarding
There are some good resources on the Internet for learning about port forwarding, with some step-by-step instructions for how to set it up:
How to Port Forward provides a good overview. But when you get to Step 5, please use the EchoLink Firewall/Router Test page instead.
How to Forward Ports on Your Router might also be helpful.
A useful Web site that discusses port forwarding, with solutions for
specific makes and models of equipment, is www.portforward.com. Choose EchoLink from the list of applications, then select
the make and model of your equipment. (Please note that portforward.com is not
affiliated in any way with EchoLink; we recommend that you use the portforward.com Web site as an information resource, and not necessarily for the optional configuration software being sold on that site.)
Windows comes with a built-in "firewall" feature that helps
protect your computer from undesired connections from the Internet. In
order to use EchoLink, you will need to adjust some settings if the built-in
firewall is enabled. This is normally done automatically during installation,
but in some cases, you might need to manually add an "exception" for the EchoLink.exe software.
Problems With Some Connections, And Not Others?
If you router isn't properly configured, you might that you are
able to connect to some stations on EchoLink, but not others. For more
information about this, please see the article
"Echolink, Firewalls, and Routers."
Satellite Internet Service Providers
Many users are successfully running EchoLink using an Internet
connection provided through a satellite dish. Although the latency (time
delay) is usually higher with this type of system, it rarely affects EchoLink
since EchoLink does not use end-to-end acknowledgements of voice packets.
However, some service providers use a router which does network-address
translation (NAT), which often cannot be configured by the customer.
Check with your satellite ISP to see if this is the case, and whether a
different tier of service is available which will avoid it.
For more information, see: