The ProCurve Secure Access 700wl Series Version 4.4.0.50 Release Notes Contents New Features in this Release ..........................................................................................................2 System Requirements......................................................................................................................3 Upgrade Notes................................................................................................................................
Release Notes, Version 4.4.0.50 Please go to the support web site located at http://www.procurve.com for the latest information on the ProCurve Secure Access 700wl Series products. The current release notes, manuals, FAQs, and problem reports are always available at this site. Important information required for updating system software is available on a secure page at the ProCurve Networking web site: http://www.procurve.com. Click on Software updates (in the sidebar).
System Requirements server, the built-in RADIUS server can manage multiple realms, each with multiple remote RADIUS servers working in a failover capacity within each realm. • SSL v.3 Protocol. The 700wl Series system now supports SSL v.3 protocol for the 700wl Series system login, logout, and stop pages. SSL v.3 is enabled by default. To revert to SSL v.2, select “Disable SSL V3 on Login/Logout/Stop page“ in the Local Networks page on the SSL tab. (2479) • MAC Location.
Release Notes, Version 4.4.0.50 Other browsers, such as earlier versions of Internet Explorer, earlier version of Netscape, or Safari (Macintosh) may not display all pages or data correctly. UPGRADE NOTES Important: Please read the ProCurve Secure Access 700wl Series Software Version 4.4.0.50 Update Guide for instructions on updating your systems that currently run software version 4.1.3.93. The update process is a two-step process, requiring an intermediate update to software version 4.1.4.
Clarifications and Usage Notes When the first remote RADIUS server is found to be down, an Access-Reject is sent to the client and the proxy server marks the remote server as dead. If the client retries during the dead time (by default—two minutes), the request is sent to the alternate remote server. The end user experience is that the first authentication fails if the primary remote server is dead and the second attempt, if made within the two minute timeframe, will succeed.
Release Notes, Version 4.4.0.50 Any Identity Profile and presumably gets rights based on the “Unauthenticated” Access Policy. On the other hand, a Registered Guest is an authenticated user, because its name and password are in the user database, although it is assigned to the Guest Identity Profile.
Software Fixes works correctly with the SafeNet 9.0.x client. Roaming also works with the 7.0.x client and other Windows OS versions. • Using 802.1X and an Odyssey is a wireless LAN client or Windows XP wireless client, when a user that has been successfully logged on disconnects and is logged off, and then tries to reconnect immediately by checking the “Connect” option, the second logon is not successful, because the client assumes it is reconnecting to an already authenticated connection.
Release Notes, Version 4.4.0.50 • An Access Controller IP address is not correctly displayed with CLI “show clients” command. (20753) • Access Controllers are not displayed in user interface when using Internet Explorer on Windows 2003 Server. (20771) • Retrieving client or session status may cause an Access Controller to reboot. (20730) • The first time the 802.1X/WPA page is viewed, an error message is displayed stating that WPA is not configured.
Known Issues And Behaviors • 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.
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.
How To Get Help • 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.
