INTERACT FORUM
Networks and Remotes => Media Network => Topic started by: widman on May 13, 2012, 08:52:48 pm
-
Last week I couldn't connect to my media server from outside of my home network because Verizon changed my IP address. Can someone explain how the access key works and if if should be monitoring changes to the WAN IP?
Thanks,
pete
-
There is a web page you can go to and get your information from the database, the IP is updated on the DB regularly.
I will see if I can find it.
-
Follow the below link enter your access key and the select you respective location and it will auto-connect you to the WebGizmo page.
http://jriver.com/webgizmo.html
-
I have the access key set up and it usually works. My problem is that Verizon changed my WAN IP, so the key was pointing to the wrong address. I had accessed the Media Server computer from inside my home network in the evening and everything was working correctly. When I tried to access the Media Server computer from outside of my network the next morning, I could not connect.
I'm trying to understand if the access key gets updated in J River's database when the external IP changes and how often the program looks for changes to the IP address.
Pete
-
You must have overlooked where I said the IP is updated on a regular basis, the update frequency was discussed recently and if memory serves me correctly the frequency is every few hours.
Edit: the update is hourly according to what I found from a quick search.
Quoted from the 17.0.125 build post 1. Fixed: Library server access key would stop hourly renewals if there was a temporary internet disconnection.
-
I have now a "no-ip" domain for free. Once configured, It will take care of the router upgrades automatically.
The link :
http://www.no-ip.com/services/managed_dns/free_dynamic_dns.html
-
You must have overlooked where I said the IP is updated on a regular basis, the update frequency was discussed recently and if memory serves me correctly the frequency is every few hours.
Edit: the update is hourly according to what I found from a quick search.
Quoted from the 17.0.125 build post
Yes, I missed that. Thanks for the info. I guess the IP must have been changed while the Media Server computer was sleeping.
Pete