I see this question was asked earlier this year. But here we go again. This will be a little bit deeper. We have a local Echolink repeater that has been up and running for many years. Recently I tried to connect to it using my Iphone and got a "Cannot connect to XXXX-R - Timed out" error. From my Iphone I can connect to my Echolink node and any others that I normally connect to. Here is the strange part using my Windows PC at home I was able to login to this -R with no problem. 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. 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. 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. The Windows PC works but the Iphone doesn’t at least for the –R in question. 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. I contacted the repeater owned and verified that the security allowed for such a connection and it did. The next thing I noticed was the Echolink version running on this -R was old didn’t have the latest version. So we got that upgraded to 2.0.908. Great I thought for sure this must be the issue but after upgrading I am seeing no change. I still get the "Timed out" error. 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. He also gets the "Timed out" error. He was able to connect to my Echolink node and any others that he tried. This same ham loaded Echomac on his Mac and gets the same error but again can connect to others with no problem. I had a ham co-worker load Echolink on his Verizon Iphone "I have AT&T" and he also saw the same results. So is this a packet header difference from MAC, Iphone, IPad to Windows? Its all on the same ports.. Very strange… My Next step...Looking at how this -R network is configured: The first thing I wanted to do was to varify how the port forwarding was setup. Since the Windows OS’s with echolink are working one would assume that this must be setup right? It turns out it’s not. 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. 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. It also uses a firewall and I’m assuming that’s what’s blocking the iPhone, IPad and MAC connections. So at this point I think we have three options: 1.) 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) 2 .) 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 3.) Get a new ISP Any other thoughts here? Anyone seen this one?