D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: obkook on December 31, 2009, 12:37:23 PM
-
This is driving me absolutely crazy and has rendered my laptops unusable for web related work.
I have DIR-655 A4 with 1.32NA 11/05 firmware on it (trying to solve this very problem)
I have 6 wired connections:
* 2008 server R2 as Hyper-V server
* Win7 VM as internet browsing machine
* Win7 VM as music library and SlimDevices server
* Win7 Media PC
* wireless music streaming device (Squeezebox2)
* Sony PS3
I have 4 wireless connections:
* my laptop
*wife work laptop
* wife Netbook
The problem, like so many others around here, is that my wireless connection drops every few minuets. Looking at the log, I can see that there is a Wireless restart every few minutes as well.
The other thing "fishy" in the log is a tremendous number of "UpNP renew entry", and a substantial number of "Blocked incoming UDP packet"
I updated to the newest firmware, am running WPA-2 security, turned off secure zone, and unchecked DNS relay. How can I fix this dog? As it is, it's useless to me except as a wired router...
Thanks,
Kook
[INFO] Thu Dec 31 12:30:55 2009 Above message repeated 2 times
[INFO] Thu Dec 31 12:30:54 2009 UPnP renew entry 255.255.255.255 <-> 98.210.171.101:63006 <-> 192.168.0.197:63006 UDP timeout:0 'Teredo'
[INFO] Thu Dec 31 12:30:49 2009 UPnP renew entry 255.255.255.255 <-> 98.210.171.101:56223 <-> 192.168.0.112:56223 UDP timeout:0 'Teredo'
[INFO] Thu Dec 31 12:30:30 2009 Wireless restart
[INFO] Thu Dec 31 12:30:15 2009 UPnP renew entry 255.255.255.255 <-> 98.210.171.101:63006 <-> 192.168.0.197:63006 UDP timeout:0 'Teredo'
[INFO] Thu Dec 31 12:30:07 2009 Blocked incoming UDP packet from 64.238.16.66:17758 to 98.210.171.101:20687
[INFO] Thu Dec 31 12:30:07 2009 UPnP renew entry 255.255.255.255 <-> 98.210.171.101:56223 <-> 192.168.0.112:56223 UDP timeout:0 'Teredo'
[INFO] Thu Dec 31 12:30:03 2009 Blocked incoming UDP packet from 64.238.16.66:17758 to 98.210.171.101:20687
[INFO] Thu Dec 31 12:30:01 2009 Above message repeated 1 times
[INFO] Thu Dec 31 12:29:57 2009 Wireless restart
-
Anybody? Bueller? Bueller?
Seriously, I just counted the number of restarts in my log in the last hour and it was 20 restarts! That's an average of once every 3 minutes!!! You've got to be kidding me!
Do I have something absolutely wrong in the configuration, or is it something else?
-
do u have wifi protected setup enabled or disabled? what is the TRANSMISSION rate set to? in the advanced TAB, under ADVANCED WIRELESS, do u have "extra wireless protection" enabled or disabled?
-
Like you, my wireless connection constantly restarts . At least I now know, I'm not the only one. I contacted Tech Support a couple of weeks ago & told them I had a new unopened Netgear router that I was about to replace this friggin D-Link with. I was assigned to a USA tech support person. He had me adjust my RTS & Fragmentation Threshold to 2100. Don't know if that was an educated suggestion or merely a "hail Marry" on his part. Seemed to improved things slightly, but I'm still being plaqued with constant restarts. Trying the forum approach before I completely abandon the D-Link.
-
coastle, do u have wifi protected setup enabled or disabled? what is the TRANSMISSION rate set to? in the advanced TAB, under ADVANCED WIRELESS, do u have "extra wireless protection" enabled or disabled?
-
and also , what do u have your CHANNEL WIDTH set to? 20mhz or 20mhz/40mhz auto?
-
Thanks for the reply!!
For me:
WiFi protected setup - enabled
Extra Wireless Protection - checked
Transmission Rate - Best (Automatic)
Channel Width - 20 MHz
Do you recommend changing any of these settings?
-
yes , change the WIDTH to auto 20/40mhz, and turn of Wifi protected setup and extra wireless protection, tell me if it helped anything.
-
and btw just so u know DNS RELAY should be enabled , not disabled.
-
OK, all changes made, and I'll enable some of the wireless clients now and see how things go. I report back in about 20 min or so.
-
nope, I can already tell that it hasn't made a difference - 19 wirelss restarts in the past 5 minutes.
-
Wow, sounds frustrating.
-
This is driving me absolutely crazy and has rendered my laptops unusable for web related work.
I have DIR-655 A4 with 1.32NA 11/05 firmware on it (trying to solve this very problem)
I have 6 wired connections:
* 2008 server R2 as Hyper-V server
* Win7 VM as internet browsing machine
* Win7 VM as music library and SlimDevices server
* Win7 Media PC
* wireless music streaming device (Squeezebox2)
* Sony PS3
I have 4 wireless connections:
* my laptop
*wife work laptop
* wife Netbook
The problem, like so many others around here, is that my wireless connection drops every few minuets. Looking at the log, I can see that there is a Wireless restart every few minutes as well.
The other thing "fishy" in the log is a tremendous number of "UpNP renew entry", and a substantial number of "Blocked incoming UDP packet"
I updated to the newest firmware, am running WPA-2 security, turned off secure zone, and unchecked DNS relay. How can I fix this dog? As it is, it's useless to me except as a wired router...
Thanks,
Kook
[INFO] Thu Dec 31 12:30:55 2009 Above message repeated 2 times
[INFO] Thu Dec 31 12:30:54 2009 UPnP renew entry 255.255.255.255 <-> 98.210.171.101:63006 <-> 192.168.0.197:63006 UDP timeout:0 'Teredo'
[INFO] Thu Dec 31 12:30:49 2009 UPnP renew entry 255.255.255.255 <-> 98.210.171.101:56223 <-> 192.168.0.112:56223 UDP timeout:0 'Teredo'
[INFO] Thu Dec 31 12:30:30 2009 Wireless restart
[INFO] Thu Dec 31 12:30:15 2009 UPnP renew entry 255.255.255.255 <-> 98.210.171.101:63006 <-> 192.168.0.197:63006 UDP timeout:0 'Teredo'
[INFO] Thu Dec 31 12:30:07 2009 Blocked incoming UDP packet from 64.238.16.66:17758 to 98.210.171.101:20687
[INFO] Thu Dec 31 12:30:07 2009 UPnP renew entry 255.255.255.255 <-> 98.210.171.101:56223 <-> 192.168.0.112:56223 UDP timeout:0 'Teredo'
[INFO] Thu Dec 31 12:30:03 2009 Blocked incoming UDP packet from 64.238.16.66:17758 to 98.210.171.101:20687
[INFO] Thu Dec 31 12:30:01 2009 Above message repeated 1 times
[INFO] Thu Dec 31 12:29:57 2009 Wireless restart
Hi
I can se you have IPV6 turned on try to only use IPV4 and try to
turn brodcast on 255.255.255.255 is a broadcast packet.
Some hints to test !
Regards
kthaddock
-
OK, I have narrowed this down a little bit.
The Problem is caused by my wired PC. I have a wired 2008 R2 server running Hyper-V with 2 VM's running iside it, both also attached to the router (via the host NIC).
I little further digging has shown others on this forum to likewise identify a wired PC to be the cause of a "wireless restart" issue. http://forums.dlink.com/index.php?topic=5851.0 (http://forums.dlink.com/index.php?topic=5851.0) in particular.
In the linked post, he was able to narrow it down to the Symantec Endpoint Protection firewall, and guess what? I have SEP on this machine as well!
It also occurred to me that the VM's might be somhow confusing things a bit, so I just shut them down and there was no change. Shutting down the entire server immediately changed from having an average of 2 wireless restarts EVERY MNUTE to none in the past hour.
Restarting the server immiately started the wireless restarts as well.
So, my question is, does anyone know what specific changes I could make to SEP to stop this?
BTW - thanks for the IPv6 suggestion - I may try that too if I can't do something with the SEP plan...
-
Here is another potential piece of the puzzle. This was on the DIR-825 as reported on this forum, but it seems to be the same phenomenon.
http://forums.dlink.com/index.php?topic=8272.0 (http://forums.dlink.com/index.php?topic=8272.0)
-
I seem to be having a conversation with myself, but I hope it will help someone in the future.
So, just disabling SEP did not seem to work, so I decided to completely uninstall it. Problem fixed.
I guess I'll have to look into another virus program as it will be cheaper than changing out the router, but this seems to be a pretty known and documented problem - shame on DLINK for not putting a sticky on it or making an announcement or FAQ.
-
If you have Symantec or SEP, install the packet without firewall and use the windows firewall. The firewall in SEP has many problems. Symantec recommend to us to uninstall the syamntec firewall.
OK, I have narrowed this down a little bit.
The Problem is caused by my wired PC. I have a wired 2008 R2 server running Hyper-V with 2 VM's running iside it, both also attached to the router (via the host NIC).
I little further digging has shown others on this forum to likewise identify a wired PC to be the cause of a "wireless restart" issue. http://forums.dlink.com/index.php?topic=5851.0 (http://forums.dlink.com/index.php?topic=5851.0) in particular.
In the linked post, he was able to narrow it down to the Symantec Endpoint Protection firewall, and guess what? I have SEP on this machine as well!
It also occurred to me that the VM's might be somhow confusing things a bit, so I just shut them down and there was no change. Shutting down the entire server immediately changed from having an average of 2 wireless restarts EVERY MNUTE to none in the past hour.
Restarting the server immiately started the wireless restarts as well.
So, my question is, does anyone know what specific changes I could make to SEP to stop this?
BTW - thanks for the IPv6 suggestion - I may try that too if I can't do something with the SEP plan...
-
Thanks, but the SEP I had installed was the version without the firewal, and the problem was *still* fixed by uninstalling it.