Release Notes 4.1.4.4

Release Notes, Version 4.1.4.4

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.

• If a tcpdump string exceeds 254 characters in length it will be truncated. (19693)

• An Access Manager can be deleted in connected state if Access Manager configuration is

edited. (19811)

• Logout button may not display using FreeBSD Netscape 7.0. (19654)

• An error message may not display when attempting to delete a Location or Time Window

that is in use in a connection profile. (19670)

• When creating a new RADIUS Authentication Service use the IP address of the RADIUS

Server for the Server field. Currently, the option to enter the Fully Qualified Domain Name

(FQDN) does not work with RADIUS Authentication Service. (19621)

• In extremely rare circumstances, Access Controllers may not complete an administrator

initiated reboot and remain in a continuous reboot state. If such a condition exists:

▫ First disconnect all the devices plugged into the downlink ports of the Access Controller

for a few minutes. When the reboot cycle completes, reconnect the devices to the

downlink ports.

▫ If the above procedure does not solve the issue, perform a factory reset of the Access

Controller by connecting to the Access Controller through the console port and

immediately typing “F” when the "To initiate a factory reset, press 'F' now..." prompt is

displayed. There is a three-second timer to respond to the prompt during the reboot

process. For more information, see the Command Line Interface chapter in the

Management and Configuration Guide.

As a factory reset clears any existing configuration information in the Access Controller, it is

advisable to write down any configuration information about the Access Controller prior to

performing an administrator initiated reboot operation. Please note that Access Controller

specific configuration information is limited only to DHCP, IP address, hostname, DNS, and

interface IP information. All rights information including identities, access policies, users,

connection profiles, and such are stored on the Access Control Server. (19586)

• Clients using LEAP authentication and identified with an Access Policy that requires DHCP

for IP address assignment may experience network connection problems even though they

have received a real DHCP IP address. The workaround is to specify the IP address of the

DHCP Server in the Access Controller Network Basic Setup tab. (19482)

• In an Integrated Access Manager, sometimes the connection time displayed for the internal

Access Controller is one minute greater than the Integrated Access Manager’s total uptime.

(19479)

• In the Access Policy Timeout tab, the Linger Timeout field accepts negative integers when it

should only accept positive integers. The Reauthenticate field allows entry of alphanumeric

characters but will not save them. The Reauthenticate field should only accept positive

integers. (19471)

• Clients using a real IP address with L2TP or PPTP authentication that are authenticated

through an Access Controller connected to a Cisco Catalyst 2950 have their IP address

associated with that Access Controller by the Catalyst 2950. If the clients log out and attempt