Cisco Cisco Aironet 350 Wireless LAN Client Adapter 릴리즈 노트
31
Release Notes for Cisco Aironet 802.11a/b/g Client Adapters (CB21AG and PI21AG) Install Wizard 2.0
OL-7578-01
Caveats
•
CSCeg81842—Client unable to get IP address
The client sometimes fails to get an IP address when using power save mode. This issue is resolved
in driver 2.0.
in driver 2.0.
•
CSCin73086—“show dot11 adjacent-ap” does not show information about previous AP
The “show dot11 adjacent-ap” frame does not display any information about the access point to
which the client adapter was previously associated. This issue is resolved in driver 2.0.
which the client adapter was previously associated. This issue is resolved in driver 2.0.
•
CSCin74956 and CSCee69323—Client fails to get IP address when CCKM CKIP+CMIC is used
with 12.2(15)JA
with 12.2(15)JA
Clients fail to obtain an IP address when attempting to associate to an access point that is running
Cisco IOS Release 12.2(15)JA and is configured for CCKM with CKIP+CMIC. To work around this
problem, configure the access point for CCKM with TKIP+Michael MIC rather than CKIP+CMIC
or upgrade your access points to Cisco IOS Release 12.2(15)XR or greater. This issue is resolved in
driver 2.0.
Cisco IOS Release 12.2(15)JA and is configured for CCKM with CKIP+CMIC. To work around this
problem, configure the access point for CCKM with TKIP+Michael MIC rather than CKIP+CMIC
or upgrade your access points to Cisco IOS Release 12.2(15)XR or greater. This issue is resolved in
driver 2.0.
Resolved ADU Caveats
The following caveats are resolved in ADU 2.0
•
CSCed72076—Channels 13 and 14 not available in ad hoc mode for Japanese cards
The Japan regulatory domain supports channels 1 through 14 for IEEE 802.11b communications and
channels 1 through 13 for IEEE 802.11g communications. However, channels 13 and 14 do not
appear in the Channels drop-down list on the ADU Profile Management (Advanced) window for
client adapters that are configured for use in Japan. This issue is resolved in ADU 2.0.
channels 1 through 13 for IEEE 802.11g communications. However, channels 13 and 14 do not
appear in the Channels drop-down list on the ADU Profile Management (Advanced) window for
client adapters that are configured for use in Japan. This issue is resolved in ADU 2.0.
•
CSCee06008—ADU-activated PEAP (EAP-MSCHAP V2) machine authentication fails domain logon
Machine authentication does not work when you activate an ADU profile that has PEAP
(EAP-MSCHAP V2) enabled. Users without cached credentials cannot log into the Windows
domain. You can resolve this problem by performing one of the following:
(EAP-MSCHAP V2) enabled. Users without cached credentials cannot log into the Windows
domain. You can resolve this problem by performing one of the following:
–
Selecting the Host Based EAP 802.1x EAP Type option in ADU and then configuring PEAP
settings in the Microsoft Wireless Configuration Manager
settings in the Microsoft Wireless Configuration Manager
Note
Refer to the
for details.
–
Configuring your client adapter for Protected EAP (PEAP) authentication in the Microsoft
Wireless Configuration Manager in Windows XP rather than in ADU
Wireless Configuration Manager in Windows XP rather than in ADU
•
CSCee22943—Signal strength displayed incorrectly
The Signal Strength values on the Available Infrastructure and Ad Hoc Networks window in ADU
are not signal strength values but signal-to-noise ratio (SNR) values. In ADU 2.0, the Signal
Strength heading has been appropriately renamed Signal-to-Noise Ratio (SNR).
are not signal strength values but signal-to-noise ratio (SNR) values. In ADU 2.0, the Signal
Strength heading has been appropriately renamed Signal-to-Noise Ratio (SNR).
•
CSCef85128—Windows login fails and registry change occurs
Upon reboot, a computer running Windows 2000 fails the Windows login when the user tries to log
into a domain. In addition, part of the registry is changed. This issue is resolved in ADU 2.0.
into a domain. In addition, part of the registry is changed. This issue is resolved in ADU 2.0.
•
CSCeg74346—PEAP (EAP-MSCHAPV2) authentication fails with self-signed certificates
PEAP (EAP-MSCHAP V2) authentication fails when ACS 3.3.2.2 is used with self-signed
certificates. This issue is resolved in ADU 2.0.
certificates. This issue is resolved in ADU 2.0.