Release Notes 4.4.0.50

Release Notes, Version 4.4.0.50
8
•
An Access Controller IP address is not correctly displayed with CLI “show clients”
command. (20753)
• Access Controllers are not displayed in user interface when using Internet Explorer on
Windows 2003 Server. (20771)
• Retrieving client or session status may cause an Access Controller to reboot. (20730)
• The first time the 802.1X/WPA page is viewed, an error message is displayed stating that
WPA is not configured. To remove the error message, click the “Save” button. (19849)
• After performing a back-up on the Access Control Server, local host events are not logged.
Access Controller events are still logged after a back-up. (19801)
• Several minor error messages and minor information messages are added to the log when a
client attempts to access a restricted page. (19394)
• In order to perform a Trace Transaction when using Kerberos, the date and time settings must
match between the Access Control Server and the Key Distribution Center (KDC). (19908)
• A QoS Marking name may consist of 1 to 32 characters. If the name is one character long, it
cannot be the number zero (0). (19872)
• When creating or editing filters for Allowed or Redirected traffic and using a “!” or the word
“not” in front of the address, you must include a space between the “!” or the word “not” and
the address. For example: not @internal@. (19410)
• If you configure an IP address range for VPN tunneling (via the IP Address Assignment page
under the VPN icon) you must also set “Allow Static IP” in the relevant Access Policies
(including the Unauthenticated Access Policy) (18869)
KNOWN ISSUES AND BEHAVIORS
The following are issues that are known to exist with this software version. The number in
parentheses following the description is an internal tracking number.
• A Cisco Access Point using the Aironet series of protocols when connect downstream of an
Access Controller could originate traffic with the same source MAC address on multiple
VLANs or VLANs and untagged networks. This may trigger undesirable behavior on the
Access Controller causing it to detect the Access Point as roaming between VLANs. The
behavior of clients downstream of this Access Point is undefined. In order to avoid this
behavior it is recommended that either the Cisco Aironet series of protocols are disabled or
that these series of protocols exhibiting this behavior are blocked through traffic filters that
may be configured on the AP. (21090)
• Windows XP and 2000 clients in NAT mode may not accept a DHCP lease if a domain name
is not defined on the system. (21088)
• An Access Controller may erroneously display an IP address of 42.0.0.2 on the LCD panel.
(21055)
• After migrating to version 4.4, a 1000Base-SX port is described as Ethernet as opposed to
1000Base-SX or 1000Base-SX full-duplex. (20918)