Release Notes 4.1.4.6

Release Notes, Version 4.1.4.6
8
•
If you change the uplink port, you must reboot the device before you can access the device's
web interface again.
• If an administrator's or client's browser fails to successfully negotiate an SSL connection with
the 700wl Series system's web server, the OpenSSL subsystem will place some fairly obscure
messages in the logs. You can identify these errors by their references to OpenSSL or to RSA
key errors. These errors are harmless as the browser and server generally do eventually
succeed in establishing an SSL connection.
• The SafeNet 7.0.x client in combination with Windows XP does not allow roaming. A roam
away from the initial Access Point causes the interface to go down, and the SafeNet 7.0.x
client cannot recover. A client reboot is required before you can connect again. Roaming
works correctly with the SafeNet 9.0.x client. Roaming also works with the 7.0.x client and
other Windows OS versions.
• Orinoco WaveLAN cards used with Windows XP do not allow successful roaming. This is
because when an Orinoco-enabled Windows XP system associates with a new Access Point,
the associated driver forces the interface to go down, destroying all open sessions. The client
should still get the same IP address, but all sessions will be gone. (17040)
• If you need to modify the 700wl Series system bridging options through the Advanced
Network Configuration page under the Network Setup tab, you should do so when the system
is idle. When you change bridging options, any clients logged on to the system are logged off.
However, they are not completely logged off – client connections are dropped, but the clients
are not removed from the Client Status list on the Access Controller. For each client
connected when the bridging option was changed, there will be error entries in the log file
similar to the following:
Error 00:20:e0:8d:d8:91: write: Socket is not connected Error
ambit_ngcfg_disconnect_hook: can't disconnect ip hook: Bad filedescriptor
These clients will not be able to log on again, because the system thinks they are still logged
on. The workaround has two parts:
▫ From the Client Status display, log out the client.
▫ The client must release and renew their IP configuration. They will then be able to log in.
• The 700wl Series system supports SecureCRT 4.05 with the Auto Detect or Standard SSH
server options. It does not support SSH Communications 2.1.0 or 2.3.0, or DataFellows
• 2.0.12 or 2.0.13. (17109)
• The 700wl Series system does not support the Phase 2 Compression (Deflate) option with the
SafeNet SoftRemoteLT client. You must disable this feature in order to establish a
connection.
Software Fixes
The following problems that were identified in previous releases of the ProCurve Secure Access
700wl Series system have been fixed in software release 4.1.4.6:
• Cannot downgrade flash based 720wl from 4.4 to 4.1 release (22288)