Print

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

[no2u]

Since upgrading firmware from 1.13 to 1.22 (1.20b8 had same issue), router is locking up once a week.  Symptoms are no access to WAN, and router does not respond to http port 80h (over wired LAN), and its DHCP functionality seems to be inoperative as well.  Wireless is broadcasting at 100% signal strength but it doesn't help much when DHCP isn't assigning an IP address.  In this state, the router does respond to ping at 192.168.0.1, and I can access all other PC's on the wired LAN that already had IP addresses assigned.

Configuration-wise, on the wired LAN I have a print server and webcam behind an ethernet switch, and a mix of Windows and linux-based PC's.  I have one laptop using wireless-G.  All LAN devices are using DHCP, but some have fixed IP addresses configured in the router, whereas others are using dynamic IP allocation.

In 1.20beta8, when this occurred the WAN LED would be on solid yellow.  This is one difference, when using 1.22 firmware the WAN LED is now blinking green when it locks up.

Power-cycling the router makes it work again (for about a week), as does temporarily removing all wired LAN connections.  Removing the WAN connection had no effect (still could not access router's admin port 80h), but I found that wireless began working (router finally assigned a DHCP address and started responding to http port 80h) after removing all wired LAN connections.  Peculiarly after reconnecting all LAN cables the router temporarily dropped the wireless connection and assigned a new IP address to my wireless laptop.  Verified that I could access the WAN successfully at this point from the wireless laptop and from other PC's on the LAN.

Too bad I can't downgrade back to 1.13 which did not have this issue.

[no2u]

This router lock-up issue seems to be occurring every 4 days now.  I can probably predict with my stopwatch when the router will hang next, I don't know if it's an issue with acquiring a new WAN DHCP address (I wish the status page would tell me when the WAN DHCP lease will expire), or the log is filling up and overwriting memory, or maybe a stack overflow, or what.

I have tried enabling/disabling Advanced DNS, enabling/disabling graphical authentication, enabling/disabling "use multicast", enabing/disabling anti-spoof checking, etc, but nothing seems to matter.  After about 10 calls to customer support, they still have no ideas, have shown no interest in the router configuration settings, and still don't want to swap it out (personally I don't think it's bad "hardware" either --- heh I've been writing firmware for 25 years myself and this time I'm uncharacteristically saying it's a firmware bug  ).  They've suggested useless experiments like re-flashing the firmware multiple times (presumably just to get me off their back for another week), even though 1.20b8 and 1.22 both had the same problem.  Still wish I could go back to version 1.13.

If I bypass the router and connect direct to the cable modem, I can access the internet just fine, but I would certainly prefer to have a router if just for the NAT functionality.  I'm not even using the wireless at this point.

[no2u]

UPDATE:  I tried disabling "DNS Relay" on 9/23, and the router has been working for a whole week now without locking up.  In my experience, that's a record for 1.2x firmware.  I'd say there's something wrong with "DNS Relay".

Certainly this workaround is better than adding a timer switch to power cycle the router every day.   

[smlunatick]

I would like to state that the DNS Relay seemed to be a problem with "day one" of owning my DIR-628 and that was before the 1.2xx firmwares.  I rather have DNS server entries from my ISP (or OpenDNS) DNS services than rely on a "crappy" performance caused bt the DNS Relay / Advanced DNS.

[weathersinc]

I am also having the same problem.  It started when I upgraded from firmware 1.13.  I have contacted support and they are RMAing the device with a device with older firmware.  I too think that it is the firmware and not the hardware.

[smlunatick]

I viewed posts in the "other" forums here and there are a lot of posts that have the same problem.  Most of "their" solutions point to the 'DNS Relay" / "Advanced DNS" service as a principle cause to this "style" of problem.  The only general accepted "solution," for now, is to disable this "optional" features.

[ulric]

Some problem here.
The Dir-628 locks up once a week, sometimes twice.

I'm quite disappointed because I've never had a router needing to be rebooting, and I had paid extra for this one hoping for better quality.

It's so strange! can't even access the router's admin page when this happens.  Advanced DNS is disabled here, but DNS Relay was not.

I thought I couldn't turn off DNS Relay, but I just realized I needed to restart the computer so that it resets its DNS.
Thanks


Just to confirm, turning off DNS Relay fixes the problem!

[manolito2112]

I'm having the same issue every single day, only way to resolve is by doing a hard reboot, I Don't recommend this router to anybody because this looks as a common system crash issue and I don't see further intentions from dlink team to correct this issue, I have no problem at all with the same network configuration since a replace the router functionality to a new different box ( a expensive Juniper netscreen )
The DIR-628 is acting now as a regular bridge since a disable the WAN port, DHCP, and Upnp to delegate those functions to the new router box, most of the connection, dropping and freeze problem in this forum are related to same issue
SMART TIP:
Have always with you powerful router (usually a expensive one) to delegate routing function on
Use a WIRELESS BRIDGE ( as stupid as better ) for media conversion ( wireless to wired )
Don’t deal with too much compromised toy’s boxes

[GRIFFON]

I am also having same problem after I upgraded firmware 1.13 to 1.22NA...

D-Link Support says "a large amount of traffic may lock the router up"
I just wanted to say... "Are you kidding me?"

and their provided solutions are....

1. Disable any broadcast protocols.
2. Disable UPnP.
3. IP Filter to block user where a large amount of traffic comes.
4. Flash Firmware with the latest version over and over again.
   (hello? I am having the problem with THE LATEST FIRMWARE..!)
5. Perform a hard reset on the router and reconfigure.

None of above solution worked for me.

and nothing mentioned Disabling "Advanced DNS" and "DNS Relay" which worked fine with me to solve the problem..

For the moment, I have to disable "Advanced DNS" and "DNS Relay" so that my DIR-628 works fine without locking up...

(Sorry to say this... but this is my impression...)
To find a solution for the problem, this forum is much better (and more helpful) than Support Center in D-Link.

[Danny1976]

If you are using windows 7, Disabling HomeGroup fixed my problem... I've been up and running 24 hours without requiring a router reboot and wireless is working great.

[ulric]

If you are using windows 7, Disabling HomeGroup fixed my problem... I've been up and running 24 hours without requiring a router reboot and wireless is working great.

That would be a fluke, because that's not what's making the router lock up.
it's a problem with the DNS relay feature

I had the problem with mac.  Recently I now have a windows 7 box on the LAN, tool.  Homegroup is on; no problem.  There are multiple computers connected to this router now. Two macs, two PCs, one PS3. two of them through WIFI.  Everything is fixed

[thomasrelee]

That would be a fluke, because that's not what's making the router lock up.
it's a problem with the DNS relay feature

I had the problem with mac.  Recently I now have a windows 7 box on the LAN, tool.  Homegroup is on; no problem.  There are multiple computers connected to this router now. Two macs, two PCs, one PS3. two of them through WIFI.  Everything is fixed

Windows 7?  HomeGroup?  Man, Windows 7 just launched...  just how many people do you think are using Windows 7 now?  Not many.  These issues were prevalent well before Windows 7 and D-Link has done nothing to resolve them.  The router is locking up due to everything it is programmed to control. 

I have noticed this router requires hard resets every 24-48 hours, regardless of use!!!  I have tested, reconfigured, upgraded, downgraded and tried everyone's ideas as to what may be causing this problem.  Over the past two weeks, I have continued having this router crash and require a hard reset. 

    -  The Wii has been unplugged, so there are NO wireless devices in range trying to connect.
        (trust me, I live in the middle of NO WHERE!)  As for wireless interference, the router is configured
        for 2.4 ONLY.  My wireless telephones are 5.8 ONLY.  I have even tested my microwave for
        excessive leakage, as I could see where a major leak of radiation (@2.4ghz) would be a problem.

    -  The computer running Vista Home Premium hooked up to the TV only accesses the internet for
       Media Center Guide updates, Windows Updates, Netflix and Hulu.   Power Management on the
       network controller is turned off -- as suggested.

    -  The computer running XP Pro SP3, as a media server and file sharing server, has been turned off
       for the past two weeks.

    -  I've used the phone/Vonage, very little, less than 4 hours total in the past two weeks.

    -  The main computer running a dual-boot of Mint Linux and Windows Vista Home Premium (usually
       running the Mint Linux and not Windows,)  has only been used for surfing the web, reading e-mail
       and watching online video from sites like Hulu and YouTube.  I have come to the conclusion that
       Windows Vista, unlike Windows 7 as you suggest, does not have any effect on the router.

As previously posted, the ONLY problem I see, the router is blocking connections, as it should from the WAN.  Does not matter if you log these events or not, the router is still actively doing something even if you are smart enough to just turn the logging OFF.  Every time I perform a hard reset, I proceed to request a new IP from my ISP.  No matter what IP I land on next, the WAN traffic that requires consistent blocking is always there.  The router locks up in the same manner each and every time and this has gotten OLD over the past year.   

[ulric]

It's not impossible that your router is simply broken (or that there an electrical problem)
it's terrible, but it happens.   my own Dir-628 router hasn't been rebooted since that post I made up there, last October

[Danny1976]

Go to that link to downgrade from 1.22NA to 1.12.

http://forums.dlink.com/index.php?topic=11135.0