Print

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

[meichelman]

Thought I would post this for the benefit of anyone else having the same issue.

First, I have revision C hardware, and I've used either of the two latest firmwares.  Currently running 3.10 in beta form, though I'm fairly sure the 3.10 release will work just the same.

To get to the point: Use only numbers (e.g. 123456789) as the Pre-Shared Key for WAP or WAP2.  No spaces, no symbols, no letters.  I tried quite a few things before stumbling into this.

The symptom: Wired connections worked just fine.  Wireless would find and connect to the SSID, but I could not get an IP address from DHCP setup on the router.  Enabling logging on the router showed a continuous stream of requests for an IP by the laptops (yes, that's plural because I tried multiple laptops), but no IP address was received.  After repeated tries to request an IP address, the laptops would simply give up and disconnect from the SSID.

I updated the wireless drivers (all Intel components) just in case, but I had not had a problem connecting to any other access points/routers in the past.  Whenever I removed security from the 615, the laptops would connect and receive an IP just fine.  WPA, WPA2, TKIP, and AES combinations all exhibited the same problem.  (Continued on the next post..)

[meichelman]

I guess I hit some sort of character limit on the forums as well.

Anyway, I worked my way through a variety of Pre-Shared keys (short, long, spaces, hex characters only, etc.)  That's when I arrived at numbers only.  It just worked, every time.  I'm currently using WPA2/AES with a 23 digit number.  The wireless connection has been working and stable.  No disconnects, no loss of IP.

So, can't say why without looking at the code (which I'm sure Dlink won't be providing), but if you're having a similar issue try using only numbers as your Pre-Shared key.

As always, you're mileage may vary.

 # m a r t y