D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: davevt31 on January 03, 2008, 03:36:20 PM
-
Just curious on how the routers are postioned and whether it makes a difference in the reboots.
-
The position of the router shouldn't effect reboots. Normally that is caused by wireless interference.
-
I was just curious becuase of so many posts with reboot issues. I was thinking may be a heat issue or maybe something in the hardware design might contribute to the reboots.
-
I noticed that my router would reboot using in in wireless mix mode on firmware prior to 1.11 under heavy strain. I have a old laptop that I remote desktop into my "tvpc" while wife is watching TV in bed and I can not use the big screen TV (Sony 50") for my internet browsing. Turn off the mix mode and the the reboot went away. Have not had to pull out laptop and tried it yet in mixed mode to see if this cures it or not on firmware 1.11.
Merle
-
Just for general knowledge, i'm still haveing the reboot issue with 1.11, all i have to do is turn on wireless, and it starts rebooting.
To be fair, i have not had a chance to play with settings, g/n, wep/wpa etc,
-
Also look at auto channel scan. It is desgined to restart the wireless portion of the router when the unit detects a large amount of traffic on a specific channel.
-
Just as a followup, It's still rebooting, with the scan turned off, and firmware 1.11
the best thing i can say abou this unit, is that the lights are a pretty shade of blue, otherwise, since i' can't use wireless on it, it was a very expensive switch...
I'm about ready to bail on it and try another company's product.
-
Just as a followup, It's still rebooting, with the scan turned off, and firmware 1.11
the best thing i can say abou this unit, is that the lights are a pretty shade of blue, otherwise, since i' can't use wireless on it, it was a very expensive switch...
I'm about ready to bail on it and try another company's product.
Hi mhochman,
Go into the Router Settings. On the Status Tab, click Wirelesss. What is the Signal Strength on that channel?
On my unit, I don't allow it to change Channels. I uncheck Enable Auto Channel Scan and I select the best channel to give me a steady 5 bar connection to the Router.
I also have moved my Wireless Phone Base which I had sitting next to the Router, to the Kitchen away from the Router.
On the Setup to Network Settings, DHCP Lease Time, I changed mine to 10080 minutes or 7 days in length. It is normal settings I believe was 60 or 180 minutes in length.
-
I have the same problem as the poster. My DIR-655 is in a continual reboot state when wireless is enabled. This is very frustrating. I have managed to upgrade the firmware to 1.11 but that hasn't solved the issue. The only resolution to this issue is to turn off wireless completely.
I have tried different combination of wireless settings to make this work. I have tried using it in 802.11g mode only. I've tried various encryption modes. I have tried various channels and signal strengths.
I also see that other people are having similar issues. This is obviously a defect in a product that is supposed to be a more 'high end' home use product. I for one am very discouraged from using d-link products now. D-Link support has doing nothing to address this issue but I think it is because they know its a hardware defect and they don't want to own up to it. This a bad stance for any company. especially on a product that is supposed to be at the high end of your quality scale.
-
D-Link TS did escalate the rebooting problem to engineers. Unfortunately we did it without replication. We could cause rebooting with auto-scan enabled in high traffic wireless areas and solved that problem by "un-enabling" auto-scan.
Other reboot scenarios have been seen by some customers that D-link has not replicated.
Rebooting is wireless "clean" environment with auto-scan checked or unchecked
Rebooting is wireless "dirty" environment with auto-scan checked or unchecked
Can the device work properly on one of those four environments? Of course. But enough people have problems (read the forums, I see at least six user names) that we escalated without repro steps.
DIR-655 1.10 fw "dirty" wireless auto-scan unchecked, no reboots.
dirty and clean are as described by users. If they don't see any AP but theirs and they don't have mirrors, APC, phone base stations, etc near the AP, I call it clean.
-
It becomes an issue of device vs. environment. just because your router reboots in your home does'nt mean dlink will see the same reboot issue in their labs. I'd wager that if you sent your unit to dlink, it won't reboot at all.
It's more then likely a problem thats isolated to a small group of people, however is seems like a lot because of the amount of 655s that dlink has in play around the world. Not to mention that forums allow people to communicate directly with one another, so it's easy to believe that the problem is en-mass, when in reality it's very small.
Then you have to take in to account the cost of fixing this "issue" vs just simply launching a newer more sophisticated product.
-
I just started using the DIR-655 about 2 weeks now and It's working fine. Everything is set by defualt with no problems. 1 desktop PC, macbook, and xbox going smooth so far! ;)
-
i had same problem, CAUTION: see my other thread regarding my RMA experience..... now happy with perfectly good working different brand router.
-
Why would being in a different position make a difference? Althought I have to submit that my router as of recently has begun to reboot several times a day without warning of course and as usual, when I am in the middle of something very important or my wife is in the middle of doing one of her online courses. I am using a DIR-655, and it just started recently within the past two weeks. Getting slightly frustrating, but I did reload the firmware just in case as of this posting date.
-
Try disabling the wireless portion and watch for reboots. If it stop rebooting maybe disable the autop channel scan and force the unit to a specific channel.
-
Did all that. Turned off wireless , reenabled wireless and turned off chan scan, reset different channels, lowered the power output, and reloaded the firmware. The only time it did not reboot (as in the past day) is when I have the wireless turned off. I dont think that it is heat related as it is in a cool place with cooling. I really like the router and only have had it since Aug 07.
-
Whats the H/W_ver?
-
Ver A2. And I have had it on all day today without a reboot with the wireless turned off.
-
On for 2 days now, no reboot with wireless turned off
-
Ok now that I have been half operational (no wireless for 3 days straight) I need to turn my wireless back on because of the need to be able to run my laptops that are not able to get on hardwire. I will make a backup of the log before starting it and see how long it takes before it resets.
-
I got a reboot a few minutes ago.
How do I know it was a re-boot as opposed to lost connection, etc? Two ways. First, I lost both the wireless and wired connection to my laptop (yes, I have them both connected). Second, I checked the log and it shows the system reinitializing:
[INFO] Sat May 17 19:54:56 2008 Time synchronization failed (status 2)
[INFO] Sat May 17 19:54:54 2008 Blocked outgoing TCP packet from 192.168.0.189:2407 to 209.85.173.103:80 as PSH:ACK received but there is no active connection
[INFO] Sat May 17 19:54:53 2008 Requesting time from 64.7.210.145
[INFO] Sat May 17 19:54:53 2008 Time server ntp1.dlink.com is at IP address 64.7.210.145
[INFO] Sat May 17 19:54:53 2008 SMTP (Email) server gmail-smtp.l.google.com is at IP address 209.85.199.111
[INFO] Sat May 17 19:54:53 2008 Starting WAN Services
[INFO] Sat May 17 19:54:53 2008 WAN interface speed measurement completed. Upstream speed is 753 kbps
[INFO] Sat May 17 19:54:45 2008 Starting DHCP server
[INFO] Sat May 17 19:54:38 2008 Estimating speed of WAN interface
[INFO] Sat May 17 19:54:38 2008 WAN interface is up. Connection to Internet established with IP Address 69.64.229.37 and default gateway 69.64.229.1
[INFO] Sat May 17 19:54:38 2008 Bringing up WAN using Static IP Address
[INFO] Sat May 17 19:54:38 2008 WAN interface cable has been connected
[INFO] Sat May 17 19:54:38 2008 LAN interface is up
[INFO] Sat May 17 19:54:38 2008 LAN Ethernet Carrier Detected
[INFO] Sat May 17 19:54:37 2008 Device initialized
[WARN] Sat May 17 19:54:37 2008 gw_wireless_schedule init
[INFO] Sat May 17 19:54:37 2008 Wireless Link is up
[INFO] Sat May 17 19:54:36 2008 Unlock AP setup
[INFO] Sat May 17 19:54:36 2008 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO] Wed Dec 31 17:00:00 1969 Loaded configuration from non-volatile memory
At the time of the reboot my laptop had a cpu usage of 98+% due to adobeupdater hogging the system and it was not responding well (long pauses between user inputs, etc.)
HW ver A3, FW ver 1.11
-
Just got another reboot. Note that this log is slightly different from my post earlier today (compare the top 4 or 5 entries in each log). I thinks that what is going on here is that the "clock" in the router is being reset to some stored value after every reboot.
[INFO] Sat May 17 19:55:48 2008 Allowed configuration authentication by IP address 192.168.0.195
[INFO] Sat May 17 19:55:45 2008 Blocked incoming UDP packet from 65.55.158.81:3544 to 69.64.229.37:4766
[INFO] Sat May 17 19:55:37 2008 Above message repeated 6 times
[INFO] Sat May 17 19:55:37 2008 UPnP added entry 255.255.255.255 <-> 69.64.229.37:62930 <-> 192.168.0.195:4766 UDP timeout:-1 'svchost (192.168.0.195:4766) 62930 UDP'
[INFO] Sat May 17 19:55:36 2008 Blocked incoming UDP packet from 65.55.158.81:3544 to 69.64.229.37:4766
[INFO] Sat May 17 19:55:36 2008 Above message repeated 1 times
[WARN] Sat May 17 19:55:07 2008 A network computer (TOSHIBA-BARBARA) was assigned the IP address of 192.168.0.196.
[INFO] Sat May 17 19:55:04 2008 Wireless system with MAC address 0013CE804B61 associated
[INFO] Sat May 17 19:55:02 2008 Blocked outgoing TCP packet from 192.168.0.195:4556 to 155.199.88.20:443 as FIN:ACK received but there is no active connection
[INFO] Sat May 17 19:55:02 2008 Blocked outgoing TCP packet from 192.168.0.195:4556 to 155.199.88.20:443 as PSH:ACK received but there is no active connection
[INFO] Sat May 17 19:55:01 2008 Blocked incoming TCP packet from 155.199.88.20:443 to 69.64.229.37:4556 as RST:ACK received but there is no active connection
[INFO] Sat May 17 19:54:58 2008 Time synchronization failed (status 2)
[INFO] Sat May 17 19:54:55 2008 Requesting time from 64.7.210.145
[INFO] Sat May 17 19:54:55 2008 Time server ntp1.dlink.com is at IP address 64.7.210.145
[INFO] Sat May 17 19:54:55 2008 SMTP (Email) server gmail-smtp.l.google.com is at IP address 209.85.199.109
[INFO] Sat May 17 19:54:55 2008 Starting WAN Services
[INFO] Sat May 17 19:54:55 2008 WAN interface speed measurement completed. Upstream speed is 752 kbps
[INFO] Sat May 17 19:54:45 2008 Starting DHCP server
[INFO] Sat May 17 19:54:38 2008 Estimating speed of WAN interface
[INFO] Sat May 17 19:54:38 2008 WAN interface is up. Connection to Internet established with IP Address 69.64.229.37 and default gateway 69.64.229.1
[INFO] Sat May 17 19:54:38 2008 Bringing up WAN using Static IP Address
[INFO] Sat May 17 19:54:38 2008 WAN interface cable has been connected
[INFO] Sat May 17 19:54:38 2008 LAN interface is up
[INFO] Sat May 17 19:54:38 2008 LAN Ethernet Carrier Detected
[INFO] Sat May 17 19:54:37 2008 Device initialized
[WARN] Sat May 17 19:54:37 2008 gw_wireless_schedule init
[INFO] Sat May 17 19:54:37 2008 Wireless Link is up
[INFO] Sat May 17 19:54:36 2008 Unlock AP setup
[INFO] Sat May 17 19:54:36 2008 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO] Wed Dec 31 17:00:00 1969 Loaded configuration from non-volatile memory
-
Here is another reboot about 3 hours after the last one; that's three random reboots today (at least three because the PCs all silently reconnect when the router comes back up and the old log is wiped out, so there could have been other reboots today that I didn't notice viat the netork connection balloon in the systray announcing that the network connection is now up):
INFO] Sat May 17 19:55:09 2008 Above message repeated 2 times
[INFO] Sat May 17 19:55:07 2008 UPnP added entry 255.255.255.255 <-> 69.64.229.37:16851 <-> 192.168.0.195:4906 UDP timeout:-1 'svchost (192.168.0.195:4906) 16851 UDP'
[INFO] Sat May 17 19:55:05 2008 Blocked incoming TCP packet from 209.85.147.19:80 to 69.64.229.37:4689 as PSH:ACK received but there is no active connection
[INFO] Sat May 17 19:55:03 2008 Above message repeated 1 times
[INFO] Sat May 17 19:55:01 2008 Time synchronization failed (status 2)
[INFO] Sat May 17 19:55:01 2008 Blocked incoming TCP packet from 209.85.147.19:80 to 69.64.229.37:4689 as PSH:ACK received but there is no active connection
[INFO] Sat May 17 19:55:00 2008 Above message repeated 2 times
[INFO] Sat May 17 19:54:59 2008 Blocked incoming UDP packet from 122.141.76.2:37647 to 69.64.229.37:1027
[INFO] Sat May 17 19:54:58 2008 Requesting time from 64.7.210.145
[INFO] Sat May 17 19:54:58 2008 Time server ntp1.dlink.com is at IP address 64.7.210.145
[INFO] Sat May 17 19:54:58 2008 SMTP (Email) server gmail-smtp.l.google.com is at IP address 209.85.199.109
[INFO] Sat May 17 19:54:58 2008 Starting WAN Services
[INFO] Sat May 17 19:54:58 2008 WAN interface speed measurement completed. Upstream speed is 753 kbps
[WARN] Sat May 17 19:54:57 2008 A network computer (TOSHIBA-BARBARA) was assigned the IP address of 192.168.0.196.
[INFO] Sat May 17 19:54:56 2008 Wireless system with MAC address 0013CE804B61 associated
[INFO] Sat May 17 19:54:45 2008 Starting DHCP server
[INFO] Sat May 17 19:54:38 2008 Estimating speed of WAN interface
[INFO] Sat May 17 19:54:38 2008 WAN interface is up. Connection to Internet established with IP Address 69.64.229.37 and default gateway 69.64.229.1
[INFO] Sat May 17 19:54:38 2008 Bringing up WAN using Static IP Address
[INFO] Sat May 17 19:54:38 2008 WAN interface cable has been connected
[INFO] Sat May 17 19:54:38 2008 LAN interface is up
[INFO] Sat May 17 19:54:38 2008 LAN Ethernet Carrier Detected
[INFO] Sat May 17 19:54:37 2008 Device initialized
[WARN] Sat May 17 19:54:37 2008 gw_wireless_schedule init
[INFO] Sat May 17 19:54:37 2008 Wireless Link is up
[INFO] Sat May 17 19:54:36 2008 Unlock AP setup
[INFO] Sat May 17 19:54:36 2008 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO] Wed Dec 31 17:00:00 1969 Loaded configuration from non-volatile memory
Again, the time is reset as Sat May 17 19:54:36 2008
HW ver A3, FW ver 1.11
-
Ok.. went 4 days without reboot with the wireless on.. then on Monday it started rebooting constantly.
One of the other things that I have noticed is that when the wireless is turned on, my time is wrong. If I set it, it will hold for a little while, then it loses itself. When I go back in later, the time is not up to date but behind, then it just keeps losing time.
If the wireless is off, the time stays "on time" not losing time. This could be an effect of the actual issue. I also have some logs to back this up. But as I see it, this piece of hardware needs to be fixed please, or replaced as soon as possible.
Thnx
-
Ok.. went 4 days without reboot with the wireless on.. then on Monday it started rebooting constantly.
One of the other things that I have noticed is that when the wireless is turned on, my time is wrong. If I set it, it will hold for a little while, then it loses itself. When I go back in later, the time is not up to date but behind, then it just keeps losing time.
If the wireless is off, the time stays "on time" not losing time. This could be an effect of the actual issue. I also have some logs to back this up. But as I see it, this piece of hardware needs to be fixed please, or replaced as soon as possible.
Thnx
I'm pretty darn sure "that when the wireless is turned on, my time is wrong" is because when your wireless is on you are getting reboots and the router pretty clearly does not maintain the correct time between reboots, but rather reloads some previous value.
-
Actually no. I have been in my router many times, and it has NEVER kept the correct time, even before this "reboot all the time when the wireless is enabled" started. Even after updating the firmware. So the issue is why is it doing this, why did it just start, and I have already put in a ticket to DLink, and how quickly will it get fixed? My wife does college online and needs the internet....
-
Is it possible that the power source for the router is flaky in some way? Securely plugged into a power strip that never was zapped? Power strip plugged securely into a reliable AC outlet? Adapter plug securely inserted into the router's power input port?
Just a thought.
Harvey
-
Probably not, as I take my "house power" and run it through a UPS backup system. It is very stable and if there is a "power issue" the UPS handles it very well.
-
UPS's have been known to cause Reboots. Is the router near the UPS?
-
UPS's have been known to cause Reboots. Is the router near the UPS?
Or maybe it is near (within 75yds) a 2.4Ghz phone (say, your neighbor), or maybe it is near organic life, or maybe it is near planet earth..... or maybe the DIR-655 only works reliably in electromagnetically sterile environments.
Keeping your modem, router and hubs on an UPS is a terrific idea, very nice to maintain the internet connection when the power goes out. Not having to replace your 2.4Ghz phone is also nice. The DIR-655 cost of ownership just keeps climbing.
-
I own 2 dir-655s. Both are connected to a DFL-800 as a gateway. I own several Servers that sit on BOTH of my LANs. I use a Belkin battery backup and have UP times of 180+ hours, and I think the last reboot was to change one of the SSIDs.
The issue is as follows. Not all devices will work in everyones environments. We understand these issues are frustrating but without being able to reproduce them here, that makes the issue a problem with your environment. We're trying to help as best as we can short of someone coming to your house with a multimeter and watching for waveform issues, theres not much that we haven't covered.
-
What about removing the UPS temporarily as a test?
-
I have my 655 sitting about 3 feet away and about 2 feet above 2 UPS's and have not had one reboot.
-
If having the DIR-655 on a UPS were part of the problem, I would have probably seen it long ago. I have always kept my router and modem on the UPS, saves a lot of headache. Also, the router has rebooted once or twice on its own without the wireless being on. I am fairly sure that there are also ( but not 110% certain) that there are no 2.5ghz phones close by. But as was stated in a previous post, the reboots happened day or night, no given time, and I had changed to every channel with no change.
-
Lets try this. Disable the internal logging and run a syslogger. Kiwi is free.
That will at least give us an idea of what the problem is.