Posted: Wed Nov 08, 2006 0:57 Post subject: Problem updating DDNS for NO-IP provider (V23 SP2)
Greetings,
I keep getting the following error with my wrt54g v4 router running v23 sp2 (09/15/06) mini :
W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 32)
W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 39)
W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 145)
W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 148)
W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 377)
It worked fine when I first configured the DDNS settings, but a few day later, I get these error messages. Could someone provide a workaround or a way to fix this problem. Thanks.
Thu Jan 1 00:01:54 1970: INADYN: Started 'INADYN Advanced version 0.1' - dynamic DNS updater.
Thu Jan 1 00:01:54 1970: INADYN: IP read from cache file is 'xx.xx.xx.xx'. No update required.
Wed Jan 17 11:59:17 2007: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Wed Jan 17 11:59:17 2007: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 0)
Wed Jan 17 12:08:30 2007: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Wed Jan 17 12:08:30 2007: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 1)
Wed Jan 17 12:17:43 2007: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Wed Jan 17 12:17:43 2007: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 2)
etc..etc...like this forever...
Thu Jan 18 11:43:30 2007: INADYN:IP: Error 0x83 in recv()
Thu Jan 18 11:43:30 2007: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jan 18 11:43:30 2007: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 112)
Thu Jan 18 13:03:13 2007: INADYN:IP: Error 0x83 in recv()
Thu Jan 18 13:03:13 2007: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jan 18 13:03:13 2007: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 125)
Thu Jan 18 13:15:36 2007: INADYN:IP: Error 0x83 in recv()
Thu Jan 18 13:15:36 2007: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jan 18 13:15:36 2007: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 127)
Thu Jan 18 13:21:56 2007: INADYN:IP: Error 0x83 in recv()
Thu Jan 18 13:21:56 2007: W: DYNDNS: Error 'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Thu Jan 18 13:21:56 2007: W:'RC_IP_RECV_ERROR' (0x15) updating the IPs. (it 128)
Noticed this as well. It worked fine last night but this morning the errors have appeared. Hopefully it's a no-ip error that will resolve. I'll wait and see for now.
Odd, I just started getting these errors on dyndns.org - totally breaking the service for me since no updates are taking place.
This is particulary annoying for me since I just dished out the money for a custom domain at dyndns.org yesterday since I was planning to run a private web/ftpserver for personal use.
theres a problem if you switch to repeater mode then back to AP it brakes connection between some cable modems that can cause dns issues, I use the linksys cable modem and if i switch to repeater for testing ill have that issue and ill have to use the reset button on the modem (i guess leaveing it completly unpluged for a while would do the samething)
I haven't got the nerves and time to track this issue down at the moment, but starting out with a completely fresh dd-wrt configuration (did a reset) fixed the problems for me. Not sure which setting caused it.
The errors reappeared after gradually setting my configuration back to what they were before the reset, however, I think I've figured it out now.
It works for me, maybe it works for you guys too.
The Administration -> Services -> DCHP Server -> LAN Domain field has to be blank, otherwise inadyn will be unable to update the IP and prints those odd error messages.
Also, set the "Used Domain" dropdown box to WAN, not LAN & WAN.
The errors reappeared after gradually setting my configuration back to what they were before the reset, however, I think I've figured it out now.
It works for me, maybe it works for you guys too.
The Administration -> Services -> DCHP Server -> LAN Domain field has to be blank, otherwise inadyn will be unable to update the IP and prints those odd error messages.
Also, set the "Used Domain" dropdown box to WAN, not LAN & WAN.
HTH.
I already had those settings and I've been getting this error for a while now apparently (got the inactivity notification in the mail from No-IP today).
I haven't changed ANYTHING for quite some time now. This appeared out of nowhere. It HAS to på No-IP's fault, right?
I started getting the same thing two days ago. That day I switched from dyndns to zoneedit so assume it's related to that. I'm hoping that my ip address will be updated properly with zoneedit.
Fri Apr 27 18:08:25 2007: W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Fri Apr 27 18:08:25 2007: W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 452)