ART not recognizing Internet connection

[bizzrunni...@gmail.com]

Today while timing a race, I was able to publish results to 
RSU and to Arrow Live. I'm using 1.6.7.2. I forgot to do a final publish before shutting down. I  got home and fired up the laptop to complete the publish . I hit the Publish Results link to RSU but got a notice which said "No Internet Connection." My internet connection on my laptop is working fine and I'm even using the same wireless hotspot I used at the race. I tested my RSU connection in the External Accounts tab on Settings and I got "Login Successful" and Authentication Successful. Arrow Live was auto syncing results the whole time so I have those completed results published. My next step was to create a new race and to use the Interfaces tab to sync to a race already on RSU. Still getting the " check your internet connection" message.  I get the same message when trying to submit the race to Arrow. Anyone have suggestions? Is this a bug?

-Linda

[Nick Mullen]

I ran into something similar yesterday. I was connected to my hotspot and could publish results and send finishing SMS messages just fine but would get the "No Internet Connection" when I attempted to sync participants from RSU. I would hit sync 3-4 times in a row and eventually, usually on the third attempt, it would work and I'd see the status bar appear and new participants would be added to the athlete list.

[Brian Agee]

I apologize I have not responded to this thread sooner. A few days ago I looked into this and doubled the "timeout" period from 5 seconds to 10 seconds. 5 seconds is supposed to be plenty of time for a PC to try and ping Google.com, however I went ahead and doubled it to see if that helps.

Prior to version 6.7, I was using a different (older and not recommended) way to check for internet access. That older way had no ability to set a 'time out' limit, but it would ultimately determine if internet access was truly available or not (even if it took a VERY long time). The problem with the old way is that some customers reporting seeing the "checking for license key..." message for a very long time when they tried to load the software on race morning. So I implemented the newer "recommended" way with version 6.7 and that the program wouldn't wait indefinitely to see if internet access was available or not.

In summary, with the next update, in addition to doubling the time out period I made it so that when the program first loads it only does the "new" method with a maximum "time out" period of 10 seconds. For all other processes (like syncing participants, pushing up results, etc.) it will do both the new AND the old way to check for internet access exists. So in environments where there is very slow or poor signal you might see the program taking a very long time to perform an action, but ultimately the software should accurately determine if internet access is available with this next update that I plan to push out in the morning.