D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: mrwinky on January 21, 2009, 07:54:04 AM
-
I've had this router for 8 months with no issues till Xmas, I replaced it with WBR 2310 (for my kids xbox for the past 3 weeks) now I'm trying to make this work. But I'm getting kicked ever 5min or so and checking the log it says PC with Mac address xxxxx Received Deauthentication.
Dir-655
Hardware A2
Firmware 1.21 11/08 one.
I've been reading that my router is hooped and I should contact Dlink on it.
Any ideas?
-
How's your wireless environment? Cordless phones or anything running at 2.4GHz will cause interference. How many clients are connected to the router wired and wireless?
-
......the log it says PC with Mac address xxxxx Received Deauthentication.....
If you only have a problem over the wireless network only, please look at the PC(s) and check the Internet security software. When I was using Norton 360 v2, I must tell the software to "trust" my wireless SSID name.
-
Remove the saved wireless profile in that computer that is deauthenticating.
Reboot that computer
Restart the DIR-655 (remove and restore power)
If this helps, the deauthentications were being caused by a saved wireless profile in the client that contained wrong information about your AP.
-
I see the following deauthentication log message every half hour:
Wireless system with MAC address 0023126D90AA disconnected for reason: Received Deauthentication
This is from my iPhone and coincides with it's 1/2 hour email check. As far as I can tell this is normal for this client. I would check to make sure that the MAC is in fact the Xbox and make sure the connection drops coincide with the deauthenticate log messages.
-
I see the following deauthentication log message every half hour:
Wireless system with MAC address 0023126D90AA disconnected for reason: Received Deauthentication
This is from my iPhone and coincides with it's 1/2 hour email check. As far as I can tell this is normal for this client.
You are right that deauthenticate log messages alone aren't a problem. My Wii deauthenticates every few minutes when not in active use -- that's normal and doesn't affect anything.
In the O.P.'s case, however, he was getting disconnected while using the device.
-
When looking at the really persistent disconnects/deauthentifications it strikes me that Wii, PS2/3 and Xbox cause 90% of those errors. Just an observation, but still a curious one. It might be worth a try to see if these errors also occur with other brands.
-
I am having exactly the same problem. Has anyone come up with a resolution that maybe wasn't posted here? I have an iPhone 3G. I think the wireless issue started around the time I upgraded the iPhone's firmware to 3.0, but I could be mistaken.
-
have an old di-634m that started doing this after we lost power. after fooling around with it, i noticed that the channels were jumbled up. changed my 3945abg to same channel as router and unchecked the "auto channel select" box and presto. Good as new.
-
If you only have aipad2 Chargers (http://www.ebelow.com/ipad-2-chargers.html) problem over the wireless network only, please ipad2 Sleeve (http://www.ebelow.com/ipad-2-sleeves.html) look at the PC(s) and check the Internet security software. When I was using Norton 360 v2, I must tell the software to "trust" my iphone 4 case (http://www.ebelow.com/iphone-4-cases-iphone4-case.html)
wireless SSID name.
If this helps, the deauthentications were being caused by a saved wireless profile in the client that contained wrong information about your AP.
-
When you check the "Status" -> Logs -> Log Details
Wireless system with MAC address XXXXXXXXXXXX disconnected for reason: Received Deauthentication ???
A workaround solution:
1. Setup -> Network Settings : Check the DHCP Reservations List
2. Do NOT Add DHCP Reservation for your device.
That's it. ;D
-
Is recommended to ADD reservations for ALL devices. The status message for this is only a status message regarding that the router received a disconnection from the device. It doesn't impact router operation or performance. It's only a status message as is designed to report this.