Summary

This article will explain how to overcome the issue where the vendor daemon is unable to start after connecting to Cisco AnyConnect Secure Mobility Client VPN.

Symptoms

When starting the license server after connecting through a VPN using Cisco AnyConnect Secure Mobility Client the following error is displayed:

Cause

The problem appears to be that the Automatic Metric setting for the Cisco VPN connection (IPV4/IPV6) is set to a manual Interface Metric value of 1 instead of the Automatic metric checkbox enabled default. Since getaddrinfo on Windows prioritises interfaces with the smallest metric, this means FNP hostname resolution attempt will fail.

Resolution

Set the Automatic Metric setting for IPV4 and IPV6 Cisco VPN back to the Automatic metric checkbox enabled default, this should resolves the issue.

To do this go to Control Panel\Network and Internet\Network Connections\Cisco AnyConnect Secure Mobility Client Connection

1. Right click and select properties.
2. Select IPv4 and properties.
3. Select Advanced.. button.
4. Check the Automatic Metric checkbox.
5. Repeat the steps for IPv6 as well.