Bridged networking does not work when loopback adapter is installed on host

Products

• VMware Desktop Hypervisor

Issue/Introduction

Symptoms:

• Automatic bridged networking is enabled
• Microsoft Loopback software network adapter is installed and enabled on the host
• OpenAFS may be installed on the host
• Any virtual machines using the bridged virtual network adapter do not have network access

Environment

VMware Workstation Player 12.x (Windows)
VMware Workstation Player 15.x (Windows)
VMware Workstation 10.x (Windows)
VMware Player 5.x (Windows)
VMware Workstation 11.x (for Windows)
VMware Workstation Player 15.x (Linux)
VMware Workstation Pro 15.x (Windows)
VMware Player 7.x (Windows)
VMware Workstation 8.x (Windows)
VMware Workstation Player 14.x (Windows)
VMware Workstation Pro 15.x (Linux)
VMware Player Pro 7.x (Windows)
VMware Player 2.x (Windows)
VMware Workstation 9.x (Windows)
VMware Workstation 6.x (Windows)
VMware Player 4.x (Windows)
VMware Player 3.x (Windows )
VMware Player 6.x (Windows)
VMware Workstation 7.x (Windows)

Resolution

This issue occurs when the Microsoft Loopback network adapter is installed on the host. Automatic bridging may incorrectly attempt to send network traffic over this adapter which does not have network connectivity.

To ensure that bridged networking functions as expected in Workstation 7.x and later:

1. Click Edit > Virtual Network Editor.
2. Select a network adapter that has the Type set to Bridged.
3. In the Bridged to drop down box select a usable network adapter.
4. Repeat steps 1 to 3 for all available physical network adapters that are displayed in the Bridged to drop-down.

To ensure that bridged networking functions as expected in Workstation 6 and VMware Server:

1. Click Edit > View Network Settings.
2. Click Host Virtual Network Mapping.
3. Edit the virtual network VMnet0 and assign it to a usable network adapter that is not the automatically chosen adapter option.