• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

have to reenter network key everytime in order to obtain ip address

HaxorNubcake

Golden Member
On my dell 600m laptop with the standard intel Bsomethingsomething wireless card and the intel proset wireless client, I need to reenter the network key in the preferences every time I connect in order to obtain an IP address (after every standby, restart, etc).

The wireless router is the Buffalo HP one, using WPA2 PSK AES.

When I change the network key in the intel proset settings, I see that the key is different than the one that I entered the last time.

My desktop, using the windows client, is able to connect flawlessly every time.

Suggestions please?

Thanks.

 
Try using latest Intel client. Their client is actually VERY good.

What do you mean by you have to re-enter the key? Did you setup a profile in the client with all the security settings and key for this SSID? Also there is a troubleshooting log that you can look at....it's in the "intel wireless troubleshooter".
 
Originally posted by: spidey07
Try using latest Intel client. Their client is actually VERY good.

What do you mean by you have to re-enter the key? Did you setup a profile in the client with all the security settings and key for this SSID? Also there is a troubleshooting log that you can look at....it's in the "intel wireless troubleshooter".

Yeah I love the client...it worked flawlessly up until i flashed the router with dd-wrt and set the security to wpa2-psk only-aes.

I have a profile set up and I have to change the password everytime. The password that I see is not the same as the one I previously entered.

 
Yeah, hit intel and grab the latest client and see if that changes anything. I've not seen this issue before.

It could be (although it's not very likely) that the DD-WRT is doing odd stuff with beacons and association requests.
 
Back
Top