Thx maratsade, and I hope so also. Kind of frustrating.
Brad
All of this is beyond my skill set; the only thing that jumped at me was the static IP addresses. I don't know if that would make a difference at all, though. Here's hoping one of the mods will know, or maybe MarkJFine or GabeU . Also, are there any support communities for the hardware and software you use? If so, someone there might be running things with HughesNet and may have an answer for you.
Yeah, both pieces of software have forums, but no one seems to running with the HT2010, and very few on HughesNet. Seems like the static IP addresses for each of my units should make it easy to get hooked up. *shrug*
Plan on trying again later this afternoon until the teeth grinding and hair pulling sends me into Beer30
Brad
I understand the static IP part, which you mean that you have set, defined IPs for each device within your local LAN.
I will also assume that your system does not require any kind of port mapping or port triggering for things coming from outside the HughesNet network. That would be problematic because although you have what appears to be a public IP at the modem it is not accessible from outside HughesNet. What this means is: If the software uses arbitrating/intermediary clouds to interface between the computer and the collection devices instead of talking directly to them within the LAN, the system might not operate properly - anything external to HughesNet can't reach in and see the computer, nor the devices to do anything with them.
I realize that may have worked under a terrestrial DSL, however HughesNet uses double-NATing/IP translation between the modem, beam and groundstation, that may cause such a thing to be inoperable.
