D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: geeky on November 11, 2008, 04:55:53 PM
-
I have been wrestling with the DIR-655 and my Macbook Pro for over a month now, and I'm really hoping someone can tell me how to solve these issues.
My main issue is this: Most of the time when the Macbook wakes from sleep, it does not get a valid IP address from the router - only a self assigned IP. The Macbook worked just fine with our previous wireless router and works fine on other wireless routers (for example, a DIR-625 with WEP encryption). We have other computers (PCs) using the wireless connection that do not have this problem. The problems occur even if the Macbook is given a static IP.
Router:
DLink DIR-655
G only
manual channel (1)
broadcast SSID
WPA - Personal / WPA - TKIP
Firmware 1.20
Macbook Pro 3,1:
OS X 10.4.11
2.4GHz Intel Core 2 Duo
Airport Extreme 1.4.4
Sometimes turning on/off the airport will help reestablish the connection. Other times, the only thing that works is rebooting the Macbook. When looking at the logs on the router, I see a lot of this:
"Router: Wireless system with MAC address 000000000000 disconnected for reason: Received Deauthentication"
Usually once I get a valid IP on the Macbook, the connection is rock solid until I put the Macbook to sleep again. However, to add insult to injury, we have started experiencing random dropped connections on both the Macbook and the PCs in the last few days.
Did I get a bum router, or is there something else I can try? I'm extremely frustrated and starting to regret my purchase. :-\
-
If this SSID you are using is the same SSID that you have used when you were using WEP instead of WPA, then I would change the SSID to something you have never used before. After changing the SSID, you will need to reconfigure your wireless clients to connect to it.
If this helps, it is because the wireless client's profile for your Access Point was incorrect or corrupted, probably because it was first configured under the old set of AP parameters and didn't completely shift to the new set. While I don't know if Apple's products were ****e to this, many products suffered from this when WPA was new.
-
If this SSID you are using is the same SSID that you have used when you were using WEP instead of WPA, then I would change the SSID to something you have never used before. After changing the SSID, you will need to reconfigure your wireless clients to connect to it.
It is the same SSID as before and I haven't tried changing it yet, so I'll give thatt a try this afternoon and report back. Thanks! :)
-
Also remove the encryption and try to connect.
-
OK an update.
Changing the SSID did not improve anything.
Removing the encryption did improve the Macbooks ability to connect after sleep. However, I don't want to leave my router unencrypted for obvious reasons.
Any other suggestions?
-
What encryption are you using?
-
What encryption are you using?
WPA - Personal / WPA - TKIP. I should note that changing to WEP seems to help, but the signal is not as strong with WEP, and I'd prefer to use WPA for the stronger encryption.
-
Are you sure your Macbook supports that level of encryption?
-
Are you sure your Macbook supports that level of encryption?
It definitely supports WPA as I can get the connection to work, but only sometimes. Like I said before, rebooting the Macbook always gets me a working connection, but after putting it to sleep it's hit or miss. I usually have to try connecting between 5 and 10 times before I get a valid IP and can use the Internet (compared to with WEP, where it connects automatically on the first try after I wake it up).
-
Hmm, that sounds like a beacon issue. Have you tried changing the beacon interval?
-
Hmm, that sounds like a beacon issue. Have you tried changing the beacon interval?
No? What is a beacon interval and how do I change it?
-
When you log into your router, go to the Advanced Section, and then select "Advanced Wireless" on the left side.
There you have options for transmit power, RTS Thresholds, etc.
D-Link recommends setting your beacon period to 80, rather than the default 100.
Edit: What's the last Airport Extreme update did you get? And it's able to use "N" right?
Review this: Router Troubleshooting Suggestions and Tips (http://forums.dlink.com/index.php?topic=54498.0)