D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: boldt on March 12, 2009, 09:37:11 AM
-
I have seen numerous posts on the "Wireless Restart" topic and many proposed solutions from:
- Downgrading firmware to 1.11
Forcing a wireless channel
Forcing a transmission rate
Forcing a channel width
Changing transmit power
Changing fragmentation thresholds
disabling WISH
and removing all wirelss security
Oh, and then changing the SSID after each change (forcing a new profile on clients)
I have even gone so far to get an RMA on one of these DIR-655 just to have it replaced with one that does the EXACT same thing!
based on the positive reviews on the DIR-655, one of two things is happening:
1) my DLINK luck is bad and I have gotten 2 duds in a row
2) this problem is a lot more widespread and either others are just not noticing it, or are willing to accept the constant wireless restarts
I can honestly say that I am about done with this unit, and quite honestly DLINK all together (their support is borderline abysmal).
However before I give up, and I really don't do this easily, I wanted to inquire one last time if anyone has a working solution AND if DLINK is even admitting there is an issue and planning to do something about it?
I look forward to hearing back from you all!
-
If your unit is failing and a replacement is exhibiting the exact same behavior, that tells us that it's not a problem with the product, it's a problem with that SPECIFIC product in your environment.
That being said, have you tried any of the suggestions you listed?
Have you checked the environment for 2.4ghz cordless devices?
Are there many other wireless networks in your house?
-
Lycan, yes you are correct, there could a another explanation. However as much as I would like to agree with you I have my doubts at this point especially with the apparent number of users out there with similar issues.
To the best of my knowledge there are no other 2.4ghz devices in my home, but do have a 5 GHZ cordless phone in the house. Will netstumbler smell the 2.4 ghz rainbow for interference? I have to admit that its been a long time since I sniffed the air to see whats there. But I will when I return home.
Yes I have tried every single one of those suggestions below to no avail. However I would like to ask what the recommended values should be on those settings?
In fact I recently downgraded to firmware 1.11 and although I do not get the wireless restarts in the log any longer, its far worse now because my clients drop off and now I have to manually reconnect every time.
Since I have seen you posting on many of these wireless restart postings, do you know why DLINK is not putting anything more helpful in the logs as to what may be the root cause of this issue? Is there beta firmware, or even 3rd party, that may be able to help identify the culprit?
Perhaps all these recommended settings and things to try (in a logical sequential order) should be compiled and a "sticky" created? just a thought.
-
It would appear that there are a great many people with failing units on these forums, thats because people with working units hardly find forums to brag about how well their device is working.
Along those lines, lets say that there are 100 people on these forums complaining about their units failing, and we sell 10,000 units in a month, thats less then 1% of failing units.
Now, those numbers are drastically under-estimated.
This doesn't mean that we don't care about the people that are suffering from these failings, or that we don't want to help. What it does mean is sometimes there isn't anything that can be done to correct the issue with that model and that a different unit (e.g. rev or different model altogether), will rectify the situation.
-
Yes indeed, and agree whole heartedly. I also work in the tech support world and rarely do we ever hear praise, just complaints when things are not working correctly.
With that said, I would like turn my negative experience (so far) into a positive one if possible. I still feel that assembling a list of things to try, and the order in which to try them in, would be the most logical (and helpful) thing to do.
-Remove all wireless security (do the wireless restarts continue?)
-Use Netstumbler to determine if there is interference by other wireless devices
-Forcing a wireless channel (start at channel 1 and work your way up to 11, until you find a channel that works)
-Forcing a transmission rate (????)
-Forcing a channel width (????)
-Changing transmit power (????)
-Changing fragmentation thresholds (????)
-Disable WISH
-Downgrade to firmware 1.11
Could/would you fill in the gaps above with your suggestions, as well as add additional steps from your experience that should be listed?
I would also invite, and encourage, anyone else that has found a solution to their wireless restart issue to contribute with their solution.
Thank you!
-
Just to also post my experience as this wireless restart. This seems to not limited to the DIR-655 models. I have a DIR-615 (B2) which does the exact same problem. Whenever the wireless network is enabled, the router would randomly reboot. Test all the available firmwares and changed the environment in hopes to clean up the interference that could possibly exist. I even move the unit to a different building (Kms or miles away from my home.) Nothing would let the 615 wireless network to work correctly.
However, with the wireless "disabled," the router works well as wired Ethernet LAN router.
I am now 'experimenting' with a Dual-band DIR-628.
-
A couple of things I've found in my 'odd ball' environment that may apply to yours as well:
1. Wii (deactiveate 24Connect). This is a problem with Wii, not the router.
2. QOS Engine. Deactivate Automatic Uplink Speed. Set to reasonable speed (e.g., 256kbps)
3. Wireless Setup: Deactivate Auto Channel Scan. Start with channel 11 and work down until disconnects cease to occur. Give each channel a day or two. With a cordless phone, bluetooth wii controllers, bluetooth cell phone, and a microwave oven -- i've had good luck with this set-up.
I've got a road runner cable modem (scientifi atlanta) coming into the DIR655. From that i set our VoIP box with a fixed IP (199) and left the other devices (2 notebooks, a desktop, a server, a PS3, and a Yamaha net radio) to use DHCP.
Our DIR655 is hardware v4.
If this doesn't help you, try the beta firmware v1.22 available at the top of this forum.
Good luck & cheers!
-
I have set up a ton of these routers in my job for clients. Only one time have I ever seen rebooting problems, but boy oh boy was it rebooting! ;D Anyway, for this client the fix oddly enough was another brand of cable modem. Strange I know, but the original modem that they had would make the router reboot randomly, once the modem was switched for a new one of another brand it worked perfectly.
I cannot remember the brand that did not work, but it was replaced by a Motorola and it worked fine. I would not even think that this was possible if I had not seen it, but it is an example of how hard these problems can be to track down. I have never had the first issue with my DIR-655 and it is easily the best router I have ever had. I use and setup tons of different brands and d-link is now my favorite "high end" home router. I honestly do not care for the low end stuff, but the high end product is great and gives me no problems in my installations. It still might not be the router for you though, but I hope you can track down your issue. What you are doing is on the right track, hope you can get it figured out.
-
I have set up a ton of these routers in my job for clients. Only one time have I ever seen rebooting problems, but boy oh boy was it rebooting! ;D Anyway, for this client the fix oddly enough was another brand of cable modem. Strange I know, but the original modem that they had would make the router reboot randomly, once the modem was switched for a new one of another brand it worked perfectly.
I cannot remember the brand that did not work, but it was replaced by a Motorola and it worked fine. I would not even think that this was possible if I had not seen it, but it is an example of how hard these problems can be to track down. I have never had the first issue with my DIR-655 and it is easily the best router I have ever had. I use and setup tons of different brands and d-link is now my favorite "high end" home router. I honestly do not care for the low end stuff, but the high end product is great and gives me no problems in my installations. It still might not be the router for you though, but I hope you can track down your issue. What you are doing is on the right track, hope you can get it figured out.
Nobody believes me at first, but there a quite some cable modems causing issue with routers. I've seen more errors caused by modems and the client PC's than specific router issues. ;D
-
Things to do:
Setup is done with a wired connection. Just trust me on this. Besides, when you wipe your old config, the wireless will shut down - so get the router next to your box with a network jack on it (they all do these days) and plug it in.
1) Upgrade to the current RELEASE firmware. Avoid betas, etc. Let's get you on a known commodity. 1.21 was the current version when I wrote this.
2) HARD reset the router. See the manual or support pages for the procedure. Afterwards, DO NOT import your old configuration - build a new one.
3) Set ONLY the features you need to have on.
4) Wireless settings:
Enable it, Always, and name it first. Don't leave it dlink, and don't name it after your last name, address, etc - nothing to personally identify YOU from IT. Name it something meaningful to you but impossible to associate. Now, set the rest of your stuff:
a)802.11 mode - mixed
b)Auto channel scan - OFF
c)Wireless channel - This will take some research on your part. 6 is the midpoint and typically the "sweet spot" in the band. It's also where every bloody router starts looking. What I did is turn the router OFF, then use my CLIENT machines to look to see what networks were out there. I didn't bother using netstumbler - I used the Dlink configuration utility (turning off windows management of the wireless to do so), and scanned the world a few times. In my case, 6 turned out to be open. Yours it might not. Avoid using the extreme ends of the band (channels 1 and 11). Channels 5-8 typically seem to work the best and avoid interference, but YMMV.
d)Transmit rate - Auto (Best)
e)Channel width - 20 MHz. Yes, I realize this is going to slow some of you down. But especially in a mixed-adapter environment where not all of your adapters are Dlink (laptop built-in cards aren't), I've found greater stability by dropping that width down. Working connection > fast but dropping one. Besides, how many of you actually have a connection capable of sustaining 300 Mbps on the internet? :)
f)Visibility status - While you're setting up, leave it visible. Once you're done? Turn it off for security purposes.
Security mode - None is a bad idea. Very bad. WEP is about 1 footstep above None. Don't use these if you can avoid it, but WEP is STILL better than None if your old card that you refuse to upgrade doesn't support WPA.
The option for you is WPA Personal. If you're in an enterprise environment and have a working Radius authentication server, chances are pretty high you aren't using this product in your network anyway.
WPA mode - Auto
Cipher - TKIP/AES
Update interval - 3600s
PSK (Pre-shared key) - set as desired. It's a password - make it something easy to remember, hard to guess, not found in the dictionary, and avoid anything that a hacker can socially engineer by digging through your garbage cans.
The setup for the rest of your pages - leave at STOCK values for now. Don't set up virtuals, etc - leave them alone. Save your configuration. Make sure you've set a password for the admin account. Now, unplug the router, unplug your cable modem/DSL modem/etc. Wait 30s to 1m. Plug in the modem, let it finish sync'ing. Now plug in the router.
I found that the best wireless performance came from having the router set up vertically with the antennas pointing up, straight out, and down (from top-bottom) - but your environment may differ and your coverage pattern certainly does, so adjust those as needed to maximize your own performance.
Once the ROUTER is done and online, unplug the WIRED connection, and set up the WIRELESS on the CLIENT end using the information you specified on the router.
Once you set up your clients, restart EVERYTHING. Powercycle the router, then turn all of your clients on and make sure they ALL connect. Now, for the hard part: Go look for the end of the internet. See if you can find it. And if you have any resets, go into the logs and copy everything you see from the router log and post it up - the answer might be there.
-
Shaith, nicely done! I am sure that this will be of immense value to others looking for a place to start troubleshooting these errors.
I can tell you that I have followed your advice to a "T", and unfortunately my wireless restarts remain.
Update on my wireless restarts:
-I updated to BETA 1.22 and its no better
-I happen to have a WII, and I have a wired adapter for it, and thought that aquanut was onto something with the WIICONNECT24, I never turned it off! well I did and the problem remains.
Unfortunately netstumbler did not work with my wireless adapter so I am hunting for a laptop/wireless card that is compatible so I can sniff the air for some interference.
-
I would go to beta 1.22b05 (big difference over the other betas in my experience),
and then I would begin disabling everything on the router bit by bit until it stopped restarting/rebooting.
Im not a big wireless user but it seems to me from what I've read here certain A models of this router have more problems with this than others ... what were yours or did I miss that?
When I say disable things I don't just mean wireless. I mean everything. Because the exercise is to find out if the router can be stable in SOME kind of configuration. So that includes such things as DNS proxying/forwarding , QOS, SPI, automatic time setting, etcetera.
And then make your wireless config as simple as possibe .. disable WISH, WMM, etcera.
If you are absolutely ruthless and thorough you'll at least have a better idea if it can be fixed via configuration. Once you know that, if both hardware versions were the same maybe you can get a different version.
Cory
Eddie: If a router reboots/disconnects "because of" the modem/PC/etc that is the routers fault not the other device. I'll agree however with the general principle that ... problems can be misdiagnosed as being with the router in lots of cases.
-
I am running A3 with 1.22 (b05)
* unfortunately I never noted the hardware version of the first one that I had RMA'd
bluenote - I am being as thorough (absolutely ruthless :-))as I possibly can here. Not only that but I am trying to keep track of what exactly I am doing so that other's might benefit from my ruthlessness.
A side note, and one that I probably neglected before, was that I am simply using the DIR-655 as an AP and a GB switch. This decreases the complexity of the config quite a bit.
Updated:
I just went back and looked at some other threads on this wireless restart subject and noted this post from EddieZ:
Get the 1.22 beta firmware. If the issue persists we can solve it, but 1.21 is too unstable to put in a lot of effort.
EddieZ - as indicated I am now running 1.22 and still have the issue. What did you mean by we can solve it? is there something I am missing in the logs perhaps that is providing some additional insight to these restarts?
-
Try this: Use DHCP reservation (static IP for LAN clients). Seems to work with some of these restart issues
-
I have the DHCP turned off on the DLINK. I actually run Windows SBS and use it for most network services.
I truly just have it configured as an AP with a GB switch.
-
I have my DHCP enabled but chose to make my wireless laptop static IP thru the software on the router. This seems to have helped from dropping the wireless signal.
My wireless problem that I have noticed is when I am trying to connect and stay connected remotely to my wireless notebook thru my desktop. Maybe tech support needs to fix the DHCP issue, I never had problems with my linksys router. I had bought a dir-615 router for another location and it disconnected really bad to the point that I could not rely on it and tech support could not help, so I ended up taking it back and purchasing another brand. I don't want to do this with my dir-655.
-
rcschaff, thanks for the input.
While I am tempted to try your suggestion i would like to know why on earth would the WAP care what IP a client was using, let alone needing it to be assigned an IP by the WAP. The DHCP scope I am using has a 8 day lease which means that clients are not going to perform DHCP requests for 4 days. so there should be no broadcasts most of the time (if the DHCP broadcast traffic is the culprit)
However, in the interest of trying everything I will assign a static IP via the WAP and see if it corrects the issue.
It is extremely disappointing that there seem to be a decent number of owners with this problem, and there does not seem to be a fix or even a log entry describing what the issue might be.
I have to admit that I would like to know if there IS a solution to the problem? will tweaking these settings ever result in a stable wireless environment, or is this a lost cause? and if so is this a result of some interference that is difficult to detect, or is this due to a hardware bug that is just not widespread?
I have a few days left on my 30 day return policy and would really like to be of the majority that loves this device.
If anyone else has any thoughts or suggestions, of even had this issue with a previous unit, please let me know! At this point I am grasping at straws to see if I should cut my loses and pick a different unit.
-
I am having the same issue with my dir-655, although with the beta firmware installed it seems to be dropping the wireless less than before. My linksys router never had that issue. I use remote desktop a lot for my systems and it is very time consuming when I have to re-connect my desktop sessions.
-
INFO] Mon Mar 16 10:00:27 2009 xxxx-router: Wireless system with MAC address 002191FB9490 disconnected for reason: Received Deauthentication
[INFO] Mon Mar 16 10:00:24 2009 xxxx-router: Wireless system with MAC address 002191FB9490 secured and linked
[INFO] Mon Mar 16 10:00:24 2009 xxxx-router: Wireless system with MAC address 002191FB9490 associated
-
Are you running 802.11N?
-
I am running mixed (B, G & N)
-
i think that it is interesting that you are showing a de-authentication issue on one of your clients.
In my case I am not showing anything other than this repeated OVER AND OVER again in my logs:
[INFO] Mon Mar 16 12:00:56 2009 Above message repeated 1 times
[INFO] Mon Mar 16 12:00:53 2009 Wireless link is up
[INFO] Mon Mar 16 12:00:42 2009 Wireless link is down
[INFO] Mon Mar 16 12:00:42 2009 Wireless restart
[INFO] Mon Mar 16 12:00:42 2009 Disconnect all stations
[INFO] Mon Mar 16 12:00:42 2009 All Wireless shut down
[INFO] Mon Mar 16 12:00:40 2009 Wireless restart
[INFO] Mon Mar 16 12:00:35 2009 Above message repeated 2 times
[INFO] Mon Mar 16 11:53:27 2009 XXXXX: Wireless system with MAC address 001D0FB22CFC secured and linked
[INFO] Mon Mar 16 11:53:27 2009 XXXXX: Wireless system with MAC address 001D0FB22CFC associated
[INFO] Mon Mar 16 11:53:27 2009 Above message repeated 1 times
[INFO] Mon Mar 16 11:53:24 2009 Wireless link is up
[INFO] Mon Mar 16 11:53:13 2009 Wireless link is down
[INFO] Mon Mar 16 11:53:13 2009 Wireless restart
[INFO] Mon Mar 16 11:53:13 2009 Disconnect all stations
[INFO] Mon Mar 16 11:53:13 2009 All Wireless shut down
[INFO] Mon Mar 16 11:53:11 2009 Wireless restart
[INFO] Mon Mar 16 11:46:14 2009 XXXXX: Wireless system with MAC address 001D0FB22CFC secured and linked
[INFO] Mon Mar 16 11:46:14 2009 XXXXX: Wireless system with MAC address 001D0FB22CFC associated
-
If you disable N support, does this behavior continue?
-
I just changed to mixed G & B. I'll report back in a few.
-
I regret to inform that within minutes of adjusting the wireless to mixed B/G only my resets returned:
[INFO] Mon Mar 16 12:52:43 2009 XXXXXXXX: Wireless system with MAC address 001D0FB22CFC secured and linked
[INFO] Mon Mar 16 12:52:43 2009 XXXXXXXX: Wireless system with MAC address 001D0FB22CFC associated
[INFO] Mon Mar 16 12:52:43 2009 Above message repeated 1 times
[INFO] Mon Mar 16 12:52:36 2009 Wireless link is up
[INFO] Mon Mar 16 12:52:26 2009 Wireless link is down
[INFO] Mon Mar 16 12:52:25 2009 Wireless restart
[INFO] Mon Mar 16 12:52:25 2009 Disconnect all stations
[INFO] Mon Mar 16 12:52:25 2009 All Wireless shut down
[INFO] Mon Mar 16 12:52:23 2009 Wireless restart
[INFO] Mon Mar 16 12:46:03 2009 Log viewed by IP address 192.168.1.3
-
Are there many other wireless networks in the area? How about cordless phones?
-
I do show 3-4 other wireless networks in the area (I live in a close nit neighborhood).
I also have a 5.8 digital cordless phone. I can only imagine that the neighbors also have cordless phones utilizing varying frequencies.
How would one determine if there was interference from one of these other wireless sources is causing these wireless restarts? and if so isolating the one that is causing the issue?
This is not the first Wireless AP that has been in this same spot in my house, just the first one that keeps having a wireless restart issue.
-
Tried different channels (manually)?
-
use netstumbler and see what channels are currently being used.
-
I wishes nestumber worked with the dwa-160. :(
-
You might want to try inSSIDer instead.
-
yeah, I had to borrow a laptop last night to run the netstumbler test (I wish it ran on an Intel 5300!). I digress, there were a LOT more networks then I remember seeing last time, but there were still quite a few openfrequencies/channels.
Here were the frequencies in use last night:
1,6,8,9,10,11
So I set my DIR-655 to "wireless channel" 4 (I thought a good one right in the hole of open freq) last night before I crashed:
The phrase "[INFO] Wireless restart" entry appears in the log file 1718 times since the time I changed the frequency to 4 and now!
[INFO] Tue Mar 17 15:38:45 2009 Above message repeated 1 times
[INFO] Tue Mar 17 15:38:37 2009 Wireless link is up
[INFO] Tue Mar 17 15:38:27 2009 Wireless link is down
[INFO] Tue Mar 17 15:38:26 2009 Wireless restart
[INFO] Tue Mar 17 15:38:26 2009 Disconnect all stations
[INFO] Tue Mar 17 15:38:26 2009 All Wireless shut down
[INFO] Tue Mar 17 15:38:24 2009 Wireless restart
Anyone else have any thoughts or suggestions?
-
You are running 1.22 but is it the latest beta? (b05)
I don't know that that beta is any better for wireless, but it was a lot better for several other bugs I was experiencing so its worth a try.
The only thing I can think to suggest at this point is to simplify the wireless to just one device for a bit and see what happens. (aside from simplifying the wireless config as much as possible which I assume you have already done) ... ie: play the disable everything game
Cory
-
yes I am running 1.22 b05.
I have to admit that I am running out of things to try, options and patience.
I have restored my antique Linksys WAP back into production for the time being.
I suppose that after going through two of these units, that I will have to blame my environment for these issues. It would be nice however if there was something in the logs that provided some sort of clue as to the reasons for these restarts!?!?!
If anyone has any other suggestions on other things to try please let me know.
-
boldt,
I have had the same wireless restart issues that you are seeing. I found that when I changed the Transmit Power from High to Medium or Low, the restarts went away. My guess is that the receiver is either susceptible to reflections (which would have a higher amplitude on the High setting) and the geometry of my environment is producing an above average number OR there is an elevated internal noise level with the transmitter at full power that is hammering the receiver.
I don't think I have had any wireless restarts since setting the Transmit Power to Low.
- Mike
-
I've given up. I just don't have the time to work my poor piece of equipment (A2 model). My DIR-655 kept "freezing" and I had to turn it off and on again throughout the day. When I called support, we proceeded to turn down performance (e.g. gigabit transmit rate...or something like that down to 10 mbps). This stopped the problem for a while but it started cropping up again. Hoping the new Cisco/Linksys works now (although I hear it too has had a rash of overheating problems).
Sometime I think there is room for a premium vendor that just gets things right - maybe not the first to market but when they release...it works.
-
I've given up. I just don't have the time to work my poor piece of equipment (A2 model). My DIR-655 kept "freezing" and I had to turn it off and on again throughout the day. When I called support, we proceeded to turn down performance (e.g. gigabit transmit rate...or something like that down to 10 mbps). This stopped the problem for a while but it started cropping up again. Hoping the new Cisco/Linksys works now (although I hear it too has had a rash of overheating problems).
Sometime I think there is room for a premium vendor that just gets things right - maybe not the first to market but when they release...it works.
Sorry to hear your bad experience (either a flawed device or bad network settings on your part, whatever...). But it would be presumtious to take your experience as THE bar for vendor qualification. I have no issues and it performs better than all models/vendors tried before. And I'm not Dlink ;D
-
I have an A2 version and did not have any problems until I installed the latest update and tried to run shareport and then the drops started. Uninstalled shareport and put older firmware back in and still constant drops. Hard to believe things were running great and then a firmware upgrade and nothing but problems. Re-installed my old Netgear router and no problems. I am fixing to start the debugging trying things mentioned and if this does not work time something will be thrown away and a new router search will begin. Hard to believe with these problems that D-Link is not doing more to resolve issues.
-
I have an A2 version and did not have any problems until I installed the latest update and tried to run shareport and then the drops started. Uninstalled shareport and put older firmware back in and still constant drops. Hard to believe things were running great and then a firmware upgrade and nothing but problems. Re-installed my old Netgear router and no problems. I am fixing to start the debugging trying things mentioned and if this does not work time something will be thrown away and a new router search will begin. Hard to believe with these problems that D-Link is not doing more to resolve issues.
Apparently these issue do not affect the majority of users. Reflashing helps 9/10 times. A bad upgrade or downgrade (and restoring the saved config since we're all lazy ;) ) can cause these issues. So reflash the firmware, reset to factory default and build up the config again. This will solve the issues.
-
After too many hours troubleshooting, I think I may have resolved the frequent reboots for my DIR-655. I have firmware 1.21. I have an external HD that was setup to run Mionet. I have disabled Mionet and have the drive mapped to each computer on the network. Apparently, Mionet randomly polled to an external server. I'm told the IP was somewhere in France. Each time it did this first my laptop connection to the router would disable, then when I reinstated that by disabling and re-enabling in network settings, the router would close the connection to the modem, and shut itself off. It's been 4 days now since I disabled Mionet, and the router has not shut itself off once.
-
I'll start a separate thread as well but since google throws this one up I'll share here too : I found that a cheap HDMI cable was the source of my frequent (30-40 times daily) wireless restarts.
If your router lives near a HDMI cable, you might want to experiment by disconnecting the HDMI (and taking it a long way away if you're superstitious!) and then monitoring your connection.
I replaced my cheap HDMI cable and I no longer see frequent restarts (although I still get one or two every couple of days).
I hope that helps someone - it took me 3 full days of researching and trial and error to isolate the issue with mine.
Like others here, I must say that the old and cheap linksys WRT54 I swapped in temporarily while experimenting was not affected by this HDMI cable.
cheers
Paul