Remote Rig
RRC 1258 Support in English => General discussion forum => Topic started by: dj0qn on 2010-11-05, 18:19:26
-
Although I find 2.26 to be stable and a good improvement, I noticed that
the DynDNS update no longer works, and returns an error message. I
use the RemoteRig as a backup to my router's DynDNS with a different
address, so it is not mission critical, which is why I just now noticed the
problem.
In checking my log on DynDNS.com, it indicates my last update took place
the evening of Oct. 28th, which is when I installed 2.26.
73,
Mitch DJ0QN / K7DX
-
It's no problem with the DynDns client. I have tested it my self, at my summer house RRC.
73 de mike
-
Which service are you using? Maybe the problem is
specific to dyndns.com? I tried reentering my information,
even though it was still there, with no change.
73,
Mitch DJ0QN / K7DX
-
Is there more than one ?
I log in at http://www.dyndns.com/index3.html
i have an free account since 5-6 years I think with five adresses.
I changed the dyndns name at the summer house to a name that hadn't been updated for long time.
then after reset I checked at dyndns and after 10 seconds it was updated.
At the statuspage in the RRC dyndns status was changed to OK also
73 de mike
-
Yes, there are several, but dyndns.com is the largest one.
I have a paid account and have several host names. At my
remote QTH, I have different ones on four devices, since my
router sometimes does not update. This allows me to have
fallback host names in case I can't reach my station.
Anyway, I just deactivated it in the RRC-1258 and then
reactivated it again, now it finally updated. If anyone was
using dyndns before 2.26, they need to apparently do this
in order to make it work again.
Thanks & 73,
Mitch DJ0QN / K7DX
-
Although I find 2.26 to be stable and a good improvement, I noticed that
the DynDNS update no longer works, and returns an error message.
Which error message did you get? And where did you see it?
-
On the "Status" page, next to last is "DYNDNS status".
It said error until I deactivated and reactivated it, now
it says "OK" as it should (and I double checked the DynDNS
web site to make sure it updated).
73,
Mitch DJ0QN / K7DX
-
OK, I see. But I don't see how deactivating and reactivating it could have helped. I would have better understood if a power reset had helped. Also it seems strange if 2.26 is like that in general, demanding deactivation and reactivation for the DynDNS to work.
-
Had the same issue, but that was happening on an other device also. So it seems that it was only dyndns that had a problem those days because of some internal changes at dyndns.
I only powerd off and on the devices.
73 de LB9GE
-
Then I have a question: when DynDNS returns an error, does it continue to
try at the defined intervals, or does it give-up and stop at that point?
If it gives-up, then this would mean the problem was coincidentally with
DynDNS at the time I installed 2.26 and simply changing the password, etc.
has no effect. You must disable/re-enable or recycle the power. This would
also explain why only I had that problem.
Since 2.26 solved the stability issue with the web page accessibility, I had
no reason to recycle the power since installing it.
73,
Mitch DJ0QN / K7DX
-
Then I have a question: when DynDNS returns an error, does it continue to
try at the defined intervals, or does it give-up and stop at that point?
......
Since 2.26 solved the stability issue with the web page accessibility, I had
no reason to recycle the power since installing it.
It should continue retrying at the defined intervals. At least that is the intention ;)
You mean that 2.26 has fixed the web page accessibility?! We haven't actually found what has caused some of you having such problems, though one minor thing was spotted during the search for it, and fixed in 2.26. If that "fixed" that problem then it really is great news! From which version did you upgrade?
-
I would check to see if it does indeed continue retrying, since that
is the only plausible explanation of why I had this problem, but no
one else did.
Yes, I was one of the guys that reported the web page accessibility
problem with 2.25 (and only with 2.25!). 2.26 has definitely
solved this, it hasn't died once since I installed 2.26.
73,
Mitch DJ0QN / K7DX
-
I would check to see if it does indeed continue retrying, since that
is the only plausible explanation of why I had this problem, but no
one else did.
We will give it a check, but I would say based on experience that there are often more reasons for a failure than one can imaging ;)
Yes, I was one of the guys that reported the web page accessibility
problem with 2.25 (and only with 2.25!). 2.26 has definitely
solved this, it hasn't died once since I installed 2.26.
That is even more strange! Can't think of any reason 2.25 would have been different than all other versions, including the older ones. (But the previous mentioned more reasons for a failure than imaginable might apply here too, hehe!)
-
I also have problems with DynDNS and ver. 2.26.
Indicates DynDNS errors in the status panel.
Uses NET1 as ISP (CDMA 450)
//Chris SM7SKI
-
We haven't changed anything concerning Dyndns for long time. We got one mail from a guy who had logged the data traffic against dyndns and in that specific case we saw that some part of the message from Dyndns was missing, either not sent or cut away when sent over the Internet. So if some one who have probelm and can handle WireShark can send us some info we will check it up. We are not able to find any problem from here and with the DynDns accounts we have.
It can also be useful if we can "borrow" a problematic dyndns account so we can test with it.
73 de mike
-
To All
Its not a problem of Microbit or any other Hardware that updates Dyndns.
The problem is caused by Dyndns itself,
a few weeks ago (around the time 2.26 was released),
I had also problems with Dyndns myself, the hardware/firmware that updated my dyndns
has not been changed since the last 5 years and it never failed to do so,
now it is not working anymore and I even got mail from DYNDNS that it was blocked....
My Linksys router on another DYNDNS name is still ok but nomatter what I try with the other one
is not working anymore and there is nothing wrong with the hardware since I can use it with other lookalike
software. The only way to keep updating that specific dyndns is to use theire own free DynDns updater.
Guy ON4AOI
-
Hi Guy,
I also am now sure that the problem was caused by DynDNS being
down at the time of my update. The problem appears to be error
recovery in the box, since it didn't update again once DynDNS
started working again
I have several addresses with DynDNS and the service works
just fine. Seems that they had a hiccup.
73,
Mitch DJ0QN / K7DX
-
Hello,
I am using the Telstra 3G network to access my remote device. The access device is a 3G wireless router which is able to update my remote IP address to DynDNS if the remote wireless device is reset. (the remote IP address is public but not static).
If I ping my DynDNS host name the remote IP address is resolved. Pinging vk3oexxxx.xxxxx.net [132.209.3.131] with 32 bytes of data.
If I use this IP address [132.209.3.131] as the SIP contact in the radio settings on the control device then I can easily connect to the remote device.
If I use the DynDNS host name instead (vk3oexxxx.xxxxx.net ) for the SIP contact then the control device is not able to resolve the remote IP address from DynDNS and I get a SIP Error and 5 sets of increasing tones.
Software is 2.26. I have not tried to use the remote rig device to update DynDNS.
This seems to be at the root of the problem.
73,
Andrew.
-
Also using FW2.26 with dyndns, I have had no problems using Bigpond Wireless NextG as well using a embedded microcontroller web server, have had no problems resolving both via dyndns url. router has port forward to internal private IP for Remoterig Box and embedded server using port 8000 and 8090.
Regards
Frank
-
Hello,
I am using the Telstra 3G network to access my remote device. The access device is a 3G wireless router which is able to update my remote IP address to DynDNS if the remote wireless device is reset. (the remote IP address is public but not static).
If I ping my DynDNS host name the remote IP address is resolved. Pinging vk3oexxxx.xxxxx.net [132.209.3.131] with 32 bytes of data.
If I use this IP address [132.209.3.131] as the SIP contact in the radio settings on the control device then I can easily connect to the remote device.
If I use the DynDNS host name instead (vk3oexxxx.xxxxx.net ) for the SIP contact then the control device is not able to resolve the remote IP address from DynDNS and I get a SIP Error and 5 sets of increasing tones.
Software is 2.26. I have not tried to use the remote rig device to update DynDNS.
This seems to be at the root of the problem.
73,
Andrew.
Just to be 100% sure: You have entered a valid "Dns server" IP address in "IP Settings"? ;)
/Jan
-
Then I have a question: when DynDNS returns an error, does it continue to
try at the defined intervals, or does it give-up and stop at that point?
Just checked this and it continues reattempting updating at the defined intervals. We are considering extending the status information regarding both DynDNS and dns in order to make it easier to diagnose problems like this.
-
Hello Jan and Frank,
Yes,,, I was experimenting with all the settings and accidently left the dns server address out!!!
Putting the dns server address in the control IP Settings and the whole system works extremely well. Without the dns address the system keeps trying to connect just as you indicated Jan, Thanks.
Many thanks. :) :)
73
Andrew.