how-to block ads
|
BillW2
@cable.rogers
| reply to Mookem
Re: DI-524 bios 1.05 disconnects
If you are experiencing disconnects on your "Wired" or "Wireless" connections, check windows "event viewer" to confirm if it is occuring every 34 minutes. You can get to event viewer via "Start | Programs | Administrative Tools | Event viewer".
If it is the 34 minute reset problem, you should be able to resolve it using any one of these 3 options:
1) Disable the wireless capability of the DLink router.
2) Downgrade to 1.03 firmware.
3) On your "Wired" nic, set the media type to "100mbps, full duplex". This is probably the best option of the 3 for most people since it has no negative impact.
From the testing I have done, here is what I believe to be the problem and reason.
I believe the problem is tied to a bug in the speed negotiation program logic of the 1.05 firmware. Even more specifically, I believe the bug is located in the unique portion of code that is used for handling the speed negotiations for the LAN side. The bug would have been introduced when they implemented the "Wan Select to 10/100 Mbps (ie. speed negotiation)" option in the 1.05 firmware.
Although the feature they were adding was dealing specifically with the WAN side of the router, it can be expected that both the WAN and LAN sides of the router share at least some portion of the Speed Negotation program logic. Hence, any changes they make to the speed negotiation logic on either side could have an impact on either side, such as in this case. Although some of the logic is shared, some of it would need be unique to each side to address the communication differences (ie. speed, media type, encryption, etc)
Here is what I believe to be happening:
When a device connects to the switched router, they negotiate and agree on the speed they will use to communicate. This negotiation process goes back and forth until the optimum speed is decided. Generally, the highest speed that they are both capable of performing becomes the agreed upon speed.
The router and broadband modem perform this negotiation successfully and connect. (Remember, the bug is located in the speed negotiation program logic unique to the LAN side.)
We hit the bug on the LAN side when the router runs it speed negotiation code for the LAN side (and wireless feature is enabled). The router & nics (wired or wireless) successfully negotiate the desired speed and a connection becomes established. But unfortunately, the buggy program logic traps the router into an endless circle of repeating negotiations. Ultimately, this leads to the router resetting itself after exactly 34 minutes (+/- 5 seconds). I suspect it is either an error trap or buffer overflow that forces the reset.
When this reset occurs, the router reboots, all connections are lost, and your wired/wireless PC experiences the disconnect. After 20 seconds, the router is back up and your devices attempt to reconnect....only to start the vicious cycle over again.
So, to resolve our problem, you need to prevent the router from running the LAN side's speed negotiation logic. We can do this by:
1) Disable the wireless side of the router. If wireless is not enabled, then the router will never try to negotiate a connection for the wireless LAN, therefore, it would never hit the bug that is believed to exist in the Speed Negotiation logic (ie. in the portion that is unique to handling speed negotiation for the LAN side).
2) Revert back to 1.03 firmware. The 1.03 firmware's speed negotiation logic was fine. It wasn't until they decided to add the user selectable "WAN Select to 10/100 Mbps" option (ie. which deals with speed negotiation) in firmware 1.05 that the bug was introduced. Unfortunately, going back to 1.03 will have you losing out on a few nice features/fixes that came with 1.05.
3) Force your wired nic to use a specific speed (ie. 100mbps full duplex). By forcing your nic to a specific speed, it becomes pointless for the router to negotiate speed. In effect, the NIC is offering the router a "Take-it or leave-it" proposition.....all it needs to do is accept (or decline) as their is nothing to negotiate.
4) Possible 4th Option: Upgrade to firmware 1.11 that the USA released for DLink 524 RevA1/2. However, please note their disclaimer that installing this on a canadian product will void warranty. I suspect it would not harm the router but haven't tried it yet. If you have, please share your experience as to if it damaged your router and/or if it fixed the 34 min disconnect issue.
Anyway, I hope this helps a few people out there.
Cheers
Bill | |
RayTech1
@xx.sea1
| I am yet another lucky fool  who got his hands on this yo yo wireless POS AP. I started with the shipped 1.05 had problems, upgraded the firmware to the online 1.05 and had problems, returned it to the store and got a new one and had problems, read online then rolled back to the 1.03 and lost Xbox live but it seemed more stable, emailed dlink techsupport and they had me jump throught he flaming hoops with no luck. I just noticed the 1.11 update for my 3 month old A1 hardware and will be trying it next. This AP has caused me much grief around my house as the internet always worked before with my Dlink 614+ until I brought this home and replaced the working Dlink B unit. I'll go ahead and paste the release notes from the 1.11 update as it is fun reading. Even more fun than not surfing the internet on the DLINK DI-524, I love it when I paid good money for a DI-524 and then my internet transaction gets lost cuz it drops my connection!
Tonight I saw a DI-624 for $16 after rebate at Fry's and I seriously considered buying it to replace my bogus DI-524. Then I wondered if the 624 has the same issues and thought that I should just spend the money on a Linksys instead.
Has anyone talked DLink into offering a replacement model? I don't want something for nothing but I do want it to just work already. I wish I was getting paid to troubleshoot this damn thing...
If you were able to get DLink understand that there are issues with this unit and replace it, what model did you get, is stable, and is it xbox compatible?
Product Name: DI-524
H/W version: A2
Release Note 03/11/2005
version 1.11b28
1.)Using wpa_1011 project from Kate's PC.
2.)Fix bug that Zone Alarm function can not work.
Product Name: DI-524
H/W version: A2
Release Note 02/25/2005
version 1.11b27
1.)Update to the latest code.
Product Name: DI-524
H/W version: A1
Release Note 02/25/2005
version 1.11b26
1.)Check WEP keys
Product Name: DI-524
H/W version: T1-1
Release Note 02/17/2005
version 1.10b24
1.}Change F/W date to 3, Feb 2005 build0024.
Release Note 02/03/2005
version 1.10b23
1.)Fixed bug no.2176 wizard wep key setting fail
2.)Fixed bug no.2181 Static DHCP fail
3.)STACK version: 1.0.0.1325, Jan, 20, 2005, Build 1325
Release Note 01/27/2005
version 1.10b22
1.)Fixed The function can't to edit or delete rules on Applications page
Release Note 01/26/2005
version 1.10b21
1.)Fixed bug No.2118 The function can't to add new rules on Applications page
Release Note 1/6/2005
version 1.10b20
1.)D-Link said change version to 1.10
2.)Fix Firewall rule list added new one rule about after 1 minute. The rule will disappear on firewall rule list.
Release Note 12/29/2004
version 4.00b19
1.)update tftpport.c ,add #ifdef _MARVELL_FLASH
Release Note 12/21/2004
version 4.00b19
1.)Dana said change version to 4.00
Release Note 12/21/2004
version 1.06b18
1.)Fix wpa can't show correct problem.
Release Note 12/14/2004
version 1.06b17
1.)Update Iniche No.1295 solve wpa & wpa-psk can't work problem.
Release Note 11/26/2004
version 1.06b16
1.)Fix cannot use wep key after showing Domain on Chklst.txt
Release Note 11/25/2004
version 1.06b15
1.)Fix cannot show Domain on Chklst.txt
Release Note 11/24/2004
version 1.06b14
1.)Support Netscape 7.1
2.)Iniche No.1276
Release Note 11/22/2004
version 1.06b13
1.)Modify status signal keep working
2.)Fix backup mode can't work
Release Note 11/05/2004
version 1.06b10
1.)Change webpage ZAP icon to ZoneAlerm icon
Product Name: DI-524
H/W version: A1
Release Note 10/28/2004
version 1.06b9
1.)Fix ZAP issue
Product Name: DI-524
H/W version: A1
Release Note 09/17/2004
version 1.06b7
1.)Fix Zap function fot user don't install Zap tool the webpage will redircet to port 8082
Product Name: DI-524
H/W version: A1
Release Note 09/17/2004
version 1.06b7
1.)Add ZAP text in help web
Product Name: DI-524
H/W version: A1
Release Note 09/17/2004
version 1.06b5 1.06b6
1.)For GST pre-test use
Product Name: DI-524
H/W version: A1
Release Note 09/09/2004
version 1.06b4
1.)1820 The range of Fragmentation is 256-2346, but it is okay to save when we wrote 2347.
2.)1859 Running Wizard cannot setup WEP function. Ex: enable WEP.
3.)1860 It have a word "DI-604" on DDNS explain page.
4.)1861 When pushed Tools / Misc. button, the functions button will display disorderly on this page.
5.)1862 It cannot set static DHCP IP address about Starting IP Address and Ending IP Address of DHCP Server range.
6.)1865 The UPNP function cannot work.
7.)1866 If the DHCP Client is empty, then push the Clone button on the Home/DHCP page. It will show wrong message. The test environment is IE 6.0 on Win2000.
Product Name: DI-524
H/W version: A1
Release Note 08/13/2004
version 1.06b3
1.)fix wireless wep function issue
Product Name: DI-524
H/W version: A1
Release Note 08/13/2004
version 1.06b1
1.)add function ZAP
2.)add cd router
Product Name: DI-524
H/W version: A1
Release Note 07/22/2004
version 1.05
1.)fix change page bug
Product Name: DI-524
H/W version: A1
Release Note 07/19/2004
version 1.05b13
1.)fix change page bug
Product Name: DI-524
H/W version: A1
Release Note 07/15/2004
version 1.05b10
1.)Change SSid Broadcast from advance\performance to wireless page
2.)take off authenciation from advance\performance page
3.)add time function in tools\time page
Product Name: DI-524
H/W version: A1
Release Note 07/09/2004
version 1.05b9
1.)fix Wireless to wireless in WEP mode can't ping each other .
Product Name: DI-524
H/W version: A1
Release Note 06/18/2004
version 1.05b8
1.)fix channel 1 to dwl-630 throughtput issue
2.)lan to wan throughtput issue
Release Note 06/04/2004
version 1.05b7
1.)fix wpa-psk page issue
2.)fix ssid 32 charachers issue
3.)Static DHCP issue
4.)Fix game "Asheron's call II" reboot issue
5.)Remove "trouble line from router code"
Release Note 06/03/2004
version 1.05b6
1.)fix wpa-psk 63 charachers issue
Release Note 05/27/2004
version 1.05b5
1.)fix 12K ping of deads
2.)add new function wireless enable/disable
3.)change iniche 1238
4.)Add Radio On/Off function
5.)Add WAN select Speed 10/100 Auto (default to 10Mbps)
6.)Predefined Virtual entries works, but when creating Custom entries using predefined port after rebooting or power cycling the gateway, the entries created in firewall rules will disappear. Recreating firewall entries resolves the problem.
Release Note 04/19/2004
version 1.05b4
1.)change advance page "DCS-1000" to "DCS-900/DCS-1000" "DVC-1000" to "i2eye "
2.)Add WPA function
3.)change iniche 1228
Release Note 04/19/2004
version 1.05b3
1.)fix ssid length issue
Release Note 04/19/2004
version 1.05b
1.)change the marvell lib for 1.80
2.)change iniche 1228
2.)Adding WPA function.
Release Note 02/23/2004
version 1.05
1.)change the lib for wi-fi test 02/23
2.)Adding the Wan select 10/100Mbps in tools\Misc.
Release Note 02/02/2004
version 1.04
1.)change the lib for wi-fi test
2.)Adding the Mode setting in advance\performance
Release Note 12/25/2003
version 1.03
1.)fix mfg-tool can't write in INTEL flash issue
2.)fix wireless page when double click wireless button the page will break issue
Release Note 12/25/2003
version 1.02
1.)fix mfg can't erease data issue
2.)Check sum number 05781081h
Release Note 12/18/2003
version 1.02
1.)change header figure PLUS color bule to red
Release Note 12/11/2003
version 1.01
1.)use the lib with no dcache
2.)fix the WPA-PSK function fail
3.)fix the DNS keep issue
4.)take off the wireless help page WEP support 256 bit and 3 layer
5.)fix the port range can setting 0 issue
Release Note 12/05/2003
version 1.00b3
1.)Take off 22 mbps
2.)fix key type bug
3.)fix port range bug
4.)reduce local domain name to 20 characters
5.)take off help wireless page reset and refresh button scriptation
6.)fix WPA-PSK function
7.)reduce throught to use no-cache lib
Release Note 11/20/2003
version 1.00b3
1.)update iniche
2.)fix virtual server schedule function
3.)fix wep key function
4.)fix wizard function 256 bit
5.)fix wizard setup pic to di-524
6.)fix local domain name 20 characters
7.)fix lan setting di-514 to di-524
8.)fix reserved ip GUI
9.)fix wireless client list
10.)fix status page packets value always 0
11.)fix huge packet pinging
12.)fix wpa function
13.)fix tx-rate setting
14.)fix logo display
Release Note 11/20/2003
version 1.00b2
1.)Fix all the DI-514 to DI-524.
2.)Fix the wizard wep key 256 bit.
3.)Tx-rate use option.
4.)Fix ping huge packet will crash bug.
5.)fix must choose authentication bug.
6.)synchronization adv_form.html and h_wireless.html radio button.
Release Note 11/13/2003
version 1.00
1.)Library use Dcache turn on.
2.)Adding function WPA-PSK | |
laserfan
join:2005-01-14
Blanco, TX
| reply to BillW2
said by BillW2:
If you are experiencing disconnects on your "Wired" or "Wireless" connections...
3) Force your wired nic to use a specific speed (ie. 100mbps full duplex)... I know this is an old thread, but my brand-new DI-524 was giving me fits until I did some surfing and found this tip.
My router has only been "up" for about 4.5hours now, but this is such a huge improvement over what it was doing before that I am delighted & think the problem may be fixed. I was faced with sending it back to the retailer.
For the record, the DI-524 that was previously re-setting frequently is a RevC, 3.02 firmware unit, with 2 hardwire connections, no WAN, and a single wireless-G client using "Static DHCP". As BillW2 said in his original post "hopes this helps someone". Bill it sure helped me! Thanks! | |
laserfan
join:2005-01-14
Blanco, TX
| Well, although the number of resets has been greatly reduced, my DI-524 RevC fw3.02 still does reset itself about once a day. I had taken the cover off also to see if heat was a problem.
Anyway I'm going to return it to the retailer, and probably NOT buy another because I have a nagging doubt about it.
I do like D-Link's "Static DHCP" feature and hope I can find another wireless AP with that... | |
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
 ·Verizon Online DSL
 ·Skype
| said by laserfan  :I do like D-Link's "Static DHCP" feature and hope I can find another wireless AP with that... It is a common feature these days. You can also run a software DHCP server, or you can set up the server machine with a static address (where it never asks for DHCP since it is preconfigured).
--
Robb Topolski  http://www.funchords.com/  Hillsboro, Oregon USA
Dear Anonymous, Thank you!!! Thank you!!! | |
laserfan
join:2005-01-14
Blanco, TX
| Robb as you have followed this thread, I wanted to add that AFTER I got an RMA to send-back my brand-new DI-524 (buy.com) for its random resets, it occurred to me that: maybe the 524, wired & used as an access point only (no WAN connection) should never have been asked to issue "Static DHCP" at all to my wireless client? My main WAN gateway/router is a Linksys, and altho I have DHCP disabled on the Linky, maybe I should never have asked the 524 to issue IPs? Then again even w/all Log options selected, there was nothing in the log to suggest any problem.
OK so I disabled DHCP completely on the 524, then set the Linky to DHCP an IP to my wireless client (via the 524 I mean of course) and while it worked fine I didn't leave it "up" in this configuration long enough to see if I got any further resets. I'd already bought a new AP today and was anxious to set it up in the 524's place.
This is my final nagging thought about this--I hate to give-up on a product, but I'll be sending the 524 back anyway without doing any more testing.  | |
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
·Verizon Online DSL
·Skype
| said by laserfan :Robb as you have followed this thread, I wanted to add that AFTER I got an RMA to send-back my brand-new DI-524 (buy.com) for its random resets, it occurred to me that: maybe the 524, wired & used as an access point only (no WAN connection) should never have been asked to issue "Static DHCP" at all to my wireless client? That's true. DHCP should have been off -- issuing no dynamic or static IPs.
The log would not have picked this up.
--
Robb Topolski http://www.funchords.com/ Hillsboro, Oregon USA
Dear Anonymous, Thank you!!! Thank you!!! | |
|
