Windows 7 cannot connect to WPA2 secured wireless network

Anonymous
2009-10-29T03:16:04+00:00

Hi all,

I am facing problems connecting to my company's network with Windows 7 x86 Enterprise edt.

The wireless network is WPA2 secured with TKIP and it normally prompts for my credentials when I was on Windows XP.

I have tried with several other machines with Windows 7 x64, also Enterprise edt and that prompts me for my credentials before I connect to the wireless network.

It seems that the problem is with the Windows 7 x86 as I am not the only person with this problem.

Could someone please advice what I can do to resolve this issue?

Thank you and Regards

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2009-11-14T20:35:59+00:00

I've solved the problem by following procedure:

My router configuration

Authentification mode: Shared key

WEP Encryption: WEP-64bits

Key index 1

Initially W7 won't connect to the wireless network.

My steps

I have Czech version of Windows 7, so, please note that text in English version might be slightly different from my translations.

  1. Goto network and sharing center
  2. Select Setup new connection or network
  3. Select Manually connect to wireless network
  4. Type network name, select WEp security and enter key, finally click Next
  5. Click Change connection settings
  6. Goto protection tab
  7. Select Security kind: Shared and Encryption kind: WEP
  8. Retype network key
  9. Precc OK and Close

This worked for me.

In case you already have some setup for your SSID, delete id before.


Đ.

Was this answer helpful?

9 people found this answer helpful.
0 comments No comments

42 additional answers

Sort by: Newest
  1. Anonymous
    2011-09-10T23:23:42+00:00

    Thanks it worked like a charm.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-06-26T05:32:35+00:00

    I have an Alienware M15x laptop with a Broadcom BCM3224 802.11a/b/g/n wireless card.

    I dual boot win7 64 bit and ubuntu (11.04 right now).

    On two separate wireless networks (the one at my work, and the one at my father-in-law's house) using WPA2, I cannot connect in windows, but can connect fine booted to ubuntu.

    in windows, it accepts the key, and then partially connects, showing "limited connectivity" but I can never actually connect and get network / internet access, etc.

    At work, if I change the encryption from AES (the one it shows up as) to TKIP, it doesn't connect at all.  I cannot change the settings on the wireless.

    The same thing happened at my in-laws.  I don't think it's driver related, but it seems to be network manager applet related. 

    Thanks

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-06-22T15:10:14+00:00

    As before, an explanation of how to use WEP does not answer the question of "Windows 7 cannot connect to WPA2 secured wireless network" no matter how helpful to anyone using Lynksys Wireless-G with WEP it is.

    well I have just changed my settings to WPA2-Personal, i just deleted the cached instance of my WEP wireless network on my Win7-32bit Fujitsu-Siemens S7220, and it connected just using my security key, this is the same laptop that gave me connection headach for 2 weeks when using WEP...

    Now the question is: why is it connecting without any hustle? could it be drivers? since i did connect before with WEP, could there have been driver exchange? Then i would suggest to anyone to try WEP then after successful WEP connection change to WPA2.

    Then that would be a workaround the WIN7 problem if ever it is a problem...(I am not yet convinced it is WIN7 problem)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-06-22T09:06:29+00:00

    well Gary, I havent tried the WPA encriptions however, I suggest instead of entering the security key as it is you use one of the generated keys...but first ensure there is no network already setup that may conflict with this connection...

    Was this answer helpful?

    0 comments No comments