The Release notes for the AWS Client VPN for Windows version 3.10.0 mention:
• Fixed a connectivity issue when Hyper-V network adapters are installed on the client machine.
Our VPN Client software is working fine for other users who are do not have Hyper-V network adapter installed.
But for users who are using Hyper-V network adapter, it appears that the VPN client is ignoring the Hyper-V adapters (Skipping Hyper-V Adapter) and it settles on the Loopback 127.0.0.1 connection to the user's computer. When trying to connect, the user gets a pop-up window with error state: Local area network IP address configuration was not found. Please check with your administrator.
This is what we see in the aws_vpn_client.log:
2023-09-20 12:06:06.888 -04:00 [DBG] Metrics data request created
2023-09-20 12:06:06.942 -04:00 [DBG] Network interface name: Ethernet 4, type: Ethernet, status: Down, description: AWS VPN Client TAP-Windows Adapter V9
2023-09-20 12:06:06.942 -04:00 [DBG] Network interface name: vEthernet (Default Switch), type: Ethernet, status: Up, description: Hyper-V Virtual Ethernet Adapter
2023-09-20 12:06:06.943 -04:00 [DBG] Skipping Hyper-V Adapter
2023-09-20 12:06:06.943 -04:00 [DBG] Network interface name: vEthernet (Cato Networks VPN Adapter Virtual Switch), type: Ethernet, status: Down, description: Hyper-V Virtual Ethernet Adapter #3
2023-09-20 12:06:06.943 -04:00 [DBG] Network interface name: vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch), type: Ethernet, status: Up, description: Hyper-V Virtual Ethernet Adapter #6
2023-09-20 12:06:06.943 -04:00 [DBG] Skipping Hyper-V Adapter
2023-09-20 12:06:06.943 -04:00 [DBG] Network interface name: vEthernet (Intel(R) Ethernet Connection (7) I219-LM Virtual Switch), type: Ethernet, status: Up, description: Hyper-V Virtual Ethernet Adapter #2
2023-09-20 12:06:06.943 -04:00 [DBG] Skipping Hyper-V Adapter
2023-09-20 12:06:06.943 -04:00 [DBG] Network interface name: Local Area Connection, type: 53, status: Down, description: TeamViewer VPN Adapter
2023-09-20 12:06:06.943 -04:00 [DBG] Network interface name: vEthernet (SonicWALL Virtual NIC Virtual Switch), type: Ethernet, status: Down, description: Hyper-V Virtual Ethernet Adapter #4
2023-09-20 12:06:06.943 -04:00 [DBG] Network interface name: Loopback Pseudo-Interface 1, type: Loopback, status: Up, description: Software Loopback Interface 1
2023-09-20 12:06:06.943 -04:00 [DBG] Initial localNetworkCidrsStringForCurrentConnection before connection
2023-09-20 12:06:06.944 -04:00 [INF] Starting OpenVpn process
Maybe there is something else that needs to be configured on the AWS side to allow these hyper-v adapters to be used?
Thanks!
AWS OFFICIALUpdated 9 months ago