Intel PRO/Wireless 2200BG fine with WEP, bad with WPA

Networking, Internet, Wireless

Networking, Internet, Wireless
From Wi-Fi to wired Ethernet, mobile broadband to modems: it's all spoken here.

Intel PRO/Wireless 2200BG fine with WEP, bad with WPA

  • I have a Latitud X1 with Intel PRO/Wireless 2200B.
     
    I tested with a 2 wifi-router Linksys and SMC Barricade.
     
    The Intel PRO/Wireless 2200B work fine in both routers without encryption or with WEP encryption (64 or 128 bits).
     
    But no work with WPA (Pre-Shared Key) encryption (AES or TKIP Algorithims).
     
    The routers work fine with others wifi-cards in WPA mode.
     
    The Wireless SSID Broadcast its Enable.
     
    I'm using Windows-XP Pro SP2 with the last soft/drivers of Intel 2200B, and the problem its the same using the Windows for management WI-FI or using the soft of the Intel.
     
    Any idea for use the WPA?.
     
     
     
     
     

    Message Edited by AlexGoldguin on 07-02-200608:32 AM

  • Since you mention AES and TKIP, I guess you're trying to set up WPA2.  This will work perfectly with the 2200BG, but WPA2 does require an update to XP. This hotfix is not offered automatically on Windows Update, so you will need to check that it is installed.

    Go to Control Panel | Add or Remove Programs. Make sure that "Show Updates" is checked, and look for

    Windows XP Hot fix KB893357

    If it's not installed, you can download it from here: http://support.microsoft.com/?id=893357

    Once you've rebooted, you should find that there is an option for WPA2-PSK when you try and set up your connection. Personally, I find that the Windows Zero Config works better than the Intel Pro/Wireless software -- it certainly uses less RAM.

    Hope that helps.

    Message Edited by rwm32 on 07-02-200605:01 PM

  • The latest drivers from dell or the latest drivers from intel?

    Latitude D430
    Dimension 9150
    Dell 1815dn Printer



  • rwm32 wrote:

    Since you mention AES and TKIP, I guess you're trying to set up WPA2.  This will work perfectly with the 2200BG, but WPA2 does require an update to XP. This hotfix is not offered automatically on Windows Update, so you will need to check that it is installed.

    Go to Control Panel | Add or Remove Programs. Make sure that "Show Updates" is checked, and look for

    Windows XP Hot fix KB893357

    If it's not installed, you can download it from here: http://support.microsoft.com/?id=893357

    Once you've rebooted, you should find that there is an option for WPA2-PSK when you try and set up your connection. Personally, I find that the Windows Zero Config works better than the Intel Pro/Wireless software -- it certainly uses less RAM.

    Hope that helps.

    Message Edited by rwm32 on 07-02-200605:01 PM




    Linksys has been implementing TKIP and AES under WPA long before there was WPA2, and the WPA2 update is not required if Intel PRO/Wireless client is in use.

     

      

    Please don't send questions about your issues to me by Private Messages; post them in the appropriate board so everyone can read. Thank you.

  • ..... Well, I didn't manage to get it working even with Pro/Wireless until after I'd installed the hotfix, but that could just be my ineptitude.  So perhaps I should have said that in my experience, the Intel 2200BG card simply wouldn't connect to my WRT54G v5 using AES without WPA2 (802.11i, I believe).  TKIP was OK, but then as I understand it, it's WPA as well as WPA2. :)
  • My 2200BG will connect to my Linksys WRT54G v1.0, WRT54G v3.1 and Buffalo WHR-HP-G54 on WPA-AES alone - there is no need for WPA2, but it will also connect on WPA2-AES as well if needed.  The WRT54G v5 is not a good basis for comparison - too many unresolved issues with this router.

     

      

    Please don't send questions about your issues to me by Private Messages; post them in the appropriate board so everyone can read. Thank you.

  • just flash them all to dd-wrt ... you don't even need a jtag for the v5s anymore :)

    Latitude D430
    Dimension 9150
    Dell 1815dn Printer



  • NemesisDB wrote:
    just flash them all to dd-wrt ... you don't even need a jtag for the v5s anymore :)


    Hahaaa... right you are :smileywink:

     

      

    Please don't send questions about your issues to me by Private Messages; post them in the appropriate board so everyone can read. Thank you.

  • Hi Thnk's for all

    The Linksys its a WRT54G v2.0 firm Alchemy 1.0 final and don't have WPA2,

    But after install Windows XP Hot fix KB893357

    work fine with WPA (AES or TKIP) with the Windows Zero Config, (the soft of Intel don't work with WPA-PSK).

     

     

  • alchemy is a joke.  i hope you didn't actually pay sveasoft money for that?  dd-wrt seems so much better...

    Latitude D430
    Dimension 9150
    Dell 1815dn Printer

  • Which 2200BG driver and client versions are you running?  The Intel PRO/Wireless client should work with either WPA-PSK TKIP and AES too (but my 2 WRT54G units are running HyperWRT firmware).

     

      

    Please don't send questions about your issues to me by Private Messages; post them in the appropriate board so everyone can read. Thank you.

  • I have the last driver of Intel 9.0.4.13 and the last client of the soft 10.1.1.3
     
     
    but don't work, only the WZC work fine with WPA-PSK TPKI or AES.
     
    I'm downloading the hyperWRT...:smileywink:
     

    Message Edited by AlexGoldguin on 07-02-200602:21 PM



  • esquire wrote:
    My 2200BG will connect to my Linksys WRT54G v1.0, WRT54G v3.1 and Buffalo WHR-HP-G54 on WPA-AES alone - there is no need for WPA2, but it will also connect on WPA2-AES as well if needed.  The WRT54G v5 is not a good basis for comparison - too many unresolved issues with this router.



    A few moments googling reveal that WPA implements a subset of 802.11i. AES is part of the full 802.11i spec, implemented as WPA2. So WPA-AES implementations might cause interoperability problems because they're not guaranteed compliant with 802.11i.   How fascinating, eh?



  • rwm32 wrote:


    esquire wrote:
    My 2200BG will connect to my Linksys WRT54G v1.0, WRT54G v3.1 and Buffalo WHR-HP-G54 on WPA-AES alone - there is no need for WPA2, but it will also connect on WPA2-AES as well if needed.  The WRT54G v5 is not a good basis for comparison - too many unresolved issues with this router.



    A few moments googling reveal that WPA implements a subset of 802.11i. AES is part of the full 802.11i spec, implemented as WPA2. So WPA-AES implementations might cause interoperability problems because they're not guaranteed compliant with 802.11i.   How fascinating, eh?




    Not, but it looks like you are confusing the issue.  WPA-PSK AES is not WPA2-PSK AES.
     
    Linksys (and a few other brands) added AES to WPA along with TKIP long before there was a final 802.11i or WPA2 - pls refer to the pre WRT54G v5 firmware version history.  It was never meant to be forward 802.11i compliant, but as an additional security feature to WPA-PSK TKIP, e.g., my Buffalo WHR-HP-G54 does not support WPA2, period but it has WPA-PSK AES.  Other brands only offer WPA-PSK TKIP.  To be 802.11i compliant, one needs to upgrade firmware to a newer version that includes WPA2 if and when they are released by the manufacturer.

     

      

    Please don't send questions about your issues to me by Private Messages; post them in the appropriate board so everyone can read. Thank you.



  • AlexGoldguin wrote:
    I have the last driver of Intel 9.0.4.13 and the last client of the soft 10.1.1.3
     
     
    but don't work, only the WZC work fine with WPA-PSK TPKI or AES.
     
    I'm downloading the hyperWRT...:smileywink:
     

    Message Edited by AlexGoldguin on 07-02-200602:21 PM




    Hmmm.... We're on the same version PRO/Wireless, but mine works with both TKIP and AES (either WPA or WPA2).  In fact, my network is currently implementing WPA-PSK AES because my new Buffalo router doesn't support WPA2.

    Do remember to perform a hard reset before and after you switch to HyperWRT:  http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=602

    Some even recommend flashing to factory firmware before switching to another custom firmware, but I didn't when I switched from Sveasoft to HyperWRT :smileytongue:

     

      

    Please don't send questions about your issues to me by Private Messages; post them in the appropriate board so everyone can read. Thank you.