Print

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

[Alezis]

Hello,

I have tried to search for an answer on the forum but I cannot find the correct answer to my issue.

I'm having a problem where my dir655 updates the wrong ip adress to dyndns server. It always report 255.255.255.255.

The dyndns information is all entered correctly and says "connected" in the dyndns configuration.

So what is wrong with the adress update from the dir-655 to the dyndns server ?

Of course I cannot use my dyndns adress since it is always at the wrong adress.

My 655 is under f/w v2.0.

Any ideas ?

[thecreator]

Hello,

I have tried to search for an answer on the forum but I cannot find the correct answer to my issue.

I'm having a problem where my dir655 updates the wrong ip adress to dyndns server. It always report 255.255.255.255.

The dyndns information is all entered correctly and says "connected" in the dyndns configuration.

So what is wrong with the adress update from the dir-655 to the dyndns server ?

Of course I cannot use my dyndns adress since it is always at the wrong adress.

My 655 is under f/w v2.0.

Any ideas ?

Hi Alezis,

The latest firmware is 2.01NA. The manually reenter all information. Upgrade procedure has already been posted.

[Alezis]

urgh... worst experience ever updating this router...

I had to return the router as it does not want to update anymore. It always says that I have the wrong firmware for the router.

I ended up in a different page when I was going at 192.168.0.1. I only had a file navigation button to get the firmware and an update button but it always crash or it says that I have the wrong firmware.

I downloaded the firmware from dlink.ca which was 2.01na revB.

I have tried to put back the original firmware and it does not work anymore.

Can you point the link to the firmware upgrade procedure ?

I had a brand new router with absolutely no config in it so it was the right time to update the firmware as I had nothing to backup.

I put my computer into static adress at 192.168.0.100, 255.255.255.0 and 192.168.0.1 standards.

Still nothing to do.

Also there is no indication in the new 2.01 firmware release notes that talk about the dyndns not being updated to 255.255.255.255.

Can someone help me with this wrong dyndns adress update ?

[FurryNutz]

If you have to do a FW update, do the following:
1. Reset to Factory defaults using the back reset button or from with in the routers web page under Tools/System.
2. Upload the correct FW for your modem and HW version.
3. Reset to Factory defaults using the back reset button or from with in the routers web page under Tools/System again.
4. Connect and configure the router. Set static reserved IP addresses in the router and set devices to obtain and IP address automantically, not static.

If the DynDNS is not working, does using the ISP DNS addresses work?
Manually enter in the ISP DNS from the Status/Device Info/Wan section into the Setup/Internet/Manual section.

Enable DNS relay under Setup/network settings. Some use this option, some don't.

[thecreator]

urgh... worst experience ever updating this router...

I had to return the router as it does not want to update anymore. It always says that I have the wrong firmware for the router.

I ended up in a different page when I was going at 192.168.0.1. I only had a file navigation button to get the firmware and an update button but it always crash or it says that I have the wrong firmware.

I downloaded the firmware from dlink.ca which was 2.01na revB.

I have tried to put back the original firmware and it does not work anymore.

Can you point the link to the firmware upgrade procedure ?

I had a brand new router with absolutely no config in it so it was the right time to update the firmware as I had nothing to backup.

I put my computer into static adress at 192.168.0.100, 255.255.255.0 and 192.168.0.1 standards.

Still nothing to do.

Also there is no indication in the new 2.01 firmware release notes that talk about the dyndns not being updated to 255.255.255.255.

Can someone help me with this wrong dyndns adress update ?

Hi Alezis,

> Can you point the link to the firmware upgrade procedure ?

http://forums.dlink.com/index.php?topic=36970.msg118928#msg118928

> I put my computer into static adress at 192.168.0.100, 255.255.255.0 and 192.168.0.1 standards.

You don't place your computer into a Static Address, you do that on the Router, not the computer.

Where are you entering 255.255.255.0? I see no place to do that.

> Can someone help me with this wrong dyndns adress update ?

Why aren't you using https://www.dlinkddns.com/login ?

Did you unzip the Downloaded firmware?

[Alezis]

Thanks for the reply, see below

If you have to do a FW update, do the following:
1. Reset to Factory defaults using the back reset button or from with in the routers web page under Tools/System. Done with hard button
2. Upload the correct FW for your modem and HW version. It never worked. It says wrong version. Router is RevB with fw 2.00. Downloaded the latest firmware from dlink.ca dir655 page, still says wrong file.
3. Reset to Factory defaults using the back reset button or from with in the routers web page under Tools/System again. Resetting the router after the wrong fw message did not change anything. When I entered 192.168.0.1, I was ending up in a white page with only a navigation file input box and a send button. No more dlink standard page. I have tried to reset multiple time and remove power still nothing to do. That is why I had to return the unit.
4. Connect and configure the router. Set static reserved IP addresses in the router and set devices to obtain and IP address automantically, not static. As stated before, not possible to do anymore since I was stuck in the white page config.

If the DynDNS is not working, does using the ISP DNS addresses work? Could not tried this as I was never able to return in the dlink menu after the fail firmware update attemps.
Manually enter in the ISP DNS from the Status/Device Info/Wan section into the Setup/Internet/Manual section.

Enable DNS relay under Setup/network settings. Some use this option, some don't. I tried this with the new exchanged router and still the same issue with or without this option. I have not risk to update the firmware at this moment as I want to be sure of the right procedure. Dyndns still updates to 255.255.255.255.

Thanks for your help, really appreciate this.

[Alezis]

Thanks for your help, I will try to be as precise as I can to answer your questions.

See also my answer below in the quote box:

Hi Alezis,

> Can you point the link to the firmware upgrade procedure ?

http://forums.dlink.com/index.php?topic=36970.msg118928#msg118928

Thanks for the link. I did follow pretty much what is in there. I have reset the router when it got out of the brand new sealed box by holding the reset button.

> I put my computer into static adress at 192.168.0.100, 255.255.255.0 and 192.168.0.1 standards.

You don't place your computer into a Static Address, you do that on the Router, not the computer.

Where are you entering 255.255.255.0? I see no place to do that.

I had put a static adress in my computer so the computer gives the adress to the router. I must tell you that I have put the DHCP range from .101-.199 so making my pc "force" to take .100 adress. I did that because after applying some changes, sometime, my computer did not seem to reconnect anymore. I was ending up with a 169.xxx.xxx.xxx adress. That is why I did try the static ip on my computer. It seems to work better but when all this config would end, I would put back everything in dhcp. I did not use the reservation list but rather use the pc to take an adress outside the dhcp range.

You can enter the subnet mask 255.255.255.0 in setup, network setting and router settings. There you can change ip router adress (192.168.0.1) and subnet mask (255.255.255.0).

I though it had something to do with the router updating the wrong adress to the dyndns service.

> Can someone help me with this wrong dyndns adress update ?

Why aren't you using https://www.dlinkddns.com/login ?

Because I pay for the service because I have more than one account and they are all managed in the same account. Was easyer for me and I've been using dyndns for a really long time. Changing all adress of every one to a new dns server would be really complicated for me to do.

Did you unzip the Downloaded firmware?

Of course, I update the .bin file and not the .rar/.zip file.

Now today, I have replaced the dir655 v2.00 that craped by another one also v2.00 but I did not risk to update the firmware at this moment. I still had to remove this and put a temporary router instead because now all the windows PC cannot get on the network over wifi as when it has fishing asking for the key, another window open and ask for a user neme and password to join the network... I never saw that before... when it was wired, no problem besides dyndns...


I am using a dir655 with fw 1.21 for myself right now and I NEVER had ANY issue with this router. Never. It stays connected all the time, I never rebooted that router since 4 years now never pulled the plug and it worked flawlessly.

I use to make everybody buy a dir655 and configure it for them (even at work, I suggested that router for projects) but I started to have complaint since v1.32 where I got multiple complaint about the internet dropping. Those people have the same ISP than I have at this moment and are in home environment, not commercial.

I've got so much trouble updating the routers from 1.32 to 1.34 and even then, I still have the internet connection drops. And now, v2.00 seems better at not dropping the internet but I cannot update the dyndns and strange login page on the wifi.

It's the second dir655 v2.0 I install with dyndns and that is not working. One using PPPOE and the other one DHCP and both are doing the same thing.

I have replaced one of 655 by a 24$ Trendnet router while returning and exchange the router for a friend so he still have internet and guess what, it works like a charm... He want's to buy my trendnet "test" router instead... which I do not want to sell along my 655 with v1.21.

Anyway, I am really disapointed and friends (and their friends) are also really disapointed. It is complicated to replace and make work... way far complicated than my 4 year old 655...

I just said all that to "vent" a little because it is not what I expected from new versions and makes me work hard, cost time to get exchange and all that...

I don't understand why dlink release such fw if it does not work... which, by the way, in the release note is not talking about the dyndns issue...

Anyway, hope this helps in finding the issue because I truly beleive in dlink products... right ?

[thecreator]

Hi Alezis,

How are you connected to the Internet?

What is your DIR-655 Router plugged into?

Cable, DSL, Dialup, or FIOS?

I use dlinkddns.com free.

[Alezis]

Hi Alezis,

How are you connected to the Internet?

What is your DIR-655 Router plugged into?

Cable, DSL, Dialup, or FIOS?

I use dlinkddns.com free.

it happend on both cable and dsl exact same problem

[thecreator]

it happend on both cable and dsl exact same problem

Hi Alezis,

you logged into dyndns and what information do you enter there? The Internet IP Address or the IP Address assigned by the Router?

[Alezis]

Hi Alezis,

you logged into dyndns and what information do you enter there? The Internet IP Address or the IP Address assigned by the Router?

When I first created the dyndns account, it did use the correct address detected through my computer and it did work at that time.

I then setup the dyndns account information in the 655, the 655 then displayed "connected" but it sends the wrong address  255.255.255.255 when I return to the dyndns web site to verify the account information.

[Alezis]

Here is the result of the account being on cable modem using the dir655 v2.00.

You can even see that this one just updated a couple hours ago as I set a refresh every 168h even when the modem adress has not change.

And here is the result of the other account being on pppoe using the dir655 v2.00

Of couse, you can't access the adress since it is tied to 255.255.255.255. I can't access the routers from my home to help these guys either.

[thecreator]

Hi Alezis,

ftp://thecreator1965.dlinkddns.com/2011-04-02%20IP%20Address.JPG

If you look at the IP Address on the Image, you will see the IP Address that the Verizon ActionTek Router assigns to my D-Link Router. I am using Firmware 1.21 also in my signature.

If I expect a visitor to my FTP Server, I need to sign in manually to :
https://www.dlinkddns.com/login

and sign in and edit my Host and use the Browser IP Address.

You need to look at the IP Address that the D-Link Router is receiving. If your D-Link Router is not registered with your Cable Modem and it needs to be a straight Cable Modem, without a Router, in order for the D-Link Router to capture your True IP Address from the Cable Modem or DSL Modem without a built-in Router.

In either case, the D-link Router, must capture the true IP Address on that line to report it correctly to http://www.dyndns.com/

Check the line on your Router.

[Alezis]

Hi Alezis,

ftp://thecreator1965.dlinkddns.com/2011-04-02%20IP%20Address.JPG

If you look at the IP Address on the Image, you will see the IP Address that the Verizon ActionTek Router assigns to my D-Link Router. I am using Firmware 1.21 also in my signature.

If I expect a visitor to my FTP Server, I need to sign in manually to :
https://www.dlinkddns.com/login

and sign in and edit my Host and use the Browser IP Address.

You need to look at the IP Address that the D-Link Router is receiving. If your D-Link Router is not registered with your Cable Modem and it needs to be a straight Cable Modem, without a Router, in order for the D-Link Router to capture your True IP Address from the Cable Modem or DSL Modem without a built-in Router.

In either case, the D-link Router, must capture the true IP Address on that line to report it correctly to http://www.dyndns.com/

Check the line on your Router.

Thanks for the reply.

I am also using a dir655 1.21 and I use the EXACT SAME cable modem as the one pictured previously with dir655 v2.00 and mine is working perfectly under 1.21.

In the "status" page, I see the actual wan modem adress 24.37.xxx.xxx, not 192.168.0.xxx. I am able to connect using the 24.34.xxx.xxx adress when the other person gives me that wan ip adress that he see in the status page of the dir655 so I know it is the one from the modem. It is a single modem without a built in router.

Even with the dsl modem WITH built in router, if you setup your internet connection to DHCP, you will get a local ip adress like 192.168.2.xxx but if you use the PPPoE type connection EVEN TRHOUGH the built in router, it will connect directly to the modem and will NOT use a lan adress. The dir655 will display a wan ip 70.53.xxx.xxx which is again, the real wan dsl modem adress.

In both cases, there are absolutely no reason it shouln'd work. We have only two providers here. Videotron (cable) and Bell (dsl). I've setup other people with 655 and it always work perfectly.

If I could show you the routers, I would also post the status page but I can't access the routers without the other person giving me the wan adress in the status page and at this moment, I am not able to get in touch with them to do it.

Hope this help narrowing the issue.

[thecreator]

Thanks for the reply.

I am also using a dir655 1.21 and I use the EXACT SAME cable modem as the one pictured previously with dir655 v2.00 and mine is working perfectly under 1.21.

In the "status" page, I see the actual wan modem adress 24.37.xxx.xxx, not 192.168.0.xxx. I am able to connect using the 24.34.xxx.xxx adress when the other person gives me that wan ip adress that he see in the status page of the dir655 so I know it is the one from the modem. It is a single modem without a built in router.

Even with the dsl modem WITH built in router, if you setup your internet connection to DHCP, you will get a local ip adress like 192.168.2.xxx but if you use the PPPoE type connection EVEN TRHOUGH the built in router, it will connect directly to the modem and will NOT use a lan adress. The dir655 will display a wan ip 70.53.xxx.xxx which is again, the real wan dsl modem adress.

In both cases, there are absolutely no reason it shouln'd work. We have only two providers here. Videotron (cable) and Bell (dsl). I've setup other people with 655 and it always work perfectly.

If I could show you the routers, I would also post the status page but I can't access the routers without the other person giving me the wan adress in the status page and at this moment, I am not able to get in touch with them to do it.

Hope this help narrowing the issue.

Hi Alezis,

I have Verizon FIOS. It comes with a specific ActionTec Router that has the Co-Axial Screw-on Cable Connection. I need to plug the D-Link into one of LAN ports on the ActionTec Router.

I can't use "PPPoE type connection EVEN TRHOUGH the built in router".  I could not get the IP Address that way. I just tried it. But I used Admin and Password to log into the ActionTec Router from the D-Link Router, and could not get the IP Address.

FIOS is different from Cable and DSL.