|
Dec 16th, 2012 at 1:25pm
Posted by admin, as requested in an email:
But my question is: I have clients with remotely monitored PV and/or thermal RE systems that I build. Sometimes, but more and more often, I sell them a sat2way (tooway in France) install, because many of them are either off-grid or far away from towns, and have poor ADSL speed and bad reliability due to the wires ripping off the poles when trees fall under snow load.
Now what does that mean for the remote monitoring, that uses dynamic DNS redirection (via no-ip, for example)? It stops. It seems that my LAN/Wifi router behind the tooway modem, that replaces the usual DSL box, perfectly signs in to the no-ip server, and registers the tooway IP address, but when I call it from my remote monitoring console, I don't get a reply. Tooway tech support says I need to sell the customer a Pro account. There is nothing like a 8Gb account that has a comparable price to the standard 8Gb account, and I get a fixed (public) IP adddress that I don't actually need.
Yesterday, the boss of sat2way France told me by email that I *could* use dyndns, but today, sent me a order form for the various Pro accounts, that I can't put on my client's bill "just" for monitoring and remote control, which is actually a feature that helps me avoid unnecessary travel to the site.
Technically speaking, while tooway got my client a better Internet speed, it is a regression for my part of the job.
Will I need to "bury" an old laptop on the site that runs LogMeIn now? Is there any better solution?
Best regards
Admin ref: Sun, 16 Dec 2012 11:49
|