Примечания к выпуску для Cisco Cisco Aironet 350 Wireless LAN Client Adapter
8
Release Notes for Cisco Aironet Client Utilities 2.70 and Driver 2.70 for Windows CE
OL-7683-01
Caveats
Step 25
Perform one of the following:
•
If your device is connected to a DHCP server, choose Obtain an IP address via DHCP or
Use server-assigned IP address and tap OK.
Use server-assigned IP address and tap OK.
•
If your device is not connected to a DHCP server, choose Specify an IP address or Use specific IP
address and follow these steps:
address and follow these steps:
a.
Enter the IP address, subnet mask, and default gateway address you want to assign to your device.
They can be obtained from your system administrator.
They can be obtained from your system administrator.
b.
Choose the Name Servers tab and enter the primary and secondary DNS and WINS you want to
assign to your device. They can be obtained from your system administrator.
assign to your device. They can be obtained from your system administrator.
c.
Tap OK.
The driver and client utility installation is complete. To verify that you have properly installed the driver
and client utilities, check the client adapter’s LEDs. If the installation was successful, the client adapter’s
green LED blinks.
and client utilities, check the client adapter’s LEDs. If the installation was successful, the client adapter’s
green LED blinks.
Note
Refer to the Cisco Aironet 350 Series Wireless LAN Client Adapters Installation and
Configuration Guide for Windows CE (part number OL-1375-05) for information on configuring
your client adapter.
Configuration Guide for Windows CE (part number OL-1375-05) for information on configuring
your client adapter.
Caveats
This section describes resolved and open caveats for client utility and driver release 2.70 for
Windows CE.
Windows CE.
Resolved Caveats
The following caveats are resolved in client utility and driver release 2.70 for Windows CE.
•
CSCeh13876—Windows CE .NET 4.2 scanners do not receive traffic after roaming if CMIC is
enabled
enabled
When a Windows CE .NET 4.2 scanner is configured for static WEP and CMIC, it may not be able
to receive traffic if it tries to scan a bar code right after roaming to a new access point. The problem
occurs only when CMIC is enabled on the access point.
to receive traffic if it tries to scan a bar code right after roaming to a new access point. The problem
occurs only when CMIC is enabled on the access point.
•
CSCeh36968—Windows CE devices cannot roam due to WEP decryption errors
Some Windows CE devices cannot roam when configured for Microsoft PEAP. The devices are able
to associate and authenticate to an initial access point but are then unable to roam due to problems
with WEP decryption.
to associate and authenticate to an initial access point but are then unable to roam due to problems
with WEP decryption.
•
CSCeh48513—Roaming with WPA does not work when client configured for certain EAP types
Windows CE .NET devices lose their connection while roaming when configured for WPA and any
EAP type other than LEAP or EAP-FAST.
EAP type other than LEAP or EAP-FAST.