Print

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

[ThePink]

Recently ran the firmware upgrade to 1.30 beta and ran it for about a week till I saw that 1.31 was available.

Not wanting to stay on a beta and hoping that maybe the 3G option had been put back in I upgraded to 1.31, resetting to factory defaults and then applying my local wireless settings.  Did not adjust any of the other settings, just my SSID, WPA and my passphrase.

After two days the router was just not responding.  Lights were on but no-one was home.  Cycled the power on the router and cable modem (Cogeco standard high speed), saw the wireless network appear and disappear moments later.  Discovered from a wired pc, (yes where i did the updated firmware from in the first place) that if I disconnected the WAN cable the router would stay responsive on the LAN and I could access the setup pages.

Read several articles, tried several things, from reflashing 1.31, setting the wan speed manually, running with default settings all to no avail.  If the WAN connection is plugged in the router stops responding to LAN and WAN requests within seconds.  I've tried to see what happens with the setup pages active and plugging the WAN cable in.  Then the page will change advising that it's trying to determine my gateway speed and then it times out and just brings me to a failed IE page where M$ offers to help me diagnose my issue.

Disconnecting the WAN cable and firing up the router again, allows me to get back in to setup.  My settings have all been the same since I got the unit over a year ago.  Even the pc and cable modem are the same.  Nothing on my network has changed except the firmware, unless Cogeco has changed something a day after I did the update.  Plugging in an old linksys befsr41 provides a reliable connection so I know it's not something as basic as the service or the pc being able to communicate.

Ideas?hints?tips?suggestions? The only thing I haven't done as yet is try to downgrage back to 1.30 beta.

[lizzi555]

Try to disable the automatic uplink detection in the QoS menu.
Set the value of your provider manually or better a bit lower.
If this doesn't help, try to disable QoS at all.

Perhaps its a fault in the cable between router and modem - did you already change it ?

[lotacus]

How is the internet port set up? did you perhaps assign it a static IP?

[Lycan]

Connect to your modem and pull an IP address. Reply with that address.

[ThePink]

Lizzi555 - disabled QOS, no joy.  Tried again this time also disabling the Auto Uplink and manually setting to 512.  Normally I get 9000 down about 650 up.  Third kick at the cat I tried setting it to Cable or Other Broadband and ensured that under Adv. Network that the Wan Port Speed was first set to Auto, then tried 10 meg the forth time around. Also swapped known good ethernet cable.

Lotacus - IP is assigned via DHCP from the ISP, Cogeco Cable in this case.

Each time I will reconnect the WAN cable, I'll see on the Status page that it'll report the cable as connected and that it's establishing an address.  If I leave the Status screen and come back it'll report it now has an address.  Within 30 seconds although the Status screen is still showing me the time tick by the router has stopped responding and the WAN activity light goes out.  Disconnecting the WAN cable, waiting a bit and trying to log in still doesn't bring it back.  I wind up having to cycle the power and start again.

Lycan - not sure I follow, however if I do, with my BEFSR41 I pickup 24.141.243.24 and with the DIR-655 what the status screen will show before the router stops responding is 24.141.253.48  So Cogeco is definitely assigning a different address.

One thing I haven't done as yet is called the cable company and tried to see if there would be anything with my service that might be affected by any QOS enhancements from the new firmware.....if there are any that would change the connection so radically.

Thanks again for the the replies.  I appreciate it.  It may be posted elsewhere but can I set the 655 as an AP and just not use the WAN port, I'll just connect it to the old linksys and at least get my wireless running in the house again.

[mackworth]

What happens when you don't change any settings, just a fresh reset?  Same issue?  If not, try enabling your customizations 1 by 1, and see if you can find out which settings it causing it.

For example, when I upgraded to 1.31 and put in all my settings at once, my router started to go into a rebooting loop. It was the time server that I had entered.

[Clancy]

Does the connection between the Cable Modem and the router need to be a Crossover cable? I've been reading the user manuals for the modems supplied by Cogeco and they say you need a Crossover cable to go from modem to hub, or switch, but there are no instructions on how to connect to a router. In this case, is the router the hub? (I'm still learning) If ThePink is already using a Crossover I will leave quietly.

[davevt31]

Using standard cable between my cable modem and 655.

[Clancy]

ThePink, do you have your NIC's MAC address entered into router setup? Have you changed your NIC recently? Do you have "Obtain IP address automatically" checked in your TCP/IP settings?

[Clancy]

Using standard cable between my cable modem and 655.

Dave, do you know if your modem's user manual mentions anything about connecting it to a hub, or switch, or router? Just wondering that if it did say use a crossover cable then I would have to conclude that a router is not the same as a hub. Just thinking out loud. Hope Xinot isn't listening.

[Xinot]

Dave, do you know if your modem's user manual mentions anything about connecting it to a hub, or switch, or router? Just wondering that if it did say use a crossover cable then I would have to conclude that a router is not the same as a hub. Just thinking out loud. Hope Xinot isn't listening.

Im not here. 
I just dont think there should be any problems with either of this cables (crossover or straight-through). This router should know what cable there are connected if im right with this.

[Demonized]

Yep, the router has automatic MDI/MDI-X Configuration on-board

[davevt31]

Most Switches have auto-sensing ports and can work with either cable.  Hubs do not have sensing ports and that is why a crossover cable is needed when attaching to Hubs together.

[Clancy]

Thank you Dave and Demonized and Xinot. I learned something today. ThePink mentioned that the modem firmware was upgraded. From reading the D-Link manual I learned that some ISP's look at the MAC address of the nic on the other end and if it is not the same as the original when the internet service was setup that it might cause a problem. I don't know where that information is stored or if it is even needed. Still thinking out loud here. I would check the TCP/IP settings to see what they are in case they magically, mysteriously changed. That probably isn't it since ThePink can hook up an old router and get it to work. Out of curiosity, I would like to know the brand and model number of the Cable modem just to do some digging on my own. And yes, I do have too much time on my hands and since I can't figure out my delayed write error problem I'm fixating on something else. Besides, this is such a civilized conversation we're having. Xinot hasn't made me feel like an idiot ONCE!