Release Notes 4.1.4.6

Release Notes, Version 4.1.4.6
6
•
If the Access Control Server has previously recognized an Access Controller, any changes
made to the Access Controller while it is disconnected from the network will be overwritten
with the saved configuration file stored on the Access Control Server once the Access
Controller is reconnected to the network. If this is not the intention, then delete the Access
Controller using the Access Control Server’s Administrative Console before reconnecting it
to the network. However, it is recommended that the Access Control Server handle all Access
Controller configurations.
• Clients running Windows XP and using L2TP/IPSec or IPSec VPN to authenticate need to
disable the Internet Connection Firewall (ICF) service. If ICF is enabled, the client’s
connection will be dropped when the IPSec security association has expired. (19360)
• Clients running Windows 98 that have logged off, or have been logged off automatically,
need to wait 20 seconds before logging on again. This is a Windows 98 constraint. (18987)
• Displaying the status of the primary or secondary Access Control Server while they are
synchronizing may result in either an error message stating “DB Error: connect failed” or
“Page data is invalid.” This only occurs in redundant systems with unusually high
configuration activity. If this error message does occur, click the Back button on the browser
to clear it. (19336)
• After changing the time zone on a 700wl Series component, it takes approximately seven
seconds for the new time to take effect. (19355)
• Before merging two 700wl Series system networks together to create a redundant system,
where both Access Control Servers are active, first deactivate the Access Control Server that
is designated to be the secondary Access Control Server in the redundant system. (19359)
• With version 4.1.1.37, the management of all 700wl Series components, including
configuration and management of all Access Controllers associated with the Access Control
Server, is done centrally from the Administrative Console on the Access Control Server.
Because of this, the ability to configure an Access Controller directly has been curtailed:
▫ The Administrative Console on an Access Controller is no longer accessible by pointing
a browser to the IP address of the Access Controller, or to the 42.0.0.1 address. In either
of these cases, you are presented with the Administrator Logon window, but when you
complete the logon you are presented with a page that provides a redirect to the Access
Control Server (or allows a logout).
▫ The Command Line Interface on an Access Controller provides a limited number of
commands, allowing configuration of only the basic parameters necessary to enable the
Access Controller to communicate with its Access Control Server (IP address and shared
secret). It does provide commands to enable viewing of the status of the unit, as well as
certain other functions such as the ability to upgrade, backup, shutdown and restart the
unit.
• There are a number of functions that will result in termination of an active SSH session.
These include any CLI commands (or the equivalent function done through the
Administrative Console) that cause a global restart, such as changing the NAT DHCP
settings, enabling or disabling remote access, enabling or disabling SSH under Wireless Data
Privacy Setup, or changing the Access Control Server IP address. Any of these actions cause
the system to restart internally which shuts down any open SSH sessions.
• A user that logs on as “Guest” matches the Guest Identity Profile, but is not considered to be
an authenticated user. If the Guest Identity Profile is associated with a Connection Profile that
includes a time window, and the time window expires, the Guest user will then default to the