AnyConnect cannot connect when installed after McAfee Internet Security
If installed after 3rd party personal firewall/AV product, AnyConnect will fail to connect. EventViewer will report inability to change the interface name for virtual adapter.
If installed after 3rd party personal firewall/AV product, AnyConnect will fail to connect
Disable all the features of personal firewall/AV, make a small change on AnyConnect virtual adapter and connect.
Further problem description
The AnyConnect virtual adapter (VA) driver is not properly installed due to the McAfee Internet Security self-protection mechanism denying certain registry operations. The McAfee log file McSvHost000.log includes multiple entries resembling the following:
(Note that the UpdateDriverForPlugAndPlayDevices Windows API, used to install the driver does not return an error, therefore AnyConnect assumes successful installation.)
As a result, even after enabling the VA via the Device Manager Management Console (devmgmt.msc), the virtual adapter is not listed by the Windows ipconfig command. Similarly, vpnagent fails to identify the VA connection name (due to the GetAdaptersAddresses native API not returning the AnyConnect virtual adapter) leading to the VPN connection failure.
Note that the VA installation works fine with McAfee VirusScan Enterprise installed. The problem only happens if the AnyConnect installation is performed with McAfee Internet Security installed.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.