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.
Hey Mark,
Thanks for your reply. I was just getting ready to reply when David came up with a direction of sorts for me to take. Both the IP address for the camera and the Davis console end in .1.4 or .1.1 respectfully. He mentioned that the range for IP in hughes is .42.xxx
So now I'm looking to see if I have to change them in the camera/Davis or just find a work around thru the Hughesnet modem, possibly using the Mac address.
Any thoughts?
Brad
He did bring up a good point that I hadn't thought of.
I would change them at the devices just to be sure. I thought the MAC address thing is really for reserving pseudo-static addressing within DHCP (automatic), but only for those connected by wifi - not ethernet.
I suggest beer (or another alcoholic drink) every two hours, or as needed. 🙂
Seriously, I'm sorry you're going through this. -Larry
This may be a stupid question, but are the static IPs in the same address range? My HT2000 has local addresses in the 192.168.42.xxx range, but as an example, say I had a device with the static IP address of 192.168.0.101, the modem will not see it. Maybe a sniffer program would see it, but for the device to be seen by the modem, it would have to be set to 192.168.42.101. Could that be the issue? I assume you altered the IP addresses when you switched from DSL to Hughes, but it may be worth checking.
Dave
Hey David,
Was just getting ready to reply to Mark when you posted, and I was going to ask him about that.
Do I have to go into the camera and davis unit to physically change the IP, or can I use the MacAddress and give it a new IP addy in HughesNet configuration. Seems I saw some sort of an option to use the mac and add a new IP in that range
Thanks,
Brad
You would have to configure it on the camera itself, I think. If you set the camera to dynamic addressing and let the HughesNet modem set the preferred address by MAC, that would work, but probably not as reliably as a static IP. You may need PC software or an Android app to configure the camera itself, whether to change the static IP address or set it to dynamic addressing. I am not familiar with that brand, that is usually how it is done.
