Talon88
The One
join:2003-08-13
Toronto
 ·Bell Sympatico
| reply to chrisodin
Re: DI-624 Firmware update w/ Crash Recovery Step
[Step 6]
After loading the firmware, perform a "Hard Reset"
by pressing the [Reset] button at least 12 sec.
This ensures that the firmware is locked in.
You should Now see the Normal Router Config Page.
[Step 6.1]
Exit IE6
[Step 6.2]
You can Set back your computer to Auto DHCP
[Step 6.3]
Run IE6 Again
Go [Step 7]
--
[=Talon88=] |
|
ANoni
@cox.net
| I must add:
Each time a crash recovery is done the NIC needs to be locked at 10 Half duplex and a static IP out of the DHCP range of the router. WHy people give PCs a static IP in the DHCP range?? Sure it will work, I will not argue that, but in the future IP conflicts can occur...
Just my 2 cents... |
|
Amnon
@bezeqint.net
|  reply to chrisodin
Are you on 2.50? 2.50 seemed to have done reboots every 5-30 minutes for me on PPPoE, although it seems that if I configured it to DHCP it wouldn't connect to my DSL (I know that it can't, I just did that to try and isolate the change from my Cable connection to DSL) but also wouldn't reboot.
When it was configured for PPPoE on 2.50 even if no computer access was done it would reboot (during the night, no access, MAC filtered, log shows restart).
I downgraded to 2.42 in the normal way (no crash recovery) and reconfigured everything.
Now I am at 1:40 and still no reboot.
Any insight? |
|
Amnon
@bezeqint.net
| 2:10 hours  2.42 with exactly the same configuration (manually performed) as 2.50 which constantly rebooted every 5-30 minutes.
Hopefully it will stay that way.
Has anyone ever proved that updating the firmware in the normal way yields different results than crash recovery? And I don't mean coincidental evidence, but bit by bit comparison of ROM or configuration? |
|
Amnon
@bezeqint.net
| :-( 2:35 and a reboot...
This reminds me that a 2.4GHz digital Panasonic phone made my connection go away...
I now disabled Super mode (as I don't have use for it at this point) to see if it will prevent the reboots.
If it works with 2.42 over night I will try 2.50 again.
Does that sound like a plan to you guys? Is it usually necessary to disable Super mode completely or just set it to Super mode with no Turbo?
Thanks! |
|
Pla
join:2004-02-25
Sunnyvale, CA | Just set it to supuer G without turbo. It greatly reduces the reboots. |
|
Amnon
@bezeqint.net | It rebooted once in 8 hours which I can live with.
Should I try 2.50 with the same setup?
Amnon |
|
Talon88
The One
join:2003-08-13
Toronto | Yes, Try Follow my step & maybe you will
gave 16 hrs ar more.....! (Don't Skip)
--
[=Talon88=] |
|
speedlever
join:2003-11-30
High Point, NC
| reply to cannot get into web
I seem to recall having a similar problem working on my brother-in-law's 624 one time. I'm trying to remember what I did to fix it.. but my memory is failing me.
1) terminate any firewall you're running (disconnect any online connection (cable/dsl) first)
2) make sure you set a static IP address
3) if you use MAC filtering, make sure your first filter covers the wired PC connected to the router.
Hopefully that will get you started.
Wish I could remember what I ran into and how I fixed it, but I recall that I was having trouble entering variables in the router setup pages and it finally locked up and wouldn't let me in to do anything.
I find that once I get a stable configuration and don't mess with things for a long time that I forget some of the finer details of setting up/managing a wireless network.  |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL
·AT&T Midwest
| Hey Talon -
You seem to know much more than most about these bloody 624s. I've more or less had it with mine - I'm back on the Netgear 614. The 624, after working fine for a while with the 6.50 firmware is now dropping various machines off the LAN daily, and doing other goofy stuff.
I'd like to convert the thing into an adaptor (I need another one for one of the desktops anyhow) if it'll let me. Is the 624 convertible? Does it have anything akin to a "client mode" or are there any settings that will allow me to use the thing as an adaptor?
Thanks! |
|
Chimmy3
join:2004-09-24
Rosedale, NY | the router can;t be turned into a wireless client. The best you can do is make it a wireless Access point. |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL | reply to Talon88
Re: DI-624 Firmware update w/ Crash Recovery Step by S
Damn! Thaks for the info... |
|
Cthen
join:2004-08-01
Ypsilanti, MI
 ·Comcast
| reply to Talon88
After being trolled in another thread with this fix I decided to let some time go by and monitor this post. Im still trying to find the "Many successful story" that I was getting trolled with in this thread: »[Help Me] SP2 and DWL G520 / DI624
I see 1 success but thats about it while the rest still report reboots and disconnects. Funny, I get 0 reboots and 0 disconnects on my setup. Why were you trying to cram this fix down my throat again? A good rule of thumb in support is: Dont try to force support on someone who doesnt need it |
|
Soulfish7
@verizon.net
| reply to Talon88
Re: DI-624 Firmware update w/ Crash Recovery Step
I've had this same rebooting problem with my DI-624 Rev C for a couple of months. The odd thing is that it only seems to happen when I'm using my wired PC. It almost never occurs when I'm on my laptop. I've tried setting the ethernet card at 10MB half duplex, as suggested by D-Link, but that hasn't helped. The card is probably 4 years old. Any chance it may be the card itself in my case and not the router? Just a thought. Cards are a lot cheaper than a new router. I've got FW 2.50 and tried the crash recovery process, but am still getting the reboots. Any help is appreciated. |
|
Tsume
join:2004-02-23
Johnson City, TN
·Embarq
 ·ViaTalk
·Comcast
| reply to Talon88
The steps listed are great and usually DO help. However, the most thorough way of getting a new firmware in and getting an old firmware out (also the way that requires the most work) is to restore factory defaults, do a normal firmware upgrade through router's firmware page, follow Talon88's instructions step-by-step for factory recover firmware but after doing the final restore factory defaults do NOT put your own settings in, then do a normal firmware upgrade AGAIN, restore factory defaults AGAIN, and then put your settings in.
The most problamatic settings with frequent (as in more than two a day) are UPNP [under Advanced > MISC] and Super-G [On newer firmware ver's, under HOME > Wireless]. Turn UPNP OFF as it is a retarded setting that is just a big security hole anyway, and DISABLE Super-G alltogether if you still get reboots frequently. It is better than just turning off the turbo but leaving Super-G on.
I'll take a look at your thread to see what I can suggest, and in the mean time please, make sure you have followed my thorough way of firmware upgrading to upgrade to either 2.50 avaliable on D-Link's US support site, or 2.52b37 avaliable on D-Link's AUSTRALIA support site. |
|
Tsume
join:2004-02-23
Johnson City, TN | Well from what I have seen, it looks like Talon was just trying to keep you up to date and such... 2.42 has some bugs [which someone could potentially exploit to take over your router and give them internet access]. |
|
dscline
join:2001-09-01
Atlanta, GA
| reply to Tsume
said by Tsume  :DISABLE Super-G alltogether if you still get reboots frequently Unfortunately, in doing so, you remove the only real advantage this router has over other more reliable models. |
|
Tsume
join:2004-02-23
Johnson City, TN
·Embarq
·ViaTalk
·Comcast
| This is for people who realized the router was a P.O.S. AFTER the deadline of RMA'ing or returning it. It's better to have a working router than one that has 'turbo' which is slower than regular 'g' for me anyway [5 hours to copy a cd image over wireless VS 20 minutes or less with standard g... turbo my a**]. |
|
srobak
@comcast.net
| Firmware punts do not solve the issue with this router.
I bought mine new about 4 months ago. Has been working fantastic, frequently pulling down a full 3Gb in downloads and gaming from my ISP.
3 days ago, I started getting random disconnects. At first, I thought my computer was horked... but then my wife's laptop started dropping signal and then getting it right back. Then all my computers plugged into the router were receiving hardware errors when doing endless pings against the router about every 20 or 30 pings. Got constant notifications that my cable was unplugged.
After getting pissed off at constantly getting kicked out of Counterstrike on one computer, getting kicked off of MSN Messenger and dumping my Kazaa downloads on another, and my wife losing her wireless (non-turbo, B mode only!), and nearly destroying it as I ripped it off the shelf in frustration and sent it flying to the floor, snapping cables and pulling RJ-45's clean off...
I decided to open the cover - initially to see if it had been damaged in my exercised displeasure. It hadn't - but I began to get curious about an over-heating problem once I saw that the case has virtually NO ventilation. So - I screwed the board back into the base and set it on the shelf without the cover and hooked everything up. I have been running it for over a day, full speed - 2x wireless connections, Kazaa pulling a steady 1.5 to 2 Mb, and Counter-strike raging....
Oh - and on firmware 2.42. With all the problems that people have reported with the newer firmware in this thread, I would recommend NOT upgrading to it. Found the same case with the old 614 a couple years back too.
From all the other threads I have read about this router on the internet, and my own proven experience - it is a thermal problem and not a firmware problem. I like the fan-job that one guy did... everyone should do that, or just remove the lid. You WILL notice a marked improvement. |
|
jonazen
Be Like Water My Friend
Premium
join:2004-02-18
Princeton Junction, NJ
·T-Mobile VoIP
| @srobak -
Interesting that so many of us started having problems in the same time frame. Massive coincidence??? I think not.
Based on my experience, yours and other posts, I'm wondering about something here. A few of us noticed that the connection seemed "stronger" and "faster" after upgrading firmware over the last several weeks.
A few people noted that the router works better if they fall back to earlier versions.
You and a few others are convinced that there's a thermal problem. If so...why would it suddenly start rearing its head NOW, and never over the last several months of use?
Why...unless the firmware upgrades, which appear to increase signal strength (?), somehow causes the router to run hotter???
So...if that's the case, if we figure out how to put reasonable fans on the device, then perhaps we can continue to use the latest firmware?
Weird -- I feel like we're talking about becoming "Router Over-Clockers"...
--
Jon
Jonathan Strong
The Strong Group, Inc.
|
|
