- Contact Us
I was using one of the older names (.homeip.net) on a Linksys router for more then a year... turned off the router to do some construction changes, missed the email to renew the account to keep the old name structure last year when things were changed. Reset my dyndns account with a new xxx.dyndns.org hostname and my router will no longer successfuly connect and update with all the proper login info. The router setup I have didn't change in any way. Same modem, same service, same router, same dyndns.org selection for the hardware update client type, same username and same password. Only difference is the new hostname i selected of dyndns.org and now no go. Frustrating.... Did something change on the dyndns side when the hostname selectons were changed that would affect the built in hardware update clients?
Cox cable internet service Wrt54G V8 router with 8.00.2 firmware.
(sorry I accidently posted this as an answer on another post - my bad).
Answer by Cry Havok · Mar 05, 2011 at 09:51 AM
There's been nothing I'm aware of that should have changed updates. Certainly my own hardware client works just fine and given that the same API is used by all clients a change that impacted one would impact all.
What is the error message you're seeing in the client?
Answer by ken85622 · Mar 07, 2011 at 08:23 PM
(can't seem to add comments now so I'm leaving an answer)
I get the "Name resolver fail, DDNS update fail!" message. Seems to imply the dyndns.org ip can't be found. Seperate ping through router diags fails. I can get the ip address to resolve through cmd prompt but no ping response. Gave up and switched to TZO which is working fine. I don't know why this has become a sudden problem. Software update client works fine on pc just the hardware client not working.
Oddly I had a similar problem in a different state, different router, and different service provider. That problem appears to have recently disappeared. On that router the probelm appeared around the same time dyndns made changes. My router stoped updating. I left it configured and just gave up on it and low and behold I checked it the other day and it connected. Don't know whats up but I basicaly give up on dyndns.
Thanks for the response thoe!
Answer by fluffywuffy · Dec 28, 2011 at 05:17 AM
Exact same problem to the T (well, not using Cox). Same WRT54g hw/fw version, functioning correctly before my account expired, but no longer functional after I have re-created it. The router cannot resolve members.dyndns.org or dyndns.com from the router's trace route utility yet using the same dns servers on my machine (behind the router) can correctly resolve both addresses.... Did you ever work this out or are your still using TZO? Linksys has released 5 more firmware updates for this model. I don't have my ISP password handy currently, so I can't try it at this moment.
update to 4.1.5 4 Answers
Moved from Fritzbox to speedport 3 Answers
update client can't modify the constant 4 Answers
"Unknown message!" for DDNS status 1 Answer