Bug 2785 - WPA2+AES fails with Cisco AP1200 w/v12.3(7)JA2
: WPA2+AES fails with Cisco AP1200 w/v12.3(7)JA2
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 28
: All Other
: P2 normal (vote)
: ---
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-04 11:42 UTC by Kevin Pearsall
Modified: 2008-12-18 11:38 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2006-01-04 11:42:47 UTC
Customer reported, but we do not have the hardware to test with.  Putting in as a placeholder for when we have a wireless driver update for SB2/3 firmware.

System:

SB3 wireless (firmware 28)
Slimserver 6.2.1 - 5194 - Windows XP - EN - cp1252
Cisco AP1200 802.11g wireless access point (model number AIR-AP1230B-E-K9,
field upgraded to 802.11g radio module, software version 12.3(7)JA2)

I have two new SB3's - one wired and one wireless. Congratulations on a
great product! 

My home wireless network has a Cisco AP as detailed above. This normally
runs in WPA2 mode and my wireless clients (Apple PowerBook and a couple of
Windows XP notebooks) can connect without problems. I have not been able
to connect the wireless SB3 using WPA2. However whenever I set the AP for
WPA TKIP I can connect fine. This is a typical message from the Cisco with
a failed attempt at WPA2 authentication from the SB:

000154: Dec 31 15:29:13.614
Debugging
Station 0004.2006.070a Authentication failed 

Whenever I set the Cisco to allow both WPA2 and WPA authentication and
change the SB3 to use WPA Personal I can then authenticate, e.g.:

001119: Jan 3 13:45:08.523
Information
Interface Dot11Radio0, Station 0004.2006.070a Associated KEY_MGMT[WPA PSK]

This is using the identical key. All I do is change the SB3 from WPA2
Personal to WPA Personal and I can connect.

Ideally I would like to use WPA2 alone instead of a mixed WPA/WPA2
environment. Any ideas what to do?
Comment 1 Richard Titmuss 2006-04-05 13:24:27 UTC
I have a fix that should appear in firmware 37.  Will update this bug when it's available for download.
Comment 2 Richard Titmuss 2006-04-06 06:05:44 UTC
Please try the latest nightly build with Firmware 37 and reopen if you have
issues.  Also, please note details of your configuration if you have not
already.