VMware ESXi and vSphere Cluster Management

Add a Virtual Network Adapter in VMware Player

Learn how to add a second virtual network adapter in VMware Player and choose Bridged, NAT, or Host-only networking for your virtual machine.

A virtual network adapter is virtual hardware that gives a virtual machine (VM) a network interface. The guest operating system uses this interface to communicate with the host, other virtual machines, or external network devices.

A VM can use more than one adapter when it must connect to separate networks. For example, one adapter can provide private host-to-VM communication while another provides access to a LAN. VMware Player supports up to 10 virtual network adapters for one virtual machine.

Before you begin

  • Open VMware Player and locate the target VM in the Player library.
  • Know whether the new adapter needs direct physical-network access, outbound access through the host, or a private host-to-VM connection.
  • Remember that the guest operating system must detect and configure its own network interface after the adapter is added.

Adapter-addition workflow

Step — VMware Player action — Result

Select virtual machine — Select the target VM in the VMware Player library — The correct VM is ready to configure.

Open Virtual Machine Settings — Use Player > Manage > Virtual Machine Settings — The VM configuration window opens.

Open the Hardware tab — Select Hardware — The virtual hardware list is displayed.

Add hardware — Select Add — The Add Hardware workflow starts.

Select Network Adapter — Choose Network Adapter as the hardware type — VMware Player prepares a new virtual network interface.

Choose networking mode — Select Bridged, NAT, or Host-only — The adapter receives the required connection behavior.

Set Connect at power on if needed — Enable Connect at power on when the adapter must attach automatically — The adapter connects whenever the VM starts.

Finish and validate — Complete the wizard, confirm the adapter appears in the Hardware list, and start or resume the VM — The guest can detect and use the new interface.

How to add the virtual network adapter

1. Select the target VM and open its settings

Select the virtual machine from the VMware Player library. Open Player > Manage > Virtual Machine Settings. In the settings window, select the Hardware tab. This tab lists the VM's virtual processors, storage, network interfaces, and other virtual hardware.

2. Start the Add Hardware workflow

On the Hardware tab, select Add. When VMware Player asks which hardware type to add, choose Network Adapter, then continue through the wizard.

3. Choose the adapter's connection mode

Select the mode that matches the network design. The three relevant choices are Bridged, NAT, and Host-only.

Mode — Connection scope — External network visibility — IP addressing behavior — Typical use case

Bridged — The VM connects through a physical host network adapter — The VM appears as a separate device on the physical network — It obtains or uses an address on that physical network — Normal access to the same LAN as the host.

NAT — The VM uses a private virtual network behind the host — External systems see outbound traffic as coming from the host's external network identity — A virtual DHCP server assigns the VM a private address — Internet or network access without making the VM independently addressed on the external network.

Host-only — The VM connects to a network contained within the host computer — It is not directly connected to the external network — The VM and host communicate through a host-visible virtual network adapter — Private host-to-VM labs and isolated testing.

4. Configure startup connection

Enable Connect at power on if the new adapter should be attached automatically whenever the VM starts. Leave this option disabled only when the adapter should be connected manually or kept disconnected during startup.

5. Finish and verify

Finish the hardware-addition wizard. Confirm that the new Network Adapter appears in the VM's Hardware list. Start or resume the VM as needed.

Inside the guest operating system, check its network-interface list and confirm that the new interface is detected and enabled. Then test connectivity appropriate to the selected mode: reach a LAN resource with Bridged, test outbound access with NAT, or test host-to-VM communication with Host-only.

Understanding the connection modes

Bridged networking

Bridged networking connects the VM to the physical network through one of the host system's physical network adapters. The VM participates on that external network as a separate network device, with its own network identity and address on the LAN.

Use Bridged mode when the VM needs normal access to the same physical network as the host or when other LAN devices must communicate with the VM as a separate machine. A development VM that needs access to an office or home LAN is a common example.

NAT networking

NAT means Network Address Translation. In NAT mode, the VM is placed on a private virtual network and receives a private address through a virtual DHCP server. VMware Player translates the VM's outbound traffic so that external systems see it as coming from the host system's external network identity.

Use NAT when the VM needs to reach external network resources but does not need to appear as a separately addressed device on the physical network. This is often suitable for browsing, software updates, and development work that requires outbound connectivity.

Host-only networking

Host-only networking creates a private network contained within the host computer. The host and the VM can communicate through a host-visible virtual network adapter, but the VM does not receive direct access to an external physical network through this connection.

Use Host-only mode for isolated labs, testing, and services that should communicate privately with the host or other virtual machines on the same host-only network.

Using two network adapters

Adding a second adapter lets one VM maintain distinct network paths. For example, configure one adapter as Host-only for private host-to-VM administration and configure another as NAT for outbound network access. Alternatively, use Bridged for LAN participation and a second adapter for a separate private network.

Each adapter has its own connection mode and may appear as a separate interface inside the guest operating system. The guest's routing configuration determines which interface it uses for particular destinations, so avoid creating overlapping or unintended routes when configuring multiple adapters.

Practical configuration examples

  • Development VM on the office or home LAN: Add an adapter, select Bridged networking, and enable Connect at power on. The VM should participate on the same LAN as other devices.
  • Outbound access without separate LAN visibility: Add an adapter, select NAT, and enable Connect at power on. The VM should receive a private virtual-network address and use the host's external identity for outbound traffic.
  • Private host-to-VM lab: Add an adapter, select Host-only networking, and enable it when required. The host and VM should communicate over the isolated virtual network.
  • Two separate network paths: Add a second adapter and assign it a different mode from the first. For example, combine Host-only with NAT or Bridged.

Troubleshooting

The new adapter is not active after startup

Review the adapter settings and confirm that Connect at power on is enabled. Then check the guest operating system's network-interface list to determine whether it detected and enabled the new interface.

The VM cannot access the external network

Host-only mode is intended for private connectivity and does not provide direct external-network access. Use Bridged when the VM must participate directly on the physical network, or NAT when it should reach external resources through the host.

Other LAN devices cannot reach the VM separately

The adapter may be using NAT. NAT shares the host's external network identity for outbound traffic. Select Bridged networking when the VM must be directly present on the physical LAN as a separate device.

The host and VM cannot communicate privately

Confirm that the adapter is set to Host-only networking and is connected. Also check that the guest operating system detected and enabled the interface.

No new adapter appears in the Hardware list

The Add Hardware wizard may not have been completed. Return to the Hardware tab and verify that the Network Adapter is listed. Also count the existing virtual network adapters and remain within VMware Player's maximum of 10 adapters per VM.

Exam-relevant notes

  • Bridged: the VM is a separate device on the physical network through the host's network adapter.
  • NAT: the VM uses a private virtual network, receives a private address through virtual DHCP, and shares the host's external network identity.
  • Host-only: communication is restricted to a private network within the host environment.
  • Connect at power on: automatically attaches the adapter when the VM starts.
  • Adapter capacity: VMware Player supports up to 10 virtual network adapters per VM.

For a related procedure, see Add a Virtual Network Adapter.