Print

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

[pp1111]

After I updated to firmware 1.05 or 1.10. My router always shows connecting to the internet and last forever.
Tired unplug both modem and router power for 5+ mins.

I'm using cable modem. (Shaw)
If I go back to 1.04 or before, it works fine.
Anyone got the same problem?

Thanks alot.



DHCP Client

QoS Engine : Active

Cable Status : Connected

Network Status : Establishing (please wait...)

Connection Up Time : 0 Days, 0:00:00

[Lycan]

Who is your internet service provider?

[pp1111]

Shaw in Vancouver 

[rydude]

Check the cabling between the modem and the router.  You may have to change to a different type of cable for it to work.

[barich]

I have the exact same problem with 1.05.  See here.  I haven't tried 1.10 yet, but I'm going to tomorrow.  1.04 and earlier work fine.

At the moment, I'm running a Netgear WNR834B, because it is more reliable than the D-Link has been, but it has worse wireless performance, no gigabit ethernet and, even though my internet connection is only 2 Mbps, it seems slower at loading web pages (probably because it has no QoS, either).  I certainly hope I can get the D-Link working properly, because when it was it was a great router.

[laltj]

After I updated to firmware 1.05 or 1.10. My router always shows connecting to the internet and last forever.
Tired unplug both modem and router power for 5+ mins.

I'm using cable modem. (Shaw)
If I go back to 1.04 or before, it works fine.
Anyone got the same problem?
Thanks alot.

Please try cross over cable from Shaw Modem to DIR 655 and try configuring to see you get a WAN IP Address with firmwares 1.05 and 1.10.

[pp1111]

tired all, no help still 

[rydude]

After I updated to firmware 1.05 or 1.10. My router always shows connecting to the internet and last forever.
Tired unplug both modem and router power for 5+ mins.

I'm using cable modem. (Shaw)
If I go back to 1.04 or before, it works fine.
Anyone got the same problem?

Thanks alot.



DHCP Client

QoS Engine : Active

Cable Status : Connected

Network Status : Establishing (please wait...)

Connection Up Time : 0 Days, 0:00:00

Due to major Shaw upgrades, you will need to downgrade the firmware to 1.04 until a new firmware is released.

[Titaniumbrain]

I have the exact same problem over here in Montreal using Videotron cable internet.... it always says Establishing (please wait...)

dpsoak: If the cable works fine with firmware 1.01 to 1.04, how can this problem be attributed to a cable?

rydude: Can you explain why this is the case?

[barich]

I got around to testing 1.10, and it does the same thing.  In fact, it's even worse.  With 1.05 it would state that the cable was connected and that it was "establishing" the connection.  With 1.10, it didn't even recognize that the cable was plugged in until I manually changed the WAN port speed to 100 Mbps.  Firmwares 1.04 and older continue to work fine.

[tonyyen]

After I updated to firmware 1.05 or 1.10. My router always shows connecting to the internet and last forever.
Tired unplug both modem and router power for 5+ mins.

I'm using cable modem. (Shaw)
If I go back to 1.04 or before, it works fine.
Anyone got the same problem?

Thanks alot.

=======================================================

same here, exectly the same issue.

and I checked all the cables, connection, etc...all

but still......need to install back to version 1.04 in order to work.

but, I've been using version 1.05 for a while, works fine and suddenly..this problem pops out.

Anybody got any idea?

DHCP Client

QoS Engine : Active

Cable Status : Connected

Network Status : Establishing (please wait...)

Connection Up Time : 0 Days, 0:00:00

[spliffstarr]

I have the same problem with my router and my shaw connection. Everything was running ok until about a week ago and now it no longer can get an ip from shaw. I have tried 1.05 and 1.10 with no luck. I assumed the was port was broken and i was going to return the router for a new one...

[spliffstarr]

1.04 seems to have fixed the problem for now, though it kinda sucks that i have to do way more troubleshooting with this router than i did with my linksys 300n which just worked...