D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: whitey019 on June 05, 2009, 12:21:05 PM
-
I just spent the last week and half trying to figure out why my DIR-655 (A4) kept periodically having wireless restarts (1-7mins). Like most people on this forum and elsewhere I tried various versions of firmware, settings and flash methods. I was all set to RMA this blasted thing when I decided to borrow another DIR-655, which was an older hardware version (A2), and it did the same thing. Then I took the router to work and it worked there flawlessly; so it had to be my environment….but what. I turned off all gadgets in the house including, phones, game systems, fluorescent lights, moved the router around to various locations and even asked neighbors to change channels on their wireless networks…all to no avail. I borrowed a ***escope network analyzer to monitor the wireless activity and found nothing out of the ordinary. Then I thought it has to be something in my network hardware…I started with the power. After plugging things in to various different outlets, UPSs and surge protectors, nothing seemed to matter. Next I disconnected all my wired computers, peripherals and switches and then an amazing thing occurred…..IT WORKED…..the highly proclaimed D-Link Dir-655 wireless router actually worked and did so continuously with no restarts at all. Well, to wrap this up, it turned out that any time I plugged one specific computer into any wired switch (I have four including the DIR-655) it would immediately cause a wireless restart followed by periodic restarts. I haven’t quite figured out what is going on, but I believe something must be wrong with the NIC in that system (RTL 8186C/8111C), because I have changed drivers, cables and connection point and nothing helps. Hopefully writing this has not just jinxed me and I’ll provide an update after I get a chance to try another network adapter.
-
There are a few of users on this forum (the Dlink Router Bashers ;D) that will still claim that you're wrong (and me too) and that the router is always at fault. Thanks for your contribution that also stresses that the environment can play an essential factor in router issues!! :-*
-
I didn't mean to suggest that I had solved 'all' wireless restart problems, but just wanted to pass on information that might help someone else in their trouble shooting efforts. I'm sure a lot of other people's problems are congestion at 2.4 Ghz and others may have bad hardware.
-
Thanks for your input whitey. I have been following this forum silently because I haven't got the tech expertise most of the other users have, your suggestion does seem as viable as any I've read so far. I haven't had my router working properly since 1.11 firmware. Constant drops on my router makes me wonder if it isn't a hardware problem somewhere.......
Lots of valuable information on this forum. I will continue trying all suggestions from Lycan, Eddie, and others until I get this thing working.
-
There are a few of users on this forum (the Dlink Router Bashers ;D) that will still claim that you're wrong (and me too) and that the router is always at fault. Thanks for your contribution that also stresses that the environment can play an essential factor in router issues!! :-*
But in this case, it should be obvious that a rogue NIC should not make the router drop its wireless connection.
-
Hi,
Just a SWAG here, but it occurs to me that your "Rogue" NIC (as it was termed) is drawing too much electricity for some reason (as these things can often be mysteries) which is indeed affecting the internal power routing/transmission or possibly causing the power chips to overheat or some other physical phenomena inside your various routers, inducing the wireless drops you are seeing.
I have had NICs go bad, but once I determined it was a bad NIC, I just tossed it and put in a good one.
SD1
-
But in this case, it should be obvious that a rogue NIC should not make the router drop its wireless connection.
And you are blaming the router for this? What nonsense. Faulty NIC's can even kill your system. They shouldn't , but they can and do.
If you get punched in the face by a madman, do you also blame yourself? ;)
-
The mystery deepens. I replaced the NIC, but still every time, and I emphasize every time,I plug that particular computer into any part of my LAN the router immediately has a wireless restart followed by periodic restarts. I'm not sure where to go now....
-
The mystery deepens. I replaced the NIC, but still every time, and I emphasize every time,I plug that particular computer into any part of my LAN the router immediately has a wireless restart followed by periodic restarts. I'm not sure where to go now....
Well, the issue stays contained to your PC. ;)
Did you get another Realtek NIC or did you get a proper one this time? Have you tried resetting the TCPIP and Winsock2 stacks?
-
Try replacing the PSU in that PC. It could be that the network card is not getting enough power from the PCI slot so its overdrawing to compensate?
When picking a power supply, feel how heavy it is, quality power supplies should be 1 - 2KG.
-
whitey019,
After reading your post, I had an idea. Is it possible that your problem is the result of a ground loop? Is the PC in question plugged into a different circuit in your house? It's not uncommon for electrical outlets, even in the same room, to be on different circuits and have their common and ground lines at different potentials from each other. This can cause current to flow (when it shouldn't) between two devices connected together and plugged into different outlets or surge suppressors/uninterruptible power supplies.
If the router and PC are on different circuits, try plugging them into the same power strip and see what happens.
Just a thought,
Mike
-
whitey019,
After reading your post, I had an idea. Is it possible that your problem is the result of a ground loop? Is the PC in question plugged into a different circuit in your house? It's not uncommon for electrical outlets, even in the same room, to be on different circuits and have their common and ground lines at different potentials from each other. This can cause current to flow (when it shouldn't) between two devices connected together and plugged into different outlets or surge suppressors/uninterruptible power supplies.
If the router and PC are on different circuits, try plugging them into the same power strip and see what happens.
Just a thought,
Mike
Thanks Mike, I had the same thought, unfortunately it still causes the problem. I also removed all surge protectors....as I've seen them cause some strange grounding issues also....but it didn't help either. I think I'll try a shorter cable than the two 50ft ones that I've tried so far. After that it would have to be the power supply or the mainboard itself.
-
I had a problem once where the network adapter kept disconnecting and I would have to disable then re-enable it (or reboot the PC) to get the connection back.
Turned out to be the power supply going bad.
-
Thanks Mike, I had the same thought, unfortunately it still causes the problem. I also removed all surge protectors....as I've seen them cause some strange grounding issues also....but it didn't help either. I think I'll try a shorter cable than the two 50ft ones that I've tried so far. After that it would have to be the power supply or the mainboard itself.
Have you tried a different PCI slot?
-
I wanted to add that I was having this problem today. It just started a few hours ago so I googled, found the threads on here, and tried things out.
On my DIR-655, first thing I did was try upgrading from 1.21 to 1.31 but the problem persisted. When I read this thread, I realized that just when the problem started showing up, I updated Symantec Endpoint Protection on a wired machine, including the firewall features, and after rebooting it, my wireless computers (3 in all) started dropping like flies. "Wireless Restart" showed up in the router log every minute or two, like clockwork.
I just shut down that wired machine and... whaddyaknow, the wifi status has been rock solid again, like it has been for the 2 past years I've had my DIR-655.
Now, I'm wondering if the firewall feature of SEP is doing something strange... I didn't have that part of SEP installed before, but upgrading to the latest release, I figured I'd include it and disabled the Windows 7 RC firewall instead. I guess I better rethink that, or at least do more tests and see if indeed it's the SEP firewall causing the DIR to drop wifi sessions like hot potatoes.
So, before you wonder about whether you have a bad router, you might try it out with all wired-connections unplugged just to see if that solves it. Whether wireless restarts are a problem with the NIC on some systems, or whether the DIR is mishandling some data in a very bad way, I'm not sure, but the wired-NIC is definitely the cause in my (and apparently other) cases.
-
mpb...you did it! All I did was disable SEP's firewall on that toublesome system and lo and behold everything works (so far anyway). But, someone is going to have to explain to me how/why Symantec EP's Firewall can cause the router to have wireless restarts.
-
Symantec? ;)
-
Just to follow up. Everything is working perfectly now that I have disabled Symantec EndPoint's (SEP) firewall on that offending system. That's 3 days without a hiccup and I expect it will continue that way. I still would like to know how SEP could cause wireless problems on a router.
-
is it doing something weird with upnp? I have a machine with SEP and it itself has nothing but connection issues.
rest of the network seems fine 90% of the time.
-
SEP is causing the issues. It's even capable of causing wireless resets.
-
From a Noob in Sweden with DIR-655 Firmware Version : 1.21EU, 2008/11/03
I have same problem with one of my laptops but not with the other laptop and not with my Mac that has both WIFI and wired Gbit connected.
Have left all systems off but when the one laptop (HP EliteBook 2530P) is connected the wireless goes down and up in cycles, just as you other guys have described it.
Strange thing is, that very laptop did NOT cause problem before I installed all the latest updates from Microsoft. And also other drivers may have been updated since it is my job computer and the IT dept keep pushing stuff out without me knowing it.
I am convinced there is something on the laptop that causes this problem with thr WIFI. Best guess is the Symantec Antivirus Full Version 10.1.5.5000 or CheckPoint VPN-1 Secure Client. Or could it be Windows IE8?
I will experiment with disabling one at a time. Will keep you posted.
PS Portion from the log , this keeps repeating:
INFO] Fri Jun 12 11:55:18 2009 Yammer: Wireless system with MAC address *********** disconnected for reason: Received Deauthentication
[INFO] Fri Jun 12 11:55:14 2009 Yammer: Wireless system with MAC address *********** associated
-
I am having the same problem with my EGreat M34a NMT with TPLink USB Wifi Dongle, but obviously no trace of Symantec intrusion under Linux. :D :)
The connection speed reported by DIR655: about 300Mbit and 92% strength
Dir 655 has 1.31NA stock (no beta)
I am using DIR655 for G and N with WPA2. The old MS router is wired to it as access point for a differently named SSID for WEP access. This one is using channel1 apart of DIR 655 - 11th channel
What I've noticed that I am having this problem only in N connection, G adapters are working fine with same security settings - WPA2 Personal, AES. auto channel, 20/40, SSID broadcast
But I'd like to play with setting on DIR 655 QOS for video streaming and change some advanced wireless settings. I'll report results...
As a last resort I was thinking to use Asus RT15 as a bridge and connect NMT through wire to it and see if problem will go away
IMHO, this product was crappy and still is crappy with all those N and other upcoming products and constantly changing firmware introducing new problems...
Peter
-
IMHO, this product was ****py and still is ****py with all those N and other upcoming products and constantly changing firmware introducing new problems...
Peter
IMHO, this product is freakin' awesome and if corporate hadn't forced the engineers to make USB port sharing the single number one priority on the planet because they spent so much money on advertising and press because they let marketing guys tell engineering what is possible even though the laws of physics say otherwise, I'd say about half the scuttlebut on this forum wouldn't be here.
Is your wireless NIC made by D-Link and chosen from the list of NIC's that "Work with" the DIR-655? Now, what follows is only my opinion and not backed by any scientific or engineering proof and if I get squashed like a bug, so be it, but if you are using Brand-X's NIC because you think it is better or for whatever reason, you've already gotten off on the wrong foot. When I chose the DIR-655 I immediately grabbed 2 DWA-652's with it. I wasn't about to take a chance that buying a different brand because it was cheaper or got better reviews might cause my router to not do the things that were advertised. I update the NIC drivers and software if there is a newer version. If I start out with all things D-Link, and I eliminate any outside influences (sun spots, somebody using an arc welder in the same room), I make sure all of my computer drivers are up to date, my OS is up to date, my PC hardware is healthy, my browser works with the router interface, I input the correct settiings for my ISP, my Wife is Happy, then and only THEN would I begin to suspect that something is fishy in Denmark. If you have done all of these things and now you are ready punch me in the nose, let me first hide behind Xinot, or Fatman.
-
My laptop workes fine on wireless with the SEP firewall configured.
It also works fine when physically connected to the router and SEP firewall configured, but while connected physically, my wireless signal drops all my other wireless devices. When I disable SEP's Firewall, my other wireless devices work fine.
I monitored my signal from another computer and watched the signal just become unstable every time a wired computer with SEP's Firewall enabled connected to my network. As soon as I disable SEP firewall, the wireless signal becomes stable and all my devices reconnect.
Any ideas on what could cause SEP Firewall to cause this issue for wireless systems when it is running on a wired system?
-
So, I was somewhat skeptical at first, but the more I read the more excited I got... I too have been plagued by wireless restarts, and been run through the ridiculous setting changes requested by tech support. I too have a hard-wired PC connected to my router, and it toois running Symantec Endpoint Protection. And, now that I was tipped off to check it out in more detail, at long last I seem to have a possible lead.
I've been able to correlate the wireless restarts to a burst of ipV6 packets (type 0x86DD) showing as "blocked" in my SEP traffic log. When I compare the logs, it's clear that both are happening at the same time, though not completely clear as to the true cause. I'll post more and let you know what I find out.
-
Man, I hope I'm not gonna jinx myself... Switched Symantec Endpoint Protection's default "block ipV6" rule to allow ipV6 traffic. Lo and Behold, I survived the last burst without a wireless restart! I'd seen wireless restart about every 5-7 minutes, and in 100% of the cases (15 out of 15) it was correlated within 15 seconds or so of a burst of ipV6 traffic getting blocked.
Try enabling ipV6 traffic in SEP and let me know if you see the same result!!!
Rob G.
-
How about upgrading your Endpoint Protection to 11.0MR4 MP2?
http://www.symantec.com/business/support/downloads.jsp?pid=54619
-
when using corporate machines you don't get to pick your software versions or upgrade them when you like claykin. and typically people are using SEP because their company tells them to.
I will inquire at my work about he IPv6 blocking and see if the network admin can change that one for me.
Edit - side note.. I just checked and the IPv6 blocking is turned on. oh and I do get restarts anywhere from 5-15 minutes apart. this is also a new laptop since my last post.
-
So, allowing the ipV6 traffic has **almost** completely elmiinated my restart problem. Literally I was having this issue every 5-7 minutes, and now I've only had 3 or 4 in the last 5 days. By the way, I was running SEP 11.0.4014.26.
-
Whitey! Thank you so much for figuring this issue out. I have the DIR-615 RevB and recently reloaded my machine. When I did so I reinstalled SEP and decided to install the network monitoring and firewall portion as well and that caused all hell to break loose with my router. I spent all day searching for a fix and shopping for a new router as well until I found your thread. Home from work, two seconds to disable the SEP firewall and here I am online with wireless enabled and devices connected.
Here is a link to my little thread that I started this morning for S n G's.
http://forums.dlink.com/index.php?topic=7134.0
Thanks again!
D-Link! STICKY THIS THREAD!
-
Old topic, but I figure I bump it because mpb, you saved me from throwing my DIR 655 out the window.
I knew Symantec's products were garbage, but I decided to install it anyways. Soon after, I started to get constant drops on my wireless connections. Had no clue what was going on and I never connected the two together. I did everything imaginable, firmware upgrades, change in settings, and even went out an bought a new DIR 655!
Nothing worked until I stumbled onto this thread.
Turned off SEP, and instantly everything worked like normal. >:( Symantec!
Anyways, I was so happy, I had to register on this forum just to tell my story. ;D
-
Just to add my experience with a Norton product also. Norton "retail" grade security packages (360 and Internet Security 2009) firewall module need to be told to "trust" the network LAN gateway IP address and the wireless network name (SSID.) If not, the software will "deauthenticate" from the router.
-
I haven't check this forum much since I solve my restart issue, but I can see that others have benefited from my experiences .........that's great. Maybe this thread should be a STICKY as suggested.
-
I'm glad disabling SEP is working for everyone else. Honestly, I don't know what made me try it in the first place, except I noticed my wireless always seemed to drop shortly after my wired machine booted up.
SEP firewall on a wireless machine seems fine... it's only that wired connection that causes the issue.
I saw the other post about it being related to the IPV6 default rule... very interesting. I'm not sure why the D-Link would react to whatever SEP is doing by deciding to restart the wireless, that's very strange, and maybe it's something D-Link could patch around, or it represents some unknown flaw in D-Link's code.
By the way, I'm running the latest version of SEP, 11.0.4202.75, and Symantec hasn't addressed or patched the issue.
I sometimes logon to the Symantec EP forums so maybe rather than wait for Symantec to stumble across this, I should actually start a thread and see if the Symantec engineers have any input.
-
Hi All,
Let me jump it here. I do not know Symantec Norton Products, because I use McAfee Internet Security and while I do not use SecureSpot, D-Link might wish to check SecureSpot's Logs.
Why?
I am running the McAfee Personal Firewall on my Personal Desktop Computers. I always check its logs. Anyway, even though the Network is completely trusted, McAfee is blocking the Router and a number of other devices that are on the Network. And the Network, again is completely Trusted.
I would look at the logs of your Firewall products that all you use and see if anything is being blocked, that is part of your Network.
-
What this all tells me is that the DIR655 experiences a buffer overflow when certain classes of network traffic are blocked by internal devices. In other words, it run's out of memory in some internal buffer and restarts the service (wireless in this case).
So, even though these personal firewalls are blocking things, it still points back to the DIR655. However, the information here does let them (DLINK) know the specific traffic type that is causing the lockups on this new 1.3.x class of firmware. This fact alone is worth the price of the post.
TheWitness
-
I have been having this as a issue for quite a while and I have un-installed SEP 11.0.4202.75 and my wireless has not restarted since(going on 2 days now). I only removed SEP from the one PC I have directly wired to the router. The wireless restarts do not seem to be a issue with a PC that has SEP that is connected wirelessly to the router.
Is this a firmware buffer overflow issue??
THANKS FOR THE FIX!
-
Just to clarify things, you can still use SEP as long as you don't enable/install the firewall.
-
I have had the same problems with wireless restarts. Then I read somewhere that it could be related to DHCP - maybe Windows 7 or IPv6 - that caused some kind of buffer overflow in the DIR-655. Well, I have reserved all my addresses and it had been solid for 48 hours. :D
Per
-
My findings on this... the issue is with SEP... the issue is not the IPv6 setting.
I'm trying to get my network guy at work to tell me what it was, we did try the IPv6 and it was not different.
The side note is that Dlink was not the only vendor that this hit... seems that only Linksys (my companies standdard provided router if you do not have one) did not get it.
-
I have a DIR-655 A3, working over a DWA-142 rangebooster N from my desktop PC. I was not getting frequent restarts, but I was getting frequent de-authentication requests being sent to the router, which disconnected my internet sessions. I'm not sure, but this may be related to the restart problem mentioned here. I upgraded my router firmware to 1.21, and the firmware for the rangebooster adapter N.
I also made all the changes to upgrade the speed to 300 mbps, which worked fine.
Per this thread, I set up my kaspersky antivirus to allow traffic from the addresses the router uses for my desktops and laptops, and to allow traffic from the router itself.
So far, so good. I booted up this morning and my internet hasn't gone down all day.
;D
Hopefully this helps someone else who may also have these problems.
I do suspect that it was the rangemaster N firmware upgrade that did the trick, but I didn't have time to do the incremental testing to confirm this.
-
ALL, thanks to everyone for their relentless pursuit to fix this problem. Like vipervin, you saved an perfectly good router from taking a flying leap.
That said, to add a note. I was running a much older Motorola Router and upgraded to a Trendnet 655 N router. No big issues until I added a second and then third computer. I didn't attribute the SAV to the problem and figured it was from a cheap router, did my research on-line and found the DIR-655 fit my needs. Still had the same issue so figured it was my Cable Modem which was pretty old (2004) so I got the cable company to replace it. New router, new modem, new computers, old PC (with SAV) same problem until now. I changed the firewall settings and so far so good. ;D
I will max my system as much as I possibly can, adding 2 more laptops and another PC on the LAN. I will update based on good or bad results.
Thanks again!
-
Have scanned the articles in this thread.
I have the 655 connected to a dlink green Gb switch, which connects it to all clients. At the time of the wireless restarts there was no laptop or any PC like client active. Only active party each night is my linux based DS207+ NAS. No SEP to be seen anywhere in the house.... So are there other reasons to let it restart? BTW i have syslog running for more than a week and this is the first with these restarts....
Dec 4 00:03:16 192.168.1.250 Fri Dec 04 00:03:19 2009 paco System Log: Wireless restart
Dec 4 00:04:23 192.168.1.250 Fri Dec 04 00:04:27 2009 paco System Log: Wireless restart
Dec 4 00:06:51 192.168.1.250 Fri Dec 04 00:06:54 2009 paco System Log: Wireless restart
Dec 4 00:16:42 192.168.1.250 Fri Dec 04 00:16:46 2009 paco System Log: Wireless restart
Dec 4 00:18:01 192.168.1.250 Fri Dec 04 00:18:04 2009 paco System Log: Wireless restart
Dec 4 00:21:33 192.168.1.250 Fri Dec 04 00:21:37 2009 paco System Log: Wireless restart
Dec 4 00:21:47 192.168.1.250 Fri Dec 04 00:21:50 2009 paco System Log: Wireless restart
Dec 4 00:22:12 192.168.1.250 Fri Dec 04 00:22:16 2009 paco System Log: Wireless restart
Dec 4 00:25:39 192.168.1.250 Fri Dec 04 00:25:43 2009 paco System Log: Wireless restart
Dec 4 00:27:29 192.168.1.250 Fri Dec 04 00:27:33 2009 paco System Log: Wireless restart
Dec 4 00:29:54 192.168.1.250 Fri Dec 04 00:29:58 2009 paco System Log: Wireless restart
Dec 4 00:34:05 192.168.1.250 Fri Dec 04 00:34:09 2009 paco System Log: Wireless restart
Dec 4 00:35:51 192.168.1.250 Fri Dec 04 00:35:55 2009 paco System Log: Wireless restart
Dec 4 00:38:41 192.168.1.250 Fri Dec 04 00:38:45 2009 paco System Log: Wireless restart
Dec 4 00:38:48 192.168.1.250 Fri Dec 04 00:38:52 2009 paco System Log: Wireless restart
Dec 4 00:39:15 192.168.1.250 Fri Dec 04 00:39:19 2009 paco System Log: Wireless restart
Dec 4 00:39:47 192.168.1.250 Fri Dec 04 00:39:51 2009 paco System Log: Wireless restart
Dec 4 00:41:23 192.168.1.250 Fri Dec 04 00:41:27 2009 paco System Log: Wireless restart
Dec 4 00:41:32 192.168.1.250 Fri Dec 04 00:41:35 2009 paco System Log: Wireless restart
Dec 4 00:41:35 192.168.1.250 Fri Dec 04 00:41:39 2009 paco System Log: Wireless restart
Dec 4 00:42:10 192.168.1.250 Fri Dec 04 00:42:13 2009 paco System Log: Wireless restart
Dec 4 00:46:09 192.168.1.250 Fri Dec 04 00:46:13 2009 paco System Log: Wireless restart
Dec 4 00:46:27 192.168.1.250 Fri Dec 04 00:46:31 2009 paco System Log: Wireless restart
Dec 4 00:48:44 192.168.1.250 Fri Dec 04 00:48:48 2009 paco System Log: Wireless restart
Dec 4 00:49:18 192.168.1.250 Fri Dec 04 00:49:22 2009 paco System Log: Wireless restart
Dec 4 00:50:14 192.168.1.250 Fri Dec 04 00:50:18 2009 paco System Log: Wireless restart
Dec 4 00:50:40 192.168.1.250 Fri Dec 04 00:50:44 2009 paco System Log: Wireless restart
Dec 4 00:50:43 192.168.1.250 Fri Dec 04 00:50:47 2009 paco System Log: Wireless restart
Dec 4 00:57:47 192.168.1.250 Fri Dec 04 00:57:51 2009 paco System Log: Wireless restart
Dec 4 00:58:35 192.168.1.250 Fri Dec 04 00:58:39 2009 paco System Log: Wireless restart
Dec 4 00:58:51 192.168.1.250 Fri Dec 04 00:58:55 2009 paco System Log: Wireless restart
Dec 4 01:00:46 192.168.1.250 Fri Dec 04 01:00:50 2009 paco System Log: Wireless restart
Dec 4 01:09:33 192.168.1.250 Fri Dec 04 01:09:38 2009 paco System Log: Wireless restart
Dec 4 01:11:13 192.168.1.250 Fri Dec 04 01:11:18 2009 paco System Log: Wireless restart
Dec 4 01:13:09 192.168.1.250 Fri Dec 04 01:13:14 2009 paco System Log: Wireless restart
Dec 4 01:19:47 192.168.1.250 Fri Dec 04 01:19:52 2009 paco System Log: Wireless restart
Dec 4 01:34:53 192.168.1.250 Fri Dec 04 01:34:58 2009 paco System Log: Wireless restart
Dec 4 01:35:02 192.168.1.250 Fri Dec 04 01:35:07 2009 paco System Log: Wireless restart
Dec 4 01:38:02 192.168.1.250 Fri Dec 04 01:38:07 2009 paco System Log: Wireless restart
Dec 4 01:38:23 192.168.1.250 Fri Dec 04 01:38:28 2009 paco System Log: Wireless restart
Dec 4 01:39:12 192.168.1.250 Fri Dec 04 01:39:17 2009 paco System Log: Wireless restart
Dec 4 01:40:34 192.168.1.250 Fri Dec 04 01:40:39 2009 paco System Log: Wireless restart
Dec 4 01:40:50 192.168.1.250 Fri Dec 04 01:40:55 2009 paco System Log: Wireless restart
Dec 4 01:42:07 192.168.1.250 Fri Dec 04 01:42:12 2009 paco System Log: Wireless restart
Dec 4 01:42:36 192.168.1.250 Fri Dec 04 01:42:41 2009 paco System Log: Wireless restart
Dec 4 01:43:58 192.168.1.250 Fri Dec 04 01:44:03 2009 paco System Log: Wireless restart
Dec 4 01:44:02 192.168.1.250 Fri Dec 04 01:44:07 2009 paco System Log: Wireless restart
Dec 4 01:46:21 192.168.1.250 Fri Dec 04 01:46:26 2009 paco System Log: Wireless restart
Dec 4 01:46:47 192.168.1.250 Fri Dec 04 01:46:52 2009 paco System Log: Wireless restart
Dec 4 01:47:12 192.168.1.250 Fri Dec 04 01:47:17 2009 paco System Log: Wireless restart
Dec 4 01:48:49 192.168.1.250 Fri Dec 04 01:48:54 2009 paco System Log: Wireless restart
Dec 4 01:55:27 192.168.1.250 Fri Dec 04 01:55:32 2009 paco System Log: Wireless restart
Dec 4 01:55:31 192.168.1.250 Fri Dec 04 01:55:36 2009 paco System Log: Wireless restart
Dec 4 01:58:05 192.168.1.250 Fri Dec 04 01:58:10 2009 paco System Log: Wireless restart
Dec 4 01:59:05 192.168.1.250 Fri Dec 04 01:59:10 2009 paco System Log: Wireless restart
Dec 4 02:00:33 192.168.1.250 Fri Dec 04 02:00:38 2009 paco System Log: Wireless restart
Dec 4 02:02:55 192.168.1.250 Fri Dec 04 02:03:00 2009 paco System Log: Wireless restart
Dec 4 02:03:01 192.168.1.250 Fri Dec 04 02:03:05 2009 paco System Log: Wireless restart
Dec 4 02:03:49 192.168.1.250 Fri Dec 04 02:03:54 2009 paco System Log: Wireless restart
Dec 4 02:04:33 192.168.1.250 Fri Dec 04 02:04:38 2009 paco System Log: Wireless restart
Dec 4 02:04:39 192.168.1.250 Fri Dec 04 02:04:43 2009 paco System Log: Wireless restart
Dec 4 02:06:59 192.168.1.250 Fri Dec 04 02:07:04 2009 paco System Log: Wireless restart
Dec 4 02:15:52 192.168.1.250 Fri Dec 04 02:15:57 2009 paco System Log: Wireless restart
Dec 4 02:19:28 192.168.1.250 Fri Dec 04 02:19:33 2009 paco System Log: Wireless restart
Dec 4 02:22:26 192.168.1.250 Fri Dec 04 02:22:31 2009 paco System Log: Wireless restart
Dec 4 02:22:37 192.168.1.250 Fri Dec 04 02:22:42 2009 paco System Log: Wireless restart
Dec 4 02:24:20 192.168.1.250 Fri Dec 04 02:24:25 2009 paco System Log: Wireless restart
Dec 4 02:27:42 192.168.1.250 Fri Dec 04 02:27:47 2009 paco System Log: Wireless restart
Dec 4 02:34:40 192.168.1.250 Fri Dec 04 02:34:45 2009 paco System Log: Wireless restart
Dec 4 02:34:59 192.168.1.250 Fri Dec 04 02:35:04 2009 paco System Log: Wireless restart
Dec 4 02:35:05 192.168.1.250 Fri Dec 04 02:35:10 2009 paco System Log: Wireless restart
Dec 4 02:36:18 192.168.1.250 Fri Dec 04 02:36:22 2009 paco System Log: Wireless restart
Dec 4 02:37:19 192.168.1.250 Fri Dec 04 02:37:24 2009 paco System Log: Wireless restart
Dec 4 02:39:13 192.168.1.250 Fri Dec 04 02:39:18 2009 paco System Log: Wireless restart
---after this the device decided to reboot itself---
-
I had the same problems with the wireless restarts. First I could not find out wat the reason was, and D-link as well. I've never linked it to SEP that I installed in the last month. So after 2 years of no problems at all, they offered to replace it. And so I did.
After I received the new one I could correlate some of the issues and fixes described above.
My first router was A2 hardware. FW: 1.21 EU. On this router I had problems with wireless restarts. Both with a wired connection as well as with the wireless laptops. On all three machines I ran SEP version 12.0.122.192. Unfortunately I did not try disabling the SEP firewall before I returned the device to D-link.
My new router is A4 hardware, also FW: 1.21 EU. On this router I do not have any problems with wireless restarts. On the wireless laptops I have disabled the IPv6 firewall rules. Permanently disabling the SEP firewall at all does not work, since after some time it automatically switches itself on again. However. NO problems with wireless restarts, even with the SEP firewall ON.
But......as soon as I connected the wired desktop with SEP running with the firewall ON, wireless restarts every couple of minutes. Disabling the SEP firewall on the desktop fixes it.
So: it is not just an wired vs wireless issue or just a SEP issue. It also has to do with the hardwareversion of your router.
I'm happy again with my router :)
-
You guys have given me hope! My wireless restarts were getting more frequent and my wireless clients were all but useless. http://forums.dlink.com/index.php?topic=10045.0 (http://forums.dlink.com/index.php?topic=10045.0)
I do have SEP, but *not* SEP firewall. But I have definiteyl confirmed that it is the wired machine which is killing the wireless clients.
Can you help me by explaining exactly which settings I need to change and where they are? Or is it possible my problem is similar but different?
Thanks!!
Kook
-
Here's the deal on SEP and Wireless networks: SEP's Network Defender module doesn't recognize the wireless clients and thinks they are a threat, so it then sends garbage to the wireless access point causing the WAP to think there is a failed NIC on the network or that there is an internal error, the WAP in an attempt to overcome the issue does a wireless restart. This can be caused by either a system running wireless or wired. I have experienced this issue with a wired system being the only one with SEP installed, once uninstalled all was well. This is both a flaw in SEP and in DLink firmware. Odd, the antivirus acting as a virus because it doesn't recognize the wireless network as a legitimate network. One possible solution is if you could disable the Network Defender module, however SEP does not have that option that I have seen. Just to clarify, SEP's Network Defender Module is a Host Based Intrusion Prevention System not the SEP Firewall module, however the firewall module could be misidentifying the IPv6 packet burst as a potential DDOS attack or rogue network adapter.
-
Bump.
I haven't looked at this in a long time since I made the original post. The post prior to this (#45) seems to have the best explanation so far. Because it seemed to have helped a good many people and no doubt saved a few routers from destruction I thought I'd bump it for others to see.