Hi Richard,
For the record, the ports you need to enable are:
5198 and 5199 UDP
5200 TCP.
It sounds like somewhere along the way, either your router (if you have one)
or your firewall are blocking incoming port 5198.
I am using Road Runner with Trend Micro Internet Security Suite 2007 and a
Linksys Router and properly configured, this set up works just fine with
Echo Link.
----- Original Message -----
From: "Richard Fiorello" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, August 15, 2007 5:15 PM
Subject: Fw: echo link
Hi;
I have been fiddling with echo link with little success. I believe the
necessary ports are enabled. When I open the program I see a list of
available stations and when I try and connect I simply time out. When I
time out, however, I get audio and cw back from echo link stating that I
have timed out so it would "seem" that info is going both ways.
I ran the diagnostic program, however, and was informed that the udp port
5198 failed.
I think I'm stumped.
Richard
----- Original Message -----
From: "Donald Breda" <[log in to unmask]>
To: "Richard Fiorello" <[log in to unmask]>
Sent: Saturday, July 28, 2007 6:45 AM
Subject: Re: echo link
Hi Richard.
Remember that with dynamic tcpip your machines address can change.
This could cause the problem.
If you opened the ports for 192.168.0.100 and your machines address changes
because of a reboot or another machine having been on that is not now and
you have rebooted the dhcp server in the router can
give your machine a different address.
So if it now becomes 192.168.0.101 the ports are not opened for that
address.
Going in to the router and changing the address in the port forwarding
screen will fix thsat if that is your problem.
Of course if your router supports port triggering instead of port forwarding
it might be better to use that since the router will find you when the
echolink requests come in.
Don
On Fri, 27 Jul 2007 21:34:05 -0500, Richard Fiorello wrote:
>Hi;
>If I did things correctly the ports should be open so I'm wondering if I
>inadvertently changed some other setting.
>Will have to investigate further.
>Richard
>----- Original Message -----
>From: "Donald Breda" <[log in to unmask]>
>To: <[log in to unmask]>
>Sent: Friday, July 27, 2007 7:06 PM
>Subject: Re: echo link
>Rich, the latest version of echolink has the firewall tester built in to
>it.
>If you haven't opened the ports in your router though then that is the
>problem. You must do that or it won't work. The only way around that is to
>use one of their proxy servers.
>Don
>On Fri, 27 Jul 2007 19:19:31 -0500, Richard Fiorello wrote:
>>Hi;
>>no, haven't looked at that program but that's a thought.
>>Thanks for the info
>>Richard
>>----- Original Message -----
>>From: "Bob Martin" <[log in to unmask]>
>>To: <[log in to unmask]>
>>Sent: Friday, July 27, 2007 4:21 PM
>>Subject: Re: echo link
>>Richard:
>>I don't recall seeing that feature, but, did you download and run their
>>diagnostic program?
>>Good luck and 73
>>Bob Martin
>>KC3FI
>>EchoLink Node - 55127
>>Please visit http://www.wan-leatonks.net.
>>----- Original Message -----
>>From: "Richard Fiorello" <[log in to unmask]>
>>To: <[log in to unmask]>
>>Sent: Friday, July 27, 2007 5:58 PM
>>Subject: echo link
>>> Hi;
>>> I am still having some echo link adventures. When I looked at the
>>> program
>>> prior to vacation there seemed to be a option to return things to their
>>> original settings. Due to a sudden brain freeze can't find that option.
>>> I
>>> thought I'd try that first prior to fiddling with my router.
>>> Richard
>>>
|
