Release Notes 4.4.0.50

Release Notes, Version 4.4.0.50

disruption of service and clients will reappear in the Client Status page once their rights

expire or when they logout and log back in. (19808, 19677)

• In a redundant system, 802.1X/WPA Authentication Service configuration is sometimes not

replicated on the secondary Access Control Server when redundancy is enabled after the

802.1X/WPA Authentication Service is configured. The workaround is to enable redundancy

and let the Access Control Servers peer up before configuring the 802.1X/WPA

Authentication Service. (19793)

• In a redundant system, if the secondary Access Control Server is disconnected from the

network, an Access Controller will maintain connectivity to the preferred primary Access

Control Server and will remove the secondary Access Control Server’s IP address from its

configuration under the assumption that redundancy has been disabled. The Access

Controller will not know about the secondary Access Control Server unless the preferred

primary Access Control Server is shutdown, at which point the preferred primary Access

Control Server will send a message telling the Access Controller to try to connect to the

secondary Access Control Server and will include the IP address of the secondary Access

Control Server.

• If the preferred primary Access Control Server is disconnected from the network, the Access

Controller connects to the secondary Access Control Server and keeps trying to connect to

the preferred primary until eventually after several unsuccessful attempts to connect, the

Access Controller removes the preferred primary IP address from its configuration under the

assumption that redundancy has been disabled. (19758)

• When the Access Control Server is configured to use the internal Access Controller’s HTTP

proxy server, clients will not be able to access web sites that use HTTPS. (19749)

• Clients using a Real IP 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)

• 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)