Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[wingerr]

I'm experiencing a problem with the DDNS tool on my DIR-625 that only recently cropped up.  It becomes disconnected by itself after some time for some reason, with the status sometimes showing the Enable checkbox cleared, and other instances it's checked, but status says disconnect. 
When I try to reset it by saving settings, it shows connecting, but then back to Disconnected.

Only after I reboot the router will it connect and stay connected for a while, but then I find it disconnected some time later.   I checked the Status/Logs for a cause, but didn't see any mention of it, except possibly some packet blocking.  Would that be a cause for the DDNS updates to be disconnected?

I've been using the D-Link dlinkddns.com server with the default timeout of 576  hours.

Is it a clue that the router being rebooted (with no changes to any settings), allows the server to get connected again?

This only started happening recently, it's been working for months prior without any issues, and nothing has been changed.  I thought it might be the D-Link server itself, but since it seems to require a reboot of the router to enable it to connect again, it seems like there's something going on in the router itself.

Any pointers on what to check for?

[chicharon]

I am having the exact same problem on a DIR-655.  Were you ever able to correct this?

[wingerr]

It happened at first only on the two DIR-625's I had, but I never had any problems with my DIR-655-
until today.  The hostname I had on dyndns was out of date and wasn't updated, so I couldn't access my IP remotely.  When I got home, it was the same situation I had with the DIR-625's.

I tried using a new hostname from dlinkddns.com as well, but each time I updated the settings, the DIR-655 would say Connecting... for a few seconds, then show Disconnected.  Nothing showed up in the logs as the help file claimed would be done in case of problems.

I tried soft rebooting several times from the "Reboot the Device" from the Tools/System menu screen, but it didn't change anything even though the new IP was assigned each time.
Ended up unplugging the power from the router, and only after doing that would the DDNS finally connect up.

We'll see if it holds up- there's apparently some bug in the way D-Link implemented the DDNS update client in their router that leads to some instability that doesn't clear up without restarting the thing.

The DIR-625 that I had problems with originally hasn't dropped out for a long time now as far as the DDNS.  It still has sporadic wireless dropouts where I need to cycle power on it before the wireless connects up, though it's infrequent enough that it's tolerable.  The DIR-655 has been more reliable in that regard, except now it's started up with the DDNS problem. 

[smlunatick]

This just happened to me on my DIR-628 router.  I am not sure if this is a firmware problem or somehow someone else was changing my options.

Change your web config access passwords.

[wingerr]

I was logged on while trying to get it to reconnect, so it couldn't have been someone else changing the options.  I power cycled the router and it connected again, and so far it's remaining connected.
Something must be getting scrambled, and it's not any user configuration I could find.

I haven't tried forcing a change of the IP to see if it picks it up properly, though. Maybe I'll try and verify it later, though it's at least showing a Connected status in the DDNS status.

[smlunatick]

I notcied also that on my DIR-628 the DDNS entry was working correctly after I activated it again.  12 hours later (next morning) it was off again.  Not sure if the router option was being reset by the rouer, my ISP or someone else.  This week-end, I flashed my firmware (to 1.23NA) and replaced my router's access password. 

All is working as it should and only time will tell.

[smlunatick]

A further update.  DDNS feature appears to be broken now at the DDNS "service" now.  DlinkDDNS is a "special" service provided by DynDNS.org.  I tried to set up a DlinkDDNS account but it refused because I have a DynDNS.org account (this is how I found the "true" DDNS service company.) The DDNS client in my DIR-628 does not appear to update the entries at the DDNS "service."   DynDNS.org is forcing their own Windows update client software.

[wingerr]

Seems to be working okay with the dlinkddns.com DDNS server.  I did have a recent recurrence of the thing showing Disconnected each time I saved the settings, but after a reboot it came back up and remained connected.  Maybe it was because it was being changed too frequently as I was trying different configurations for port forwarding.