Release Notes 4.5.0.37

Known Issues And Behaviors

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)

• 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 Interface 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.

In either case, the IP address will then be displayed correctly. (18819)

• Access Control Server may display Access Controller logs with an incorrect timestamp after

a reboot of the Access Controller. (20824)

• “Reset to Defaults” button in the Administrator SSL page may not be working. (20657)

• RealIP IPsec client traffic is redirected to the default router even if staying on the local

network. (20760)

• Some PPP clients may be denied login (with error message) under heavy PPP system load.

(20749)