Posted: Sun May 27, 2007 22:48 Post subject: Possible solution for W: DYNDNS: Error 'RC_IP_CONNECT_FAILED
Hello!
Just saw a series of topics with this error: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server, because I had the same issue on a Motorola WR850G loaded with a DD-WRT v23 SP2 (09/15/05) std.
I have a Dyndns account which I got running for some time and then allways got this error.
My solution was to update the router time and date using a NTP server: Administration-Management-NTP client.
Posted: Mon May 28, 2007 19:16 Post subject: Re: Possible solution for W: DYNDNS: Error 'RC_IP_CONNECT_FA
lampadinha wrote:
Hello!
Just saw a series of topics with this error: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server, because I had the same issue on a Motorola WR850G loaded with a DD-WRT v23 SP2 (09/15/05) std.
I have a Dyndns account which I got running for some time and then allways got this error.
My solution was to update the router time and date using a NTP server: Administration-Management-NTP client.
Hope this hint help you all.
Hey, it seems to be working...! Thanks!
I'd never heard of NTP before, but I guess it's the same thing the Windows clock uses. Sort of.
Anyway, I used pool.ntp.org and the time was sure changed. Before there was like a 2 min difference from the system time in my computer.
And then the DDNS worked like nothing had been wrong all of a sudden.
Posted: Fri Jun 29, 2007 4:00 Post subject: Possible port 80 blocking from ISP
Hi,
NB. Edited from previous post. Although it showed that it was updated, the update actually didn't work. These settings below worked instead.
I managed to solve a similar problem by re-directing the checkip process to the same url with a different port. inadyn defaults to using port 80 to check the ip. This fails when I use the default DYNDNS settings because it checks my IP using checkip.dyndns.org. Use the custom method to change this settings.
Posted: Wed Jul 18, 2007 15:51 Post subject: Re: Possible solution for W: DYNDNS: Error 'RC_IP_CONNECT_FA
lampadinha wrote:
Hello!
Just saw a series of topics with this error: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server, because I had the same issue on a Motorola WR850G loaded with a DD-WRT v23 SP2 (09/15/05) std.
I have a Dyndns account which I got running for some time and then allways got this error.
My solution was to update the router time and date using a NTP server: Administration-Management-NTP client.
Hope this hint help you all.
That worked for me as well, I used the 'time.nist.gov' time server.
I have the same problem with the dyndns. Now I tried to set the NTP-Server on the Administration -> Management Screen.
I set it to "pool.ntp.org" as well and it is enabled of course but the problem with the dns still exists. Then I logged on to the router via telnet and typed the unix command "date"
it says January 1 1970. When I try to set the time manually ("date -s") it will not change. Is this effect because the ntp is set?
I use Firmware: DD-WRT v23 SP2 (09/15/06) std on a linksys wrt54g. it is configurated as a accesspoint only behind a router. do I need to forward any port to the wrt54g?
* - I have replace password, usernames etc. in the above
Despite the log and conf appearing OK - my browser fails to load and refers to refused connection and traceroute on the dyndns web address appears to stop at my cable modem supplier
DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Getting the same error as others. Fixes suggested so far in this thread were already set.
Seems to work every few days & was successful just yesterday morning, but retries every 5 hours with this error. I have forced update interval set to 10 days. Perhaps there is a way to set update interval to once/day instead of every 5 hours? _________________ DD-WRT v24-sp2 (04/07/12) big - 18946M NEWD-2 K2.6 Eko
Linksys E1550
DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Getting the same error as others. Fixes suggested so far in this thread were already set.
Seems to work every few days & was successful just yesterday morning, but retries every 5 hours with this error. I have forced update interval set to 10 days. Perhaps there is a way to set update interval to once/day instead of every 5 hours?
How many days does it work for you ?
Which NTP server did you enter ?
I´m testing this now with a NTP server that is near to me.
My theory is the folowing:
I´ve read this WIKI page:
Don`t know if this page is actual.
What happens when the time can not be synchronized with the NTP server.
Is inadyn working then correctly ?
What NTP server uses DD-WRT when no NTP server is set ? (in the WIKI it`s "ntp2.usno.navy.mil" )
DD-WRT synchronizes the time every hour.
What happens when it can not reach the NTP server ?
Perhabs this is the real issue ?
Can i see somewhere that the time synchronize was successful ? _________________ Netgear WNR834B v2 - Eko build v24-sp2 15943M mini NEWD K2.4 (running MINIUPNPD)
Tested with BS 15943 mini build with my 32/1 line over wireless:
NTP: time-a.nist.gov
Don't know how often it updates, but the displayed time is to-the-second in synch with my PC using the same NTP _________________ DD-WRT v24-sp2 (04/07/12) big - 18946M NEWD-2 K2.6 Eko
Linksys E1550
When this wiki is actual, DD-WRT updates the time 24 times a day. What happens when one is not successful ?
Is this causing inadyn to output these errors ?
Time will give me the answer.
I`m using this one: 129.69.1.153 .
It`s giving me good pings back (20ms).
Actually i´m 3 hours error free...
Will give response when getting errors _________________ Netgear WNR834B v2 - Eko build v24-sp2 15943M mini NEWD K2.4 (running MINIUPNPD)
Tested with BS 15943 mini build with my 32/1 line over wireless:
Posted: Thu Nov 26, 2009 18:30 Post subject: INADYN problem with NO-IP.COM
Hi,
I use inadyn on a linux satellite receiver.
All is configured.
But I get this error message all the time :
INADYN: Started 'INADYN version 1.96' - dynamic DNS updater.
INADYN:IP: Error 0x83 in recv()
W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 0)
INADYN:IP: Error 0x83 in recv()
W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 1)
the times of the sat-box and the router are correct and up to date.
anyone has an idea why that error keeps on showing up ?
I have been having this problem over a year now, but never got into it. . .until now that i have setup the same router for my mom, hah.
Anyway, i'm going to look back into this and definately find a solution. Here's what i think the source of the problem is:
** The router cannot resolve hostnames to IPs. So therefore, only IP works **
Maybe not everyone has this particular issue, but i definately do. If you want to check, just SSH or Telnet into your router, and try to ping something like googl.com or yahoo.com, and you will see it does not resolve. But if you ping by IP, it does ping successfuly.
So why would this be an issue for DDNS? One of the errors i got a year ago, was that the router could not resolve "checkip.blabla.com" (i forgot the hostname). I belive the INADYN service built into DD-WRT is trying to resolve some hostsnames, but it cannot, and therefore spits out errors.
Also, if you have configuration in your DDNS settings such as:
DYNDNS Server: updates.dnsomatic.com
it will fail to to resolve that hostname, and therefore, spit out errors.
So that's my theory. I think once the router can resolve hostnames, the service will work just fine. I'll post more if i can get some more info. _________________ CCIE & 10+ Year DD-WRT User
“Power lacks moral or principles. It only has interests.”
-Horacio Castellanos Moya
However, please note this was a TEMPORARY solution. I never did fix the real problem (router not being able to resolve hostnames).
**EDIT** I updated the IPs noted above, as it's been a year since i checked. I updated my startup config, and the problem has gone away!! Again, it's only a temporary fix until the router can resolve hostnames on it's own. _________________ CCIE & 10+ Year DD-WRT User
“Power lacks moral or principles. It only has interests.”
-Horacio Castellanos Moya
Posted: Mon Feb 01, 2010 6:56 Post subject: DNS issues
EEK, if your router cannot resolve hostnames, then there's a problem with the router's DNS configuration. Try entering the OpenDNS servers (208.67.220.220 and 208.67.222.222) in the "DNS 1" and "DNS 2" fields on the main router setup page. That should enable your router to make successful DNS queries, and you can remove the hosts file hack.