Home |
Search |
Today's Posts |
|
#1
![]() |
|||
|
|||
![]()
On 5 Mar 2005 20:37:07 -0800, " wrote:
I just got a ham friend to install echolink and he's having a problem that I've never seen. He can bring echolink up and sees all the stations that are logged in. He has my call in his favorites and when he clicks on my call the problem happens. On clicking, I get a connect and everything looks good on my end, but on his end it says connecting and then times out after 50 seconds. This happens with the test server also. We had configured his router for ports 5198,5199, & 5200 and disabled the windows and norton firewalls, but to no avail. Does anyone have any ideas as to why he's having the problem. By the way, he has a linksys wireless router and is on bellsouth DSL. What is the IP Bellsouth assigns him? If it is 10.x.x.x or 192.168.x.x then he is being double-firewalled and will likely have to use a proxy. Many DSL users in this area (Georgia) have this problem. On my system, I had to set my firewall router up with a DMZ to my computer and use Norton firewall to keep the script kiddies out. (I am not on DSL, but cable.) -- 73 for now Buck N4PGW |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Noise Problem on 11955kHz | Shortwave | |||
HELP: 2 meter repeater intermod problem from pager transmitters | General | |||
OT EMI problem with stove and internet connection | Homebrew | |||
Echolink problem | General | |||
Echolink and ATV on The ISS project | General |