D-Link → DI-624 version 2.70 available

Initially 2.70 seemed to have a faster throughput, but as I used it (on my own personal network and at my parents house) it seemed to have serious issues with sustained connections/downloads.

I, of course, had the DHCP connectivity problem with my Centrino laptop, using WPA2-Auto fixed that issue right up.

But on my desktop (wired) and my laptop (wireless) I was getting quite alot of variance in my download speeds, as well as dropped connections in the middle of a download (this was not P2P, it was direct file downloads from various reliable servers)

Ultimately, before I reverted to 2.50, I would be regularly dropped from a download only minutes into it.

Now back at 2.50, I have no issues at all.

I am also back at a trouble free 2.50. I installed 2.70 ans immediately started to see repeated disconnects untilfinally it disconnects and cannot reconnect.

I've had version 2.70 for several days now.
I notice that it reboots about once a day.
That's not acceptable for me so I went back to 2.50.
Been two days without any reboots. Been using 2.50 for a while. It seems to reboot once a week.

i just bought the DI-624 revC and updated the firmware to 2.70, i have a toshiba satellite laptop with an intel prowireless 2200BG adapter, i also updated its driver. Then finally i installed the WinXP SP2 893357 for WPA2 enabling. After all this, i can't get my laptop to connect with WPA2 security, it only connects when security is WEP. I've tried WAP, same problem, it keeps on "limited or no connectivity" after "enabling network...." for quite some time.

This is the only post where i've seen some info that relates to my problem and hope someone can help. Would really appreciate it.

eMule's KAD still causing reboots using 2.70. eD2K part seems stable as before.

Disable SuperG. I believe you will get your problem solved. The problem is that it seems you can authenticate, but cannot get an IP address when using WPA2+SuperG. So, disable SuperG and post your results here.

Hope this helps,

Richard.

Has anyone noticed that with version 2.70 that the clock gains time - approx 30 minutes a day? I have used the firmware from the USA site on a UK router. With all their technical knowledge have the Americans found a way of making time run quicker?

Got 2.70 installed with WPA2-PSK AES turned on and Super-G off. Have two computers connected to it via DWL-G520 and some Broadcom 54g card in my laptop. 520 needed upgrade to latest drivers to support WPA. No problems to report.

Please report back if you notice problems with your LAN. Maybe accessing files in the second computer or printing. Everything was fine with 2.70 for a few days in my setup, then the LAN began acting up.

Upgraded my DI-624 rev C1 to fw 2.70 and the router keep rebooting 1-2 times a day. This is not acceptable so I'm back to 2.52 beta 39 build for me.

Thanx Richard,

It seems to work on WPA2-Auto with AES & PSK (Super G with Dynamic Turbo is on). After disabling Super G and leaving it on channel 6, i chose WPA2 PSK & AES (without the Auto option) and still got the same problem, it authenticates but doesn't assign me an IP address. The D-link tech service also had me disable the Super G and put it on channel 10, and that didn't work even with WPA-PSK TKIP (not WPA2). The D-link service that told me it was WinXP SP2 bug "limited or no connectivity" which can be fixed, i guess they blew me off with that, because there were no such bug with wireless connections, it was a bug for DSL/Cable LAN connections.

Anyways could this be a problem with the Intel PRO/wireless 2200BG preinstalled on my toshiba centrino laptop? I already upgraded the driver to the latest 9.0.2.31 (driver date 7/19/2005).

I also installed the Microsoft update KB893357 for WinXP SP2. I noticed that when i'm on WPA2-Auto, it doesn't request the passphrase when connecting. Also when using WPA2 without Auto, i try to type in the passphrase myself from the properties of the preferred networks, but it still won't assign me an IP address. Then when i go back to the properties again, i find a different 8 character passphrase on there by default??!

I also did notice a "time" problem, its always going back to april 1, 2002. I guess this the APRIL FOOLS FIRMWARE,haha. Anyways, the time doesn't bother me, i just saw someone mention it.

Zoos

Hi!

The time problem means your router is rebooting.

About the DHCP problem, it happens to a lot of people, not only the ones with INTEL adapters.

In my case, i get it solved by using TKIP.

I also have a DWL-2100AP wich i use with WPA2-AES. No problems whatsoever, so, the problem must be in the router.

Richard.

I just flashed my router this morning. It actually rebooted while I was in the middle of changing the settings. Then it continued to reboot randomly throughout the day. Once, it rebooted three times in a row with just seconds between each reboot. There is only one wired and one wireless computer connected to it, I just got back from a trip and haven't unpacked my notebook yet.

I reset the router to factory default setting, changed the password and disabled the wireless radio and it hasn't rebooted yet. I'll start changing one setting at a time and see if I can find out if it's a setting I'm changing that's causing the reboots.

:::

DI-624C3 v2.7 WPA-AES in action with Bit Torrent...!

:::

U have 1372 concurrent connection?!!! My goodness, that is GREAT!

Yes ! And he is so smart to keep his private, reserved, unroutable over the internet, unreachable IP-address space a secret so we can't hack him. (/sarcasme)

But serious Talon88: it's still confusing to new users.

Bwuutje.

:::



Bwuutje, My Screen Shot are for Advance User like
you..... hehe... I don't think noob user actually
know what the shot is about....

:::

I've tried everything and it seems that if I have the wireless radio on, I get random reboots. Turn it off and it runs fine. I guess it's back to 2.50 for me.

2.7 was a complete disaster for me. for a minute I was checking to see where I can get a new wireless router cause I for sure thought that mine was dead.

I put back on 2.50 and it's been clear sailing since then.

Things were working perfectly well on 2.42; I never should have attempted the upgrade. (especially given the hell I went through to get 2.42 to flash properly)

My Windows notebook worked fine, but the Mac OS X never was able to connect. Weird, things usually work the other way.

Anyways, I have finally given up. The new Linksys WRT45G went in in seconds, and everything flashed up on WPA2 beautifully in seconds.

Well, I upgraded to 2.70 back in August. Ran fine for about 48 hours then the 624 started rebooting. I found that the old phone in the garage was the culprit (2.4 Ghz). Solved that problem and ran fine until last week. I decided to run WPA/PSK with a paraphrase. I am presently writing this while listening to a Count Basie album on remote #3 in my network. Everything runs great and the Count is sounding good too.

Here's what I feel is the difference. I keep the machines updated with the latest from MS for XP-sp2. All the wireless units run D-Link cards so there is no incompatibility. I use SSID and MAC addresses because I want to. Call me old fashioned (been around since the 8088 and analog modems running 300 baud) but a little thought and planning seems to keep the problems to a minimum. I have yet to experience any of the problems that many of the owners of the 624 complain about and this is with any of the firmware! Maybe I'm just lucky.

When a new firmware comes out, I upgrade the 624 and add the settings a little at a time. This way, I can see if the problem is a setting or an outside problem. Perfect example is how the garage phone got me this time (it never seemed to bothered the system before 2.70).

Jimnms,

They may have messed with the sensitivity, in fact, they almost certainly did (definitely for XR, perhaps for other reasons too).

If that's your only 2.70 problem, and you want to use it, try reducing the Xmit power. In many cases, there is no performance loss and it will solve problems like you've described.

Another way to fix a problem like you've described is to stand the unit on end and swivel the antenna so it still points to the ceiling. This makes the signal travel along a thinner surface of the unit and may be enough to avoid self-inflicted radio interference.

The microsoft download fixed my problem. I have a Dell 600m with the intel wireless adapter. I wasn't able to get an IP address from my router. After installing the fix, everything works great. Thanks

I tried the 2.70 firmware,what a reboot job i had on my hands. I turned the tx power down to 12.5% with no luck. No matter what i did it would reboot every 2 or 3 minutes tops. I went back down to 2.50 and no reboots , very solid. i have noticed anything above 2.50 for me is trash nothing but reboots.

I have tried crash recovery and not, to see if there is a difference and it ends up the same. My hats are off to dlink on there firmware they are doing a good job. I hope they read these and maybe they can fix there firmware problems (reboot problems) Soon.

Well, now that I have a new C3 router after RMA'ing my C1, I've got first-hand experience with 2.70, which came preloaded on the replacement C3 router. At first blush, it worked wonderfully, but after a couple of hours of extended use, I found the following bugs:

1) Wireless client (MacOS X 10.3.9) can't get a DHCP lease when using WPA-PSK w/ AES encryption. This has been reported here repeatedly, so it's clearly widespread. I can't use WPA2 (wasn't able to connect wirelessly at all with WPA2, don't know why since OS X supports it!) and did not try disabling WPA to see if DHCP worked. Manual network settings work just fine in all circumstances.

2) Network connectivity will hang after ~1 hour. The wireless connection is up but the router does not respond to ANY packets from the wireless client. Wired connectivity works just fine, and disconnecting/reconnecting the wireless client will reset the network connection and restore connectivity... but obviously it loses any open connections and is a pain in the butt. I don't know if this is WPA-related or not, since I did not try disabling it.

3) OS X Printer Sharing does not work between wired and wireless clients with this firmware. It works fine between two wired clients, but a wireless client can't see any shared printers that are shared from a wired client.

Downgrading to firmware 2.42 solves all of these issues, obviously. I suspect 2.50 would also probably work, but I haven't tried it yet... I figure 2.42 is stable enough for me. No reboots on 2.70, at least.

I reported all of these issues directly at D-Link's website, so hopefully something will happen, someday. Yes, I'm an optimist.

Oh well, 2.42 for me, for now. Unless anyone knows other workarounds for the above issues?

Folks,

Last time, I have shared with you that the WPA2 - DHCP issue seems to be solved. But, not exactly all the way.
When the router has just flashed with the 2.70, it works flawlessly for many, many days. The connections with all laptops were fine... Until I shut them off - not standby or hibernate - and turned them back on, the problem came back. No DHCP. However, after 2 weeks of trial-and-error, I have found a workaround for myself and hopefully it will work for some of you...

I have a several laptops with Intel Centrino (2200BG adapter), running Windows XP SP2 with the WPA2 update.

1. Add a Maunally Configured connection under the TCP/IP properties in Windows... Wireless Connection Properties > General > Internet Protocol (TCP/IP) > Properties > Alternate Configuration > User Configured...

2. Pick an IP Address you want to assign for your computer, Subnet Mask is 255.255.255.0, Default Gateway is 192.168.0.1, and I like to use 4.2.2.1 / 4.2.2.2 as DNS servers...

3. So whenever you connect the computer to the router, you may see it is trying so hard to acquire an address via DHCP. But, it may likely to be time-out. Then the Alternate Configuration will kick in. At this point, you should at least have access to the router if not all the way to cyberspace.

4. Log into the router and force reboot it... Tools > Misc. > Reboot.

5. When it comes back online, just hang on for another while... The DHCP should work and you can verify with the Network Conenction Status in Windows as well as the router's DHCP table.

Good luck.

Well, if you would actually read this forum and this thread you would have seen that manually setting an IP if the router's DHCP-server doesn't work correct has been suggested many, many times before.

"2. Pick an IP Address you want to assign for your computer, Subnet Mask is 255.255.255.0, Default Gateway is 192.168.0.1, and I like to use 4.2.2.1 / 4.2.2.2 as DNS servers..."

Erhm..those DNS IP-addresses you are mentioning are the ones YOU need to use in combination with YOUR provider. Completely nonsense to post them here, stop doing this.

Let me try to explain in a simple way: DNS-server addresses are provider-specific and large providers (can and will) have more DNS-servers their clients should use. Also these (resolving !) DNS-servers are usually set to only serve their own customers, so e.g. a AOL-customer can and should not use Comcast DNS-servers to resolve IP-addresses.

Bwuutje.

4.2.2.1 - 4.2.2.6 have open for everyone to use since 1999. It is owned by Verizon/Level3 who inhereted it from GTE.

Even though that was only 6 years ago, the fact that they're so easy to remember, answer ping, and are open to everyone, have made the 4.2.2.x DNS servers just an established historic and open public resource on the internet.

You'll find a list of other open and free DNS lookup services in the RCN FAQ here on BBR.

Yes, those particular ones perhaps are open. But in general my comment applies and maybe I should have mentioned that.

Besides that however it's always best/better to use your providers own DNS-servers since they often are closer to you and so respond faster (well, at least should be). And in general providers are preventing more and more that other (non-customers) are (mis)using their servers/services and especially DNS-servers since they have been abused and have proven to be both vulnerable and critical to an ISP's operating business.

So if tomorrow Level3 (or anyone else) decides to be less philanthropic and close this free services to the public you have to change them anyway...