Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pdmachado]

Hello, I own a DIR-655 that I purchased a few weeks back.  This unit has not worked properly since I purchased it.  So I exchanged it for a new one.  Same issue.  The issue is that as soon as I enable any type of wireless security (haven't tried WEP) I get an insane amount of wireless restarts.  I've tried everything else that I've found on the forums, including changing channels, dropping speed.  I have absolutely no 2.4GHz devices in the house.  I'm completely boggled as to what this could be.  The only resolutoin I have found is to remove Wireless Security altogether.  Of course in that case I need to put the router in Invisible mode. Can anyone give me any indication as to what can possibly be going on here.  My logs are posted below and any help would be very much appreciated.  I've never had these types of issues with any other devices I've ever owned.  Why I went to DLink, I don't know. 

14:46:09 2009 Dropped packet from 192.168.0.2 to 255.255.255.255 (IP protocol 6) as unable to create new session
[INFO] Fri Jan 16 14:46:09 2009 UPnP added entry 255.255.255.255 <-> xx.xx.xx.xx:49340 <-> 192.168.0.2:49340 TCP timeout:-1 'uTorrent (TCP)'
[INFO] Fri Jan 16 14:46:09 2009 Dropped packet from 192.168.0.2 to 255.255.255.255 (IP protocol 6) as unable to create new session
[INFO] Fri Jan 16 14:46:09 2009 UPnP added entry 255.255.255.255 <-> xx.xx.xx.xx:49340 <-> 192.168.0.2:49340 TCP timeout:-1 'uTorrent (TCP)'
[WARN] Fri Jan 16 14:45:38 2009 A network computer (xxxxxxxxxxxx-PC) was assigned the IP address of 192.168.0.80.
[INFO] Fri Jan 16 14:45:38 2009 MACHNET2: Wireless system with MAC address xxxxxxxxxxxxxx secured and linked
[INFO] Fri Jan 16 14:45:38 2009 MACHNET2: Wireless system with MAC address xxxxxxxxxxxxxx associated
[INFO] Fri Jan 16 14:45:38 2009 Above message repeated 1 times
[INFO] Fri Jan 16 14:45:38 2009 Wireless link is up
[INFO] Fri Jan 16 14:45:17 2009 Wireless link is down
[INFO] Fri Jan 16 14:45:16 2009 Wireless restart
[INFO] Fri Jan 16 14:45:16 2009 Disconnect all stations
[INFO] Fri Jan 16 14:45:16 2009 All Wireless shut down
[INFO] Fri Jan 16 14:45:14 2009 Wireless restart
[WARN] Fri Jan 16 14:43:53 2009 A network computer (xxxxxxxxxxxx-PC) was assigned the IP address of 192.168.0.80.
[INFO] Fri Jan 16 14:43:53 2009 MACHNET2: Wireless system with MAC address xxxxxxxxxxxxxx secured and linked
[INFO] Fri Jan 16 14:43:53 2009 MACHNET2: Wireless system with MAC address xxxxxxxxxxxxxx associated
[INFO] Fri Jan 16 14:43:53 2009 Above message repeated 1 times
[INFO] Fri Jan 16 14:43:49 2009 Wireless link is up
[INFO] Fri Jan 16 14:43:27 2009 Wireless link is down
[INFO] Fri Jan 16 14:43:27 2009 Wireless restart
[INFO] Fri Jan 16 14:43:27 2009 Disconnect all stations
[INFO] Fri Jan 16 14:43:27 2009 All Wireless shut down
[INFO] Fri Jan 16 14:43:25 2009 Wireless restart
[INFO] Fri Jan 16 14:43:19 2009 Blocked incoming TCP packet from 70.20.131.90:39612 to xx.xx.xx.xx:49340 as RST received but there is no active connection
[WARN] Fri Jan 16 14:42:47 2009 A network computer (xxxxxxxxxxx-PC) was assigned the IP address of 192.168.0.80.
[INFO] Fri Jan 16 14:42:47 2009 MACHNET2: Wireless system with MAC address xxxxxxxxxxxxxx secured and linked
[INFO] Fri Jan 16 14:42:47 2009 MACHNET2: Wireless system with MAC address xxxxxxxxxxxxxx associated

[EddieZ]

Have you looked through the various post in the forum that describe the same issue? If so, have you followed the different options to solve it. If not, please do so (unless somebody else is prepared to go into the issue once again).

[lookez]

Well, first I would try resetting (I mean in the button in the back of the device) , then upgrading the firmware*, then changing the SSID.

You could also test with another device like an iPhone or a friend's notebook so that you can see it's not a client-related problem.

It seems to me more like a firmware problem.

*Try upgrading the firmware from a different computer than the one you updated the firmware before, this could be a problem too.

Hope it helps you! =)

[lesviva]

SAME HERE!!! I am writing this because now I am completely pissed by this product!!!
Just got the router for a month. Wireless drops every few minutes.
Upgraded and downgarde to different FW versions 1.10, 1.11, 1.13, 1.20 and 1.21...
With all the methods, change advanced wireless settings... change channel.
Don't ever tell me is my ISP problem, because when the wireless disconnected, my pc with the wire still got the connection.
and also the WEP/WPA/WPA2, AES/TKIP things, I tried them with more than 20 times different combinations...
the only thing I so glad which is I didn't get ride off my Linksys 54g router after getting this piece of s***, and I put it back, no disconnected wireless anymore!
Thanks DLINK, you have done a great job to lose a customer!

[EddieZ]

SAME HERE!!! I am writing this because now I am completely pissed by this product!!!
Just got the router for a month. Wireless drops every few minutes.
Upgraded and downgarde to different FW versions 1.10, 1.11, 1.13, 1.20 and 1.21...
With all the methods, change advanced wireless settings... change channel.
Don't ever tell me is my ISP problem, because when the wireless disconnected, my pc with the wire still got the connection.
and also the WEP/WPA/WPA2, AES/TKIP things, I tried them with more than 20 times different combinations...
the only thing I so glad which is I didn't get ride off my Linksys 54g router after getting this piece of [exploitive deleted], and I put it back, no disconnected wireless anymore!
Thanks DLINK, you have done a great job to lose a customer!

Nice to hear you have some anger issues. Looking at the number of post you don't feel like getting help. Must be your ignorance, though you make it look you are the expert.

Do you want any assistance in solving your issue or is it a done deal?

[pdmachado]

EddieZ, sorry for getting  back to you so late,  but I can definitely relate to Lesviva.  This is extremely frustrating.  If I put a linksys in the exact same location where my Dlink is, it works without a problem.  I had a buddy of mine bring over a WRT310N and it worked flawlessly, with full WPA2.  Not sure what is going on with these units.  To answer your question, I've searched, searched and searched and I cannot find a solution to this problem after attempting several potential solutions.  If you wouldn't mind pointing me in the direction that you feel may solve my problem, please let me know.  It would be greatly appreciated.  Thanks.

Edit: I am running 1.21 without securespot.  I have an Intel 4965AGN network card in my laptop.  I have 2 of these routers....one runs 1.21 with securespot and the other 1.21 without securespot.  I've also gone from 1.11 right on through to the firmwares I'm at now.  No matter what I do, if I connect this laptop to either one I get the condition I mentioned above.  I haven't tried any other wireless devices to see if the issue is replicated with other devices.  I'm assuming it would though. 

[lesviva]

Nice to hear you have some anger issues. Looking at the number of post you don't feel like getting help. Must be your ignorance, though you make it look you are the expert.

Do you want any assistance in solving your issue or is it a done deal?

EddieZ, I am so sorry if you dont feel my frustrations... But thank you for your attention.
The reason I bought this router is because reviews around the internet are good. So that I make my wireless N solution to DLINK.
I am not a expert on this networking stuff, but I do come from an IT background. To me I just want a product which can be plug and play, and I think most of DLINK customers like it this way.
I had many routers before I got this DIR-655, none of them needs me to pay such efforts to them to give me a flawless wireless connection.
I am from Singapore, I know people got their routers to RMA for 3 times but still have the same problem. I think I have to say this my done deal with DLINK's router, at least for this one. I am going back with Linksys this time. But I will still keep my DNS-323 as it's a good product(plug and play)...

[lesviva]

one last thing, I just want DLink to understand that this must be something wrong with the Hardware or the Firmware, not the Settings.

[EddieZ]

I cannot judge any other device then my own. And that one works flawlessly with wireless media center (KiSS), Pocket PC, Smartphone, 2 laptops and a wireless photoframe. So your device may be defective, those things happen and it is always a sad thing. But if you have a look on the Linksys forums you will find the same complaints and issues on those Linksys products, although your Linksys stuff worked OK.

Everybody wants a plug and play device. Unfortunately we don't live in a perfect world and looking at all possible network configurations and combinations (devices, OS'es, laptop chipsets etc) , the perfect device will be a different one for each and every one of us.

[funchords]

All:

TIP: Change your SSID to something you've never used before ANYTIME you change your wireless security or some other connection parameter.  Then completely restart the AP (reboot from the Tools - System menu or simply remove and restore power).  Then on your wireless clients, erase all stored client  profiles, reboot, and reassociate with the "new" AP.  This practice will avoid many of the problems being described here. 

If this helps, it's because
1.  Changing the SSID forces the client to create a new profile instead of looking up settings in an old one. Those older settings may be incorrect or corrupt.
2.  Restarting the AP clears out any 802.1x (including WPA, WPA2) security lockouts of any clients
3.  Erasing the stored client files keeps the clients from seeking other clients once in a while.
4.  Rebooting the client clears out any 802.1x (including WPA, WPA2) security lockouts of any APs
5.  Reassociating with the "new" AP creates a new profile with the current settings

[funchords]

14:46:09 2009 Dropped packet from 192.168.0.2 to 255.255.255.255 (IP protocol 6) as unable to create new session

This is a very unusual error. It means that it is making an IP broadcast, which it does when it's looking for an IP from a DHCP server.  The DIR-655 handles this fine, normally.  So other than a DHCP broadcast, any idea what 192.168.0.2 might be doing here? 

If 192.168.0.2 is turned off, do you continue to have problems with the DIR-655?

[pdmachado]

Funchords, I've tried that.  I actually attempted to connect my notebook after a fresh re-installation of Windows Vista.  It immediately did the same thing.  Not sure what else to try here...   There's only two wireless clients connecting to this AP.  The laptop I just referred to and a PS3 but the PS3 is off most of the time.  192.168.0.2 is actually a windows 2008 server connected to a Linksys VPN router RV042.  The DIR-655 in question here is issuing IP addresses and so is the RV042 in two different ranges.  But 192.168.0.2 is statically assigned to the server with the RV042 set as it's gateway and DNS server.

Just to reiterate, I only wireless restarts when I turn on wireless security.  I haven't tried WEP and I don't want to.  But any of the WPAs cause the problem. 

[EddieZ]

Funchords, I've tried that.  I actually attempted to connect my notebook after a fresh re-installation of Windows Vista.  It immediately did the same thing.  Not sure what else to try here...   There's only two wireless clients connecting to this AP.  The laptop I just referred to and a PS3 but the PS3 is off most of the time.  192.168.0.2 is actually a windows 2008 server connected to a Linksys VPN router RV042.  The DIR-655 in question here is issuing IP addresses and so is the RV042 in two different ranges.  But 192.168.0.2 is statically assigned to the server with the RV042 set as it's gateway and DNS server.

Just to reiterate, I only wireless restarts when I turn on wireless security.  I haven't tried WEP and I don't want to.  But any of the WPAs cause the problem. 

I am starting to think that your network config might cause the behaviour. If the DIR is issuing IP's on the same subnet as the RV042 then you have trouble. Having more routers in the network can cause more serious issues though. Could you give a detailed network map?

[pdmachado]

Eddie, I understand that....however network communication has never been an issue.  I will compile a network map and provide it to you.  My only issue is the wireless restarts.  Seems that as soon as turn on wireless security my laptop disconnects, my PS3 will disconnect as well.  With Visibility off (obviously) and running unsecured, it works flawlessly.

My map is as follows:

RV042: wan port connnected to WAN switch with static IP from ISP : gateway is the dsl modem.  Internal network is configured with 192.168.0.3 as ip and DHCP in the range 100 to 130.  Lan side is connected to a LAN switch connecting the LAN side of all my routers.

DIR-655 : wan port connnected to WAN switch with static IP from ISP : gateway is the dsl modem.  Internal network is configured with 192.168.0.10 as ip and DHCP in the range 50 to 80.  Lan side is connected to a LAN switch connecting the LAN side of all my routers.

DIR-655 : wan port connnected to WAN switch with static IP from ISP : gateway is the dsl modem.  Internal network is configured with 192.168.0.20 as ip and DHCP in the range 150 to 80.  Lan side is connected to a LAN switch connecting the LAN side of all my routers.

[EddieZ]

As more threads show, consoles like Wii and PS3 cause these issues. If I remember well, you can configure the PS3 so it does not cause the wireles restarts. Don't know what though, I don't have one but with a 655 forum search you might trace it.