I have the following situation:
After connecting to my VPN GW with Windows 10 and Cisco AnyConnect 4.5 I see three reconnects. After them, the connection is up and without any problems. It just happens when the Hyper-V Adapter "vEthernet (Management)" is installed. It looks like when the Client connects to the VPN GW, the Hyper-V Adapter intervene in, no connection is possible and after three times the connection over wifi/wire is up, and everything is good. Is there any way that the VPN client dont's use the Hyper-V Adapter? Or do you know that problem at all?
There is article from a blogger who describes the problem a little bit better:
Solved! Go to Solution.
Looks like this is expected. There was a recent doc bug opened by Cisco to update their documentation:
It looks like the HyperV adapter might be coming up a few times after Anyconnect connects. Each time there is a network change, Anyconnect checks to see if it has to establish connection via that adapter. This may be why the reconnects are happening.
Thank you for that information. Is this going to be fixed or not? Or is there any solution for that behavior?
It does not look like there is going to be a fix for the behavior. A possible workaround would be a code change for Anyconnect not to consider the Hyper V adapter as a viable network adapter. I would open a TAC case, reference the bug and check if there is a fix or workaround for this.
This is not a solution!
Hyper-V is a supported feature in Windows 10. It is widely used along with supported security features like "Credential Guard, Device Guard" and "Windows Defender Application Guard".
All our computers use "Credential Guard". Either this gets fixed or we need to stop using Cisco Anyconnect.
Absolutely agree with you that Cisco should fix this problem. In this day and age, different software should learn to work with each other, especially when they are prominently used in common operating systems. From what it looks like from the bug, Cisco has resigned to the fact that this is expected behavior and that should not be the case. Opening a TAC case and asking for a fix is the next step here.
Just to let you know we've managed to get Cisco TAC to implement a fix for this either this month or in August.
It was supposed to have been fixed in 4.6.02074 but we're still seeing the issue so i've asked TAC to one again look into the issue.
"Fixed Hyper-V Behavior Showing Multiple Notifications. To accommodate a Hyper-V behavior change on Windows 10 (Redstone 3 or later), tunnel security reinforcement has been optimized while using tunnel-all or split-exclude configurations. When a new interface address is detected, Hyper-V is properly enforced without causing the appearance of multiple reconnects. (CSCvj71152)"