Release Notes 4.4.0.50

Software Fixes
7
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. The
client must use the “Reauthenticate” option to reconnect in this case. (19782)
• 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 Local Networks 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 software have been fixed in software release 4.4.0.50:
• Access Controller intermittent disconnects from Access Control Server. (20529, 20945)
• Access Controllers sometimes cannot display any clients after upgrade. As a workaround,
modifying a configuration item will usually fix this. (20669)
• Users authenticating with 802.1X Logons and associated with a Connection Profile that
specifies a VLAN ID will not get the correct rights row in the Rights Assignment table.
(19849)
• A client with a static IP and valid address on the uplink does not always get redirected.
(20832)