Release Notes 4.4.0.50

Known Issues And Behaviors
9
•
In a redundant Access Control Server configuration an Access Controller may not show a
connection to an Access Control Server if the secondary Access Control Server is not
reachable. (20578)
• Under certain circumstances the uptime may displayed incorrectly which can be corrected by
manually setting the time and a system reboot. (20825)
• If many Kerberos clients continually log in or out through L2TP every 10-15 seconds
(approx. 120 authentications per 60 seconds totally), some authentications may fail. The
Windows XP clients which fail to authenticate due to system error #691 (i.e. user
name/password invalid in domain) will succeed in the subsequent attempts and ping real-IP
peer client. (21054)
• If an Access Controller is downgraded from version 4.4 to 4.1, several disklabel warning
messages are issued. These errors are harmless and only appear when version 4.1 is started.
(20823)
• Exporting the Rights configuration does not export the list of files used in Logon
Customizations. (19914)
• If bandwidth limits are modified in an Access Policy used by an encrypted client, and if the
encrypted client has completed a roam before the bandwidth limits were changed, the new
bandwidth limits will be displayed correctly in the Client Details page when the “Refresh
User Rights Now” is selected. However, the bandwidth limit changes will not take affect until
the encrypted client logs off and logs on again. If the encrypted client does not roam during
the bandwidth limit changes, the changes take affect immediately after the “Refresh User
Rights Now” is selected. (19910)
• In the 802.1X/WPA authentication service with the built-in RADIUS server configured as a
proxy, if a client keeps getting authentication failures, verify the following:
 All components of the authentication service (access points, remote RADIUS servers,
clients) are EAP-compatible.
 802.1X/WPA authentication service is configured correctly within the 700wl Series
system and for each component (access point, remote RADIUS server, and client). For
instance:
- Shared secret and IP address of the remote RADIUS server is correct
- Access Control Server is a client on the remote RADIUS server configuration
If all of the above is correct and the client still cannot authenticate, restart the built-in
RADIUS server by rebooting the Access Control Server, or contact ProCurve Technical
Support for assistance. (19884)
• QoS classification cannot be performed on encrypted (L2TP, PPTP, IPSec) client data.
Encrypted data paths consist of inner and outer tunnels, where the outer tunnel is the
encryption tunnel and the inner tunnel contains the data packets. QoS classification is
currently performed on the outer tunnel. (19871)
• In a redundant system, if there is loss of connectivity between the preferred primary Access
Control Server and the secondary Access Control Server, the secondary will promote itself to
acting primary. If clients log on to an Access Controller connected to the new acting primary
Access Control Server and then connectivity is restored between the preferred primary and
secondary Access Control Servers, the restored preferred primary Access Control Server may
have a different view of the network than actually exists. This could result in inaccurate
information being displayed in the Client Status page. Note that clients do not experience a