- #ECHOLINK APP FOR APPLE ANDROID#
- #ECHOLINK APP FOR APPLE PC#
- #ECHOLINK APP FOR APPLE MAC#
- #ECHOLINK APP FOR APPLE WINDOWS#
It is technically of interest to me, but not enough to carry the torch. If it were something critical to my needs, I would fight this battle.but it isn't. I am sorry I am not contributing anything to the OP issue, except to confirm it is apparently a common problem, as I expected.when all COMPUTERS can connect with no problem, and I can control my HF rig remotely with no problem, clearly it isn't a router problem per se, so this is where I get off.been there, done that.not gonna fiddle with my router or change my ISP and mess up a system that works fine in every OTHER respect except this one issue with cell phones. Someone who isn't jaded and entirely sick of this kind of issue can probably solve it if they are willing to spend enough time! I spent 20 years in IT and I've done my time in TCP/IP Heck. That -R is linked 24/7 to my node, so we have that workaround hence I'm not going to stew about it nor delve into the intricacies of this problem. However, EVERYONE CAN connect using those devices to a local -R.
#ECHOLINK APP FOR APPLE ANDROID#
Another ham friend nearby cannot connect to HIS own -L node using his Android phone, either. My son who is a ham, cannot connect to my -L node using his iPhone nor his iPad. ) Replace this all in one dsl/router with just a dsl modem and supply our own router and have some control to setup the port forwarding/firewallĪny other thoughts here? Anyone seen this one? So at this point I think we have three options:ġ.) Have the ISP setup the port forwarding "This could be like pulling teeth" Since this is an ISP supported all in one solution you don’t get access to this dsl/router (I may be wrong here we still need to call them)Ģ.
#ECHOLINK APP FOR APPLE MAC#
It also uses a firewall and I’m assuming that’s what’s blocking the iPhone, IPad and MAC connections. From what little documentation I can find on this ISP type dsl/router is it uses Dynamic Port forwarding so it listens to the tcp/ip sessions that are outbound and makes assumptions on that data to determine what to do with the inbound reqest in this case port 5200.
This -R is using Fairpoint as the ISP and the provided all in one (router,DSL and wireless) made by Clear Access model number SR300N.
#ECHOLINK APP FOR APPLE WINDOWS#
Since the Windows OS’s with echolink are working one would assume that this must be setup right? It turns out it’s not. The first thing I wanted to do was to varify how the port forwarding was setup. My Next step.Looking at how this -R network is configured:
So is this a packet header difference from MAC, Iphone, IPad to Windows? Its all on the same ports. I had a ham co-worker load Echolink on his Verizon Iphone "I have AT&T" and he also saw the same results.
This same ham loaded Echomac on his Mac and gets the same error but again can connect to others with no problem. He was able to connect to my Echolink node and any others that he tried. Just to make sure I'm not crazy I had a local ham try his IPad from his home and work wireless and he too got the same results. Great I thought for sure this must be the issue but after upgrading I am seeing no change. The next thing I noticed was the Echolink version running on this -R was old didn’t have the latest version. I contacted the repeater owned and verified that the security allowed for such a connection and it did.
#ECHOLINK APP FOR APPLE PC#
Now since I can connect via the same network using a Windows PC and using the same login I would automatically assume that all users types are allowed at this -R. The Windows PC works but the Iphone doesn’t at least for the –R in question. At this point we have no difference from my home PC to my Iphone I even setup with the same IP as my PC just to make sure. Changing my Iphone to go direct "no relay or proxy" and setting up my port forwarding to point at my Iphone IP address I still get the "Timed out" error. Going back to my Iphone and connecting to my home Wireless "not 3G" this is the same network my PC is running on and again I get the "Timed out" error and can never connect.
Here is the strange part using my Windows PC at home I was able to login to this -R with no problem. From my Iphone I can connect to my Echolink node and any others that I normally connect to. Recently I tried to connect to it using my Iphone and got a "Cannot connect to XXXX-R - Timed out" error. We have a local Echolink repeater that has been up and running for many years. I see this question was asked earlier this year.
0 kommentar(er)
