Release Notes 4.1.4.8

Known Issues And Behaviors

•

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

to log in again to another Access Controller connected to the same Cisco Catalyst 2950, or

roam to another Access Controller connected to the same Cisco Catalyst 2950, they will not

be able to gain network access because the Cisco Catalyst 2950 associates the client’s IP

address with the first Access Controller. Clearing the ARP cache on the Cisco Catalyst 2950

removes the previous association of the client's IP address with the first Access Controller

and allows the client to connect through the other Access Controller that is connected to the

same switch. (19427)

• When redundancy is disabled in a redundant 700wl Series system, the secondary Access

Control Server reboots but sometimes does not complete a factory reset. When the former

secondary Access Control Server reconnects after rebooting and not completing a factory

reset it sends a message to all Access Controllers in the system identifying itself as the

secondary Access Control Server. If the former primary Access Control Server is rebooted,

the Access Controllers will attempt to connect to the former secondary Access Control

Server. (19354)

• Several minor error messages or minor information messages are added to the log when a

client attempts to access a restricted page. (19394)

• Downgrading to a prior release may cause known issues of the earlier version to re-emerge. If

downgrading to a prior release in a redundant system, disable redundancy before performing

the downgrade. (19330)

• The LCD display on the Access Controller may blank out when throughput is high. (19306)

• The “Maximum Concurrent Logons per User” setting in an Access Policy does not apply to

sessions using SSH port forwarding. (16236)

• From the CLI, doing a traceroute command on an invalid IP address gives only a partial result

and does not appear to complete. The workaround is to press Return after waiting at least 30

seconds (the traceroute timeout interval). (17472)

• The HTTP Proxy feature was implemented using HTTP 1.0. Sites that make use of HTTP

1.1-specific features may not work reliably. In particular, clicking on a link may result in the

browser being redirected to various erroneous alternate links. (17813)

• When viewing Client Status from the Access Control Server for all Access Controllers, some

clients may be displayed with blanks as the IP address. This may happen through both the

Administrative Console or through the CLI. To see the actual IP address assigned to the

client, you can take one of two actions:

▫ Display the detailed view for the client

▫ Select the Access Controller through which the client is connected, and display client

status just for that Access Controller.