Avaya has released version 10.06.500 of their VPN client (formerly Contivity Extranet Client) that supports both 32-bit and 64-bit versions of Windows 8.

This single client supports the following operating systems (in both 32-bit and 64-bit versions);

Windows XP

Windows Vista

Windows 7

Windows 8

The following note is included at the top of the release notes;

When upgrading from Windows 7 GA to Windows 7 Service Pack 1 (SP1) users must remove the Avaya VPN Client prior to upgrading to SP1. Once the upgrade to SP1 is complete, reinstall the Avaya VPN Client.

Users who upgrade from a v10.05 or earlier release to v10.06 may receive the following error dialogue when attempting to establish an IPSec VPN tunnel – “Activation of VPN Adapter Fa iled”. This issue occurs when the AVC filter a dapter is not upgraded correctly during software installation.

wi01109393 10.06_500 – AVC Client does not work with SSL Protocols TLS1.1 and TLS 1.2.

wi01131474 10.06_500 – SSL tunnels may be disconnected due to multicast or host routing table entry changes which should have no impact on tunnel security. Changes to multicast and most host routes are now properly ignored.

wi01138381 10.06_500 – The SwapAdapters option added in 10.06.200 does not take into account the registry path for 64-bit systems.

You should refer to the release notes for all the details, including the interoperability issues.

Note: I’m hosting these files from my own servers so please don’t abuse my generosity by hot-linking to them from other sites or by downloading the files dozens of times needlessly.

I’m no longer personally using the Avaya VPN Client. These days I utilize the Juniper Network Connect (and Pulse) client when working remotely. So I’m not really in a position to help everyone with their installation problems. In the past I’ve found that the client will work fine on a fresh OS installation the majority of the time when it wouldn’t work on that same machine prior to the re-imaging.

I’m no longer personally using the Avaya VPN Client. These days I utilize the Juniper Network Connect (and Pulse) client when working remotely. So I’m not really in a position to help everyone with their installation problems. In the past I’ve found that the client will work fine on a fresh OS installation the majority of the time when it wouldn’t work on that same machine prior to the re-imaging.

wi01090553 VPN Client Route Monitoring for SSL Tunnel Mode is inconsistent or not working as expected.

wi01090556 The VPN Client disconnects a user due to detected route table changes (via route monitoring) if the client machine’s local area connections renew their DHCP lease while a tunnel is active – and the DHCP server returns a default gateway value (normal in most environments).

wi01105916 Changes introduced by wi01059319 in 10.06.200 may result in the client returning error “General System Problem.” This has been resolved.

wi01090812 AVC/SSL connection drops while roaming when original metric lower than VPN adapter.

You should refer to the release notes for all the details, including the interoperability issues.

Note: I’m hosting these files from my own servers so please don’t abuse my generosity by hot-linking to them from other sites or by downloading the files dozens of times needlessly. Since May 5, 2013 the Avaya VPN Client downloads have accounted for ~ 36.8 GB of traffic from this site.

I’m no longer personally using the Avaya VPN Client. These days I utilize the Juniper Network Connect (and Pulse) client when working remotely. So I’m not really in a position to help everyone with their installation problems. In the past I’ve found that the client will work fine on a fresh OS installation the majority of the time when it wouldn’t work on that same machine prior to the re-imaging.

wi01049421 – Unsigned EAC Miniport Driver Blocked by Windows XP OS. A new binder.exe utility has been included in the installation directory (default: %ProgramFiles%\Avaya\Avaya VPN Client) on Windows XP systems to assist with remediating this issue.

wi01056647 – AVC may crash when connecting through an unstable wireless access point

wi01059319 – Sometimes WINS Servers may not take effect in Windows XP

wi01068400 – Dial-up not working properly on 32 bit platforms

wi01028196 – AVC fails to properly identify Windows XP x64 operating system which may result in improper client operation

Activation of VPN Adapter Failed

wi00928966 – Users who upgrade from a v10.05 or earlier release to v10.06 on Windows XP may receive the following error dialogue when attempting to establish an IPSec VPN tunnel – “Activation of VPN Adapter Failed”. This issue occurs when the AVC filter driver is not upgraded correctly during software installation. As a precautionary measure, rebooting the machine before an upgrade installation is highly recommended. If the problem does occur, the workaround would be to uninstall and then reinstall the client. Please note, uninstall will remove all profiles and configurations. If users want to carry them over to the following reinstallation, they can use the Import/Export feature to export them before uninstall and import them back after reinstallation. For more details about the Import/Export feature please see Section 7 of this document.)

You should refer to the release notes for all the details, including the interoperability issues.

wi01011943 AVC “Display Warning” or “Disconnect” Limitation. Previously the VPN client would be abruptly terminated if a user attempted to shut down or restart the host machine. Now the tunnel is gracefully disconnected prior to shut down or restart.

wi01032791 Disconnect the VPN tunnel when AVC service is closed/stopped

Open Issues

wi01011920 AVC may Orphan NetBT NameList registry entries if ungracefully terminated. The workaround is to clear the NetBT NameList or gracefully terminate the VPN Client before rebooting or restarting the host PC.

wi01031645 AVC SwapAdapter feature does not reprioritize the VPN Adapter binding order for SSL tunnel types.

Interoperability

McAfee ViruScan v8.8

Microsoft Internet Explorer v8

Microsoft Windows 7 IPv6 6to5 Adapter Duplicates

Avaya NetDirect Client

DNS Binding Priority with Windows Operating Systems

You should refer to the release notes for all the details, including the interoperability issues.