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.
- wi00889600 10.06_500 – AVC 10.04.109 Client in SSL Mode Doesn’t Accept Untrusted Self-Signed Cert.
- wi00982245 10.06_500 – AVG IPsec mobility performance is very low.
- wi01069664 10.06_500 – AVC Mobility feature fails when moving from a wireless to a wired connection.
- wi01069666 10.06_500 – Repeated failover between wired and wireless connections may cause mobility failure.
- wi01100993 10.06_500 – VPN Client – PLAP is unreliable on Windows 8.
- wi01100994 10.06_500 – VPN Client – OSK (On-Screen Keyboard) does not launch with client.
- 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.
AVC32-10.06.500.exe (32-bit – Windows XP, Windows Vista, Windows 7, Windows 8)
AVC64-10.06.500.exe (64-bit – Windows XP, Windows Vista, Windows 7, Windows 8)
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.
Do you have the custom kit versions of this release?
VPN User says
Thank you for posting the Avaya VPN Client binaries.
I just discovered that you can’t download them directly unless you have the right kind of Avaya account. Free, “non customer”, accounts on support.avaya.com don’t have permission. You don’t even have permission to view the MD5 checksum or Avaya signature files to verify binaries found elsewhere…
But you can see the various VPN client versions here, and see the files available for each:
Michael McNamara says
Michael Hartrick says
This posted saved my ass once a long time ago, but I was silly and only downloaded the 64bit client. I figured I would never need the 32bit file.
The links are now broken, do you still have the AVC32-10.06.500.exe file? if so, could you email it to me? I have a contivity VPN and I really want to be able to connect with my netbook, which I run 32bit windows 10 on.
Thanks in advance
Michael McNamara says
I’ll look Michael… not sure I still have that software laying around.
Ok, I see the problem… when I migrated to Nginx and starting using cdn.michaelfmcnamara.com as an alias and poor mans CDN.