If you have a Cisco card, try to go to Atheros websie to find drivers. Don't expect Cisco come up with ACU or ADU for one more month at least.
Apparently the XP version of the Atheros client does work under Vista (seen in the wild on a Fujitsu tablet). The Cisco ADU may work as well. If anyone is willing please try installing the ADU on Vista and report back. You'll get points from me FWIW.
Update ... Intel just told me that they plan to release supplicant support (incl. LEAP/EAP-FAST) (on Intel 2200/2915/3945/4965) on Vista in their new 11.1 wireless client release, targeted for late March/April.
Cisco yet not have any plan to support Vista ...May be in future WINBU ...plan to release ADU for Cb21AG card to support vista.
Aethors client are not supporting LEAP on Vista ...( tested ). You can use client to just have basic wireless connectivity.
I have tested PEAP ms-chap V2 and it supported by on vista..
So I think for now you can either be on Xp or need to switch to Microsoft propriety security like PEAP with Ms chap V2
Intel Proset Wireless 11.1 is out but not include LEAP support for Windows Vista. I think CISCO must support it!! Many schools uses LEAP and isn't easy that they will change authentication..
I wait for news...
This is really frustrating. I need the Aironet client to work with my laptop that has Vista, and the medical center I need to connect to won't change from LEAP. What is Cisco going to do when lots of people have Vista? I don't have a Cisco card. I was told by the medical center IT staff that the internal wireless card that my laptop has should work with the Aironet utility.
I think using internal wireless card with Aironet Client Utility is completely misleading. You can look this up for yourself at http://www.cisco.com/en/US/products/hw/wireless/ps4555/prod_release_note09186a00807ab153.html#wp32270
I think the medical center people should be more co-operative by letting you use Static WEP instead of LEAP.
The problem with UCSF Medical Center is getting them to cut through all the red tape to use a different method. Plus, if it is something they have to change on their servers, I can pretty much forget about ever finding the right person to do it, and I can't imagine them doing it for just me.
> I think the medical center people should be more co-operative by letting you use Static WEP instead of LEAP.
I think Cisco should be more co-operative by supporting Vista!
Amen brother! I am hearing that Vista support will be delivered via a CCX5 "Toolkit" to hardware vendors (since when is OS support part of CCX?) and that this is not expected until Summer or later.
Having a hospital on LEAP is like having unprotected sex in a third world opium den.
Hopefully, someone will inform them of this before somebody ends up with a handful of AD credentials. Perhaps this will entice them to use PEAP at least, which should work on your laptop!
Amen to that. Here's a video on exactly how to crack LEAP using only Windows XP/sp2 and free tools. It's a snap.
This is fantastic!
I support a network with 400 Cisco WAPs and approximately 5000 users.....all using LEAP!
I guess the good news is that we won't have to spend the money we had planned to upgrade all the WAPs to 802.11g.
If we are forced to migrate away from LEAP to PEAP, meaning I basically have to redesign the entire network infrastructure, we can start purchasing cheaper equipment from another vendor, and stop forcing my clients to buy Cisco cards!
This is kinda stupid: We have a university network with approx. 1000 users authenticating to the wireless network via PEAP but there's no client for Vista available. Most of them have Intel Notebooks and there software does not have this profil manager Windows XP got.
What can we do except waiting?
Both M$ and Cisco worked on PEAP(v0). Cisco just took it a step further and developed PEAPv1 which has no native Windows support.
Either way, isn't PEAPv0 preferred over LEAP? One of our customers wants to migrate from LEAP to PEAPv0 because of its native Windows support.
Looks like we will have to wait longer. Cisco is doing a "Microsoft EAP Certification" process to get EAP-FAST working on Vista...
Please help!, still no leap support for vista??? I work for a hospital. They WONT change from leap and there are hundreds of us who have migrated to vista but are stuck with no wireless access. I guess we either have to downgrade to xp or wait until another company like meetinghouse develops the software.
What you say doesn't make any sense to me.
If you are using PEAP-MSCHAPv2 then, by definition, you are not using LEAP. There is no support for MSCHAPv2 over LEAP.
What does LEAP configured WAPs mean? Are you saying that you have an SSID configured for LEAP on an access point? There is no EAP type specific information on the AP or WLC, the EAP type is between the client and the RADIUS server. The AP or WLC simply passes the EAP messages directly between the wireless client and the RADIUS server and visa versa.
For example, you won't find the word LEAP anywhere on a configuration web page for an autonomous IOS AP or the centralized wireless controller other than for the local RADIUS server.
You know, you are right. The word LEAP is not anywhere in an autonomous IOS AP. We use LEAP authentication between our clients and an ACS server. I was just pointing out the fact that PEAP-MSCHAP works with our current SSID configuration used by our LEAP clients.
So although it doesn't make sense to you, it does work.
Thanks for the clarification. It is true that *IF* the RADIUS server is configured to allow multiple 'inner' EAP types simultaneously (LEAP, PEAP, EAP-MD5, EAP-TLS, etc) then this will work. The wireless controller or autonomous AP is configured just for 'outer' EAP, regardless of 'inner' EAP type.
This may change so your mileage may vary. Note that several available RADIUS servers (freeRADIUS, idEngines, Funk/Juniper) can allow specific 'inner' EAP types per authenticator, unlike ACS which is a global setting.
For those watching this thread, I thought I'd post that Intel appears to have updated their drivers to support Cisco authentication mechanisms like EAP-FAST and LEAP in Vista. Version 184.108.40.206 of the IntelÂ® PROSet/Wireless Network Connection Software for Windows Vista now includes this support, as well as all the other CCXv4 perks (though now I want CCXv5 from Intel... the grass is always greener, I guess).