Equipment Support > Hardware By Brand > D-Link > Known Issues with 2.37 Firmware and DI-624

reply to SoCal99

Re: Known Issues with 2.37 Firmware and DI-624

Just installed the 2.41 update. So far everthing seems stable. I was very %$#@% with V2.37, almost to the point of chucking all my DLink product. I will reserve any final opinion for a few days.

reply to SoCal99
No Bueno here for me with the 2.41 firmware regarding the ONE issue that affects me--the date/time issue.

I even tried resetting to factory and ONLY installing the 2.41 firmware, and that didn't even resolve the issue.

But then again, the notes for this revision didn't specifically indicate that it was resolved with this particluar revision . . .

Sure hope they fix it soon, because my 30 days is closing in quickly . . .

reply to SoCal99
Ok looks like firmware 2.41 is out so let's see if this helps any of the known issues that 2.37 has

FW »support.dlink.com/products/view.···4%5FrevC

New Thread »DI-624 Rev C New Firmware v2.41

reply to DLINK2
DLINK2 said:

D. This is a driver issue, or an OS issue. Not a router problem. You can test this yourself by, using a different wireless card.

The fact that so many of us seem to be having different, or even contradictory, experiences, really underscores just how difficult it is to nail down the specific causes when there are SO many variables to take into account that could conceivably be relevant.

I don't have a linksys device in the mix, but I've got a di-624/c2, a laptop with a dwl-g650 (XP/home), a pc with a dwl-g520 (xp/home) and a hard-wired pc with xp/home.

Once I upgraded past fw 2.28 for the di-624/c2 (using the "factory reset" procedure), and ever since, using 2.37 and 2.41 fw, I have yet to see any problems such as the ones you're describing. The router itself had been rebooting only occasionally under fw 2.37 -- and the wireless devices would reconnect pretty much instantly. I've had 2.41 running for a couple of days now, and haven't seen a single reboot or disconnect.

I'm running dynamic turbo, and the 624 is set to CTS off, G only, UPNP off, standard dynamic dhcp on. It all works beautifully.

If the router CAN work properly in some instances, as it appears to in mine, I'm more inclined to think that the problems lie either in the particular OS config (e.g., updates applied, particular driver combinations, Windows settings, etc.), the driver for the network adapter, or a combination of the two. Unless there's some invisible difference between one DI-624/c2 and another, these should behave identically. That we're seeing seemingly different behavior really convinces me that we should be looking at the pc's, windows configs, and possibly the network adapter drivers and/or the software used to manage the connection (e.g., D-Link utility or Windows wireless zero config).

Re: Windows -

I've got ALL updates applied, and also ran the Wireless rollup, although I haven't taken the time to see if the combination was actually redundant. Certainly doesn't hurt to run them all even if a couple of patches are applied twice.

I've also unchecked "allow windows to manage your wireless connection" and use the D-Link utility instead.

Anyway - on the surface, it sounds like you and I have overlapping setups, but my G650 and G520 reconnect instantly with the DI-624 whether it reboots itself (rare, but was still happening occasionally last week), or if I reboot it as a result of changing a setting.

If I reboot the laptop or the pc with the g520, it also reconnects to the di-624 instantly, gets a new dhcp assignment, and is off and running.

I don't doubt what you're reporting. But unless we're assuming that different di-624's act differently, I'm pretty sure the explanation is more likely in the Windows config, the level of updates, the network driver or some combination.

- Jon
--
-- Jonazen --

said by jonazen:

---

I don't doubt what you're reporting. But unless we're assuming that different di-624's act differently, I'm pretty sure the explanation is more likely in the Windows config, the level of updates, the network driver or some combination.

- Jon

---

reply to jonazen
I am open to the possibility of it being windows, but this is the main reason I still think it is the router.

When everything (computers and router) has been rebooted, it always works (everything in fresh state). After a couple of days, when trying to start the computers, they can no longer connect. The computers have just been booted, so they are in that same fresh state as they were when they were working the day before. If I then reboot the router (taking it back to its fresh state) the computer will connect (no reboot needed). So nothing changes on the computer side, it is change on the router side that gets it working again.

If the problem was, after a couple days of uptime, the computer would drop the connection, but a reboot of the computer would fix it while a router reboot did nothing, I would say the opposite.

reply to jonazen
jonzen for the factory reset, did you do the 'deep reset' crash recovery and just load in the new firmware, or do you load in the original 2.28 and then load the 2.41? Thanks ;o)

I'm still thinking it can be my old motorola cybersurfer wave modem causing the whole problem. stupid nondocsis compliant but it runs fast without the router [

Hi -

I did the "crash recovery" routine -- unplugged the di-624, held in the reset button while plugging it back in, and kept the button in for another 10 - 15 secs until I saw all the lights flashing again.

Then I loaded the 2.37 directly.

When I upgraded to 2.41 from 2.37, I didn't bother with Crash Recover - just did a normal firmware upgrade from the router config menu.

I was prepared to do the crash recovery routine if this didn't work, but so far 2.41 has been working very well for me, with perhaps 1 reboot a week, and working perfectly in every other regard.

- Jon
--
-- Jonazen --

reply to todnbeck
What is the link to download 2.41?? official dlink
sites actual is still 2.37

reply to TheHondaMan
After I upgraded my DI-624 (hardware ver. C2) from v2.28 to v2.37 firmware, I noticed that the firmware upgrade instructions caution to only upgrade firmware via a wired (not a wireless) connection. Well, I think I already successfully upgraded my firmware wirelessly (at least the DI-624 Status panel indicates a "Firmware Version:2.37, Mon,23Feb 2004"), and my notebook computer is not able to "see" my DI-624 if I connect it to the DI-624 via an ethernet cable. Also, I am able to surf the web and post to this forum, so I must have succeeded in upgrading to the 2.37 firmware? Right?

reply to SoCal99
Let me add one more irritating thing that I have noticed.
I cannot edit or remove the firewall settings that I create.

I created one that is in error and cannot change it. Sure I can click on the edit, but everything is grayed out.

If anyone can help me, please email Tommy at vpn1951@yahoo.com. Thanks very much.

try changing via virtual server...

tmartindub:

I had a similar problem with my original 624 C2 upgraded to 2.37. I tried to use WPA-PSK and somehow got the pass phrase out of sync. I could not go in and blank out or change the pass phrase. I went to tools and restored a prior saved configuration. Everything seemed to work fine after that. I have yet to turn on WPA-PSK. I think I will wait until I apply the new firmware 2.4x.

reply to Roger_dd

said by Roger_dd:

---

What is the link to download 2.41?? official dlink, sites actual is still 2.37

---

reply to SoCal99
WOW!

Exactly identical problems. Only that tech support will not even acknowledge them