| Known Issues with 2.37 Firmware and DI-624 I'd like to document all known issues with the current 2.37 firmware and the 624 router (Things still to fix). I don't want to bash Dlink here, but I do want a place for experienced users to post, that have issues with features of the router (that they know don't work) and have called up-to Dlink Tech Support level 3, and Dlink still can not get it to work properly (thus ruling out any true configuration issues).
A. Router reboots when 2.4 GHz phone is in use and super g is enabled (level 3 acknowledges that a phone may knock out the wireless but should not reboot the entire router).
B. When router reboots, date and time are reset to April Fool's day 2002 and NTP doesn't work (level 3 acknowledges problem)
C.SMTP email logs don't work (level 3 acknowledges problem)
D.Some wireless clients won't auto connect to the network after a computer reboots (level 3 acknowledges this and thinks it may be a driver issue or OS issue)
E. When reloading the Saved Settings file, it does not remember the saved password for admin but resets it to "enter". On the 714p+ if you reload your Saved Settings (and it included a password) once the unit reboots you must relog in with that saved password, but this is not the case with the 624. (level 3 not sure if this is a bug or "new operation", been several weeks and I have gotten no update on this).
F. Enabling WPA-PSK won't allow some to connect to the network (I have not talk to Level 3 on this issue lately because once I install their dwl-g650/c2 and 3.17 driver, my wireless now connects to the network with WPA-PSK enabled).
G. Once a wireless connection is lost, a Rescan in Site Info won't reconnect the wireless client and the only way to get reconnected is to reboot the computer (Level 3 is still investigating this, but no word back in over a week)
What I'm not looking to do here is bash Dlink, but just collect some facts. I'm also not looking for the post, "well I have xyz enabled and it works just fine for me." Because I have seen too many situations where something works for one and not the other and later it turns out to be a Dlink bug, and in addition, once you have made it to level 3 you have confirmed that it is not a configuration issue.
Next, I'd like only posts where you have contacted Dlink lev 3 with the problem, that way they know about it, and it ensures by the time you have made it to level 3, you have tried every configuration possible with them. And if they still can't get it to work, then you both know its a bug whether stated or implied, for example they say, "it should work sir, I don't know what to tell you, I'll look into and get back to you" but hasn't happened yet and its been weeks. |
|
kpiskin
join:2004-01-20
Virginia Beach, VA | I can definitely confirm "G". |
|
| I can confirm B,C,D and G.
Steve Rose |
|
| reply to SoCal99
A. I cannot confirm this. I use an AT&T 2.4GHz phone right next to my system and my unit does not reboot. The base station was less than 10 feet away. Yes I have Super G enabled with Static Turbo.
D. This was my biggest issue. After starting this (»G520A2, 624C1 and Zone Alarm Pro) thread I also PM'd Dlink_help about it. He suggested I make a simple setting change to ZoneAlarm and this fixed my autoconnect issue. I am curious if more users have firewall's (even XP's firewall) that is causing this.
--
"We defend and we build a way of life, not for America alone...but for all mankind." - Franklin D. Roosevelt |
|
| said by Fubar12345:
A. I cannot confirm this. I use an AT&T 2.4GHz phone right next to my system and my unit does not reboot. The base station was less than 10 feet away. Yes I have Super G enabled with Static Turbo.
No need to, pla, matroy, ufokiller2 and others have confirmed that their 2.4GHz phones reboot the 624s also.
»DI-624 C1 2.37 keeps restarting |
|
cvp
join:2004-02-24
Boca Raton, FL | reply to SoCal99
said by SoCal99:
B. When router reboots, date and time are reset to April Fool's day 2002 and NTP doesn't work (level 3 acknowledges problem)
...
G. Once a wireless connection is lost, a Rescan in Site Info won't reconnect the wireless client and the only way to get reconnected is to reboot the computer (Level 3 is still investigating this, but no word back in over a week)
...
B. While it's true that initially after a reboot the date is set to April Fool's Day, if you have it configured as a router (not an AP) within a few moments of receiving its IP address it will reset to the current time. In AP mode it never will!
G. it's true that rescan won't work, but Disable/Enable will and is the essential part of the reboot - but a heck of a lot quicker!! |
|
|
|
| said by cvp:
it's true that rescan won't work, but Disable/Enable will and is the essential part of the reboot - but a heck of a lot quicker!!
CVP, I guess I should of been more clear. A reboot is the only thing that works 100% of the time for me. A Disable/Enable will only reconnect me about 50% of the time. |
|
| reply to SoCal99
said by SoCal99:
I'd like to document all known issues with the current 2.37 firmware and the 624 router (Things still to fix). I don't want to bash Dlink here, but I do want a place for experienced users to post, that have issues with features of the router (that they know don't work) and have called up-to Dlink Tech Support level 3, and Dlink still can not get it to work properly (thus ruling out any true configuration issues).
A. Router reboots when 2.4 GHz phone is in use and super g is enabled (level 3 acknowledges that a phone may knock out the wireless but should not reboot the entire router).
B. When router reboots, date and time are reset to April Fool's day 2002 and NTP doesn't work (level 3 acknowledges problem)
C.SMTP email logs don't work (level 3 acknowledges problem)
D.Some wireless clients won't auto connect to the network after a computer reboots (level 3 acknowledges this and thinks it may be a driver issue or OS issue)
E. When reloading the Saved Settings file, it does not remember the saved password for admin but resets it to "enter". On the 714p+ if you reload your Saved Settings (and it included a password) once the unit reboots you must relog in with that saved password, but this is not the case with the 624. (level 3 not sure if this is a bug or "new operation", been several weeks and I have gotten no update on this).
F. Enabling WPA-PSK won't allow some to connect to the network (I have not talk to Level 3 on this issue lately because once I install their dwl-g650/c2 and 3.17 driver, my wireless now connects to the network with WPA-PSK enabled).
G. Once a wireless connection is lost, a Rescan in Site Info won't reconnect the wireless client and the only way to get reconnected is to reboot the computer (Level 3 is still investigating this, but no word back in over a week)
What I'm not looking to do here is bash Dlink, but just collect some facts. I'm also not looking for the post, "well I have xyz enabled and it works just fine for me." Because I have seen too many situations where something works for one and not the other and later it turns out to be a Dlink bug, and in addition, once you have made it to level 3 you have confirmed that it is not a configuration issue.
Next, I'd like only posts where you have contacted Dlink lev 3 with the problem, that way they know about it, and it ensures by the time you have made it to level 3, you have tried every configuration possible with them. And if they still can't get it to work, then you both know its a bug whether stated or implied, for example they say, "it should work sir, I don't know what to tell you, I'll look into and get back to you" but hasn't happened yet and its been weeks.
Confirm:
B, C, D, E, F, G
I have installed over 20 DI-624s in the past month, have urged all to upgrade to 2.37 firmware...Seems 128bit WEP is the best way to go for wireless encryption instead of WPA-PSK, and it seems like the most reliable way to go is to use B-revision PCI cards, C-revision PCIMA cards, and C-revision routers.
--
The Power of Dreams. Powered by Honda |
|
Pla
join:2004-02-25
Mountain View, CA | reply to SoCal99
Definetly Confirm:
A, D, F, G
Have not tried any of the others. |
|
cvp
join:2004-02-24
Boca Raton, FL | reply to SoCal99
said by SoCal99:
CVP, I guess I should of been more clear. A reboot is the only thing that works 100% of the time for me. A Disable/Enable will only reconnect me about 50% of the time.
That's not my experience, SoCal. I can't say I'm happy about it, but one of the few things that I can count on in this fiasco is the Disable/Enable routine. (My experience is also only for XP Pro - I guess there are enough variables in this game that I should state that for the record).
And just to confound me - my router stayed up almost a whole day without a reboot, but I got up this morning to see that it's reverted to its old ways!!!
In any case, although I might be picky about those events you stated being 'always' and 'the only way', I'm 100% in agreement with the overall flavor of your original post. This mess is really unforgiveable from such a major participant in consumer electronics. |
|
| reply to SoCal99
I confirm A and B. Like I said in an other post, my 2.4ghz Uniden phone causes the router to reboot almost every time it rings and while being on a call. As soon as we hang up the phone the router stops rebooting and works fine except for the April date.
By the way, it reboots in ANY of the SuperG modes: no Turbo, Static and Dynamic.
The only way I've found to stop the the problem is to change the phone channel until I find one that is not interfering with the router. This is easier with the Turbo mode disabled probably because it occupies a smaller range of frequencies. Unfortunately, the phone doesn't display the channel numbers and seems to change each time we use it...
Martin |
|
| I can confirm G on XP Pro, SP1. (G650 rev B) |
|
| reply to SoCal99
I can confirm A. My phone is Panasonic 2.4GHz. I am using Static Turbo G only with WPA-PSK. |
|
| reply to SoCal99
I'm using DI-624 Rev C2
I ONLY agree on E & G since I have not problem using my 2.4G phone while I'm on the net, when router reboots the correct time's still there, SMTP log emailing never failed on me since the first day I use it. About problem D & G try not to use the WPA to connect and instead use the "OS" to take over the wireless network configuration. |
|
kpiskin
join:2004-01-20
Virginia Beach, VA | Has anyone seen a D-Link rep since we complained about 2.36? Seems like they think they solved all the problems. |
|
Chameo3
join:2004-02-20
Richmond Hill, ON | G. May be related to the client drivers not the router?
'»DWL-G520 Rev A New Drivers Released'
I'm using older client drivers and have not noticed this problem. |
|
| reply to SoCal99
I can confirm A for sure. I called tech support, and after getting hung up on by some fool who said my problem was that I was getting pinged to death (despite the fact that the option is checked to discard WAN pings), the problem was found to be the UPNP and Gaming enabled button states. Once those were set to disable, the router stopped rebooting.
D-Link needs some real techs working to come up w/ a version "3" that fixes EVERYTHING and makes the router work AS ADVERTISED. |
|
| reply to SoCal99
i have di-624 (rev.c firmware 2.37)and my issue still is part A -- everytime i make/receive call on my panasonic 2.4ghz i lose wireless connectivity on my laptop(dwl-g650) - hopefully d-link dont push me to invest in a new 5.8ghz corless phone |
|
1 edit | reply to SoCal99
Ok once Dlink fixes the known issues with 2.37 listed below, do they have a stable platform on which to build from or are there any other confirmed issues with Dlink lev 3 that need to be added so that they can get this router to work as advertised?
A. Router reboots when 2.4 GHz phone is in use and super g is enabled (level 3 acknowledges that a phone may knock out the wireless but should not reboot the entire router).
B. When router reboots, date and time are reset to April Fool's day 2002 and NTP doesn't work (level 3 acknowledges problem).
C.SMTP email logs don't work (level 3 acknowledges problem).
D.Some wireless clients won't auto connect to the network after a computer reboots (level 3 acknowledges this and thinks it may be a driver issue or OS issue).
E. When reloading the Saved Settings file, it does not remember the saved password for admin but resets it to "enter". On the 714p+ if you reload your Saved Settings (and it included a password) once the unit reboots you must relog in with that saved password, but this is not the case with the 624. (level 3 not sure if this is a bug or "new operation", been several weeks and I have gotten no update on this).
F. Enabling WPA-PSK won't allow some to connect to the network (I have not talk to Level 3 on this issue lately because once I install their dwl-g650/c2 and 3.17 driver, my wireless now connects to the network with WPA-PSK enabled).
G. Once a wireless connection is lost, a Rescan in Site Info won't reconnect the wireless client and the only consistent way most users can get reconnected is to reboot the computer (Level 3 is still investigating this, but no word back in over a week).
H. Some users are still having random rebooting with 2.37 although at a reduced frequency.
I. Some users are experiencing DHCP renewals as depicted in the 624 logs. |
|
| reply to SoCal99
A: No problems with older Panasonic 2.4GHz - none
D: Confirmed, this seems to depend on WPA vs. WEP and driver for G520 or G650. I also believe this to be a card driver issue, not a router issue.
G: Confirmed, Disable/Enable routine worked 100% of the time, but a pain in the butt to do. They have some serious issues to work out - especially with WPA. |
|
