Windows 10: Wifi unable to connect to WPA2-PSK AES while open network is working just fine

Hello all.


I'm having this weird issue trying to get my desktop pc connected to my home wireless network via an usb wifi adapter. The wireless network is set up with WPA2-PSK AES security. I am able to connect to this network with my mobile phone while my usb wifi adapter is not. When trying to connect i see the following message: "No internet, secured".

I should mention i am using a cable to acces the internet for looking up info about this issue, whenever testing wifi i simply pull the cable.

Ipconfig reveals the IP adress of the wireless connection is 169.254.221.212. After looking this up it is clear to me this is caused by APIPA.

When setting up a static ip i'm still seeing the message "No internet, secured", but the MAC adress of the adapter is visible on my router config page - wireless connections. I can also see it in the gateway router at the DHCP client list, altough shown status is "not connected" and the IP adresses' last 3 digits don't match. When matching the static IP with the one seen in the gateway router i'm getting the same results.

I'm sure the password is correct


For the sake of troubleshooting, i disabled wireless security for a moment. Voila, no issues whatsoever. Wireless connection working perfectly fine. I am positive i pulled the ethernet cable. When switching wireless security back to WPA2-PSK AES i'm getting the APIPA IP again. After connecting the ethernet cable i am able to set up the mobile hotspot feature in Windows and using my phone i am able to connect and having acces to the internet.


I would like to get connected to my wireless home network set up with WPA2-PSK AES security. Can someone help to explain what i am doing wrong?

I hope the description of my problem is understandable, obviously the English language is not my first tongue.


Additional info:

-USB wifi chipset: Realtek RTL8188CTV (latest driver)

-Gateway router: Ziggo mediabox XL (aka UPC Horizon box)

-Wireless router: TP-Link TL-WR1043ND

:)

 

N95 WPA2 PSK Help

Hi guys,

At home I have a linksys WRT54G wifi router with WPA2 Personal PSK, and AES encryption. When I try to connect my N95 to it, it correctly detects my network is WPA/WPA2, but when I go to enter my pre-shared-key it will only let me enter 63 characters (my PSK
is 64 characters in length). If I enter a 64th character it lets me, but the "Ok" button dissapears.

I'm not sure the reason behind this since the same shared key works fine with my Wii and my other PC. Only thing I can think of is it doesn't let me specify the "AES" encryption anywhere. I've updated my firmware from version 12 to version 20.0.015 and it still
does the same thing.

I generated my key using wpa_passphrase and this is its output:

wpa_passphrase myessid password

network={

ssid="myessid"

#psk="password"

psk=659a8b4f7a0ee2be3005cd1eb5461b1ffd9b6dad6bb4b88a2b9b08d6971b9dbf

}

The "psk" is always 64 characters in length. Anyone any ideas what the problem might be?

Thanks.

 

WPA2/AES upgrade for WM2003

Yeah man, is there a way to connect using WPA2-PSK/AES? It's frustrating to compromise my entire network's security in order to make WM2003 compatible!

 

Can't connect to home wifi network with WPA2 AES

My Lumina 920 phone won't connect to my home wifi network which uses WPA2 preshared key with AES encryption. It says cannot connect to wifi network. I even copied the WPA2 password from my router's setup screen to a text file and uploaded this file to
my Skydrive. I opened the file on my phone and copied and pasted the password into the password field in the Wifi settings. My phone still won't connect. On my desktop PC if I copy and paste this password from the same text file I have no trouble connecting
to my wifi network. HOW DO I GET WINDOWS PHONE 8 TO CONNECT?!