kevinz wrote:
Hi cabsandy,
Assume you use and setup NeoRouter domain name properly to your NR server. ( go to NR Configuration Explorer or NR web console to verify if your NR server has a NR domain name associated, if not, set it up)
NR server will call our back end server to sync up its public IP, associated with the NR domain name and the listening port number. It calls every time NR server starts and once an hour when a timer is timeout. So please make sure your computer (on that NR server is running) has access to our Dashboard website.
To verify this, you can manually restart NR server service; it may take couple of minutes for it to update its public IP address and you can see it in the Dashboard. (You may setup a wrong IP in Dashboard before testing.)
Once NR server updates the public IP, NR client may take a sometime to detect the changes and automatically reconnect to the server at new IP address.
If your server does not update the IP address after NR server service restarts, there would be something wrong and need to investigate it.
Thanks,
KevinZ - NeoRouter team
Kevin-works exactly as you explained so thank you for that.I suppose that 1 hour timeframe is set, you dont/wont allow servers to update quicker?
One last question-in the free version, can you segment devices into different networks (so multiple star networks-one controlling device that can talk to all, but none of the the other devices can speak to each other)?
So like having multiple VLAN's-or is that in the Pro version