VMware ESXi and vSphere Cluster Management

Add a Virtual Network Adapter in VMware Workstation Player

Learn how to add a second virtual network adapter in VMware Workstation Player, choose Bridged, NAT, or Host-only networking, and verify the guest connection.

A virtual network adapter is a virtual NIC that VMware presents to the guest operating system as a separate network interface. Adding another adapter lets one virtual machine use more than one network at the same time.

Common uses include separating LAN traffic from test traffic, connecting a VM to multiple virtual networks, and building gateway, firewall, routing, or isolated lab environments. VMware Workstation Player supports multiple adapters in one VM, up to a maximum of 10 virtual network adapters.

Before you begin

Identify the target VM in the VMware Workstation Player library.
Know which network the new adapter should use: Bridged, NAT, or Host-only.
Understand the guest operating system's basic network settings, including IP address, subnet, gateway, and DNS.
Plan for a possible loss of network access. Changing an adapter can interrupt remote administration or active connections.

Open the virtual machine hardware settings

Select the desired virtual machine in the Player library.
Open the VM management menu and choose the option for virtual machine settings. In many Player versions, this is available through Player > Manage > Virtual Machine Settings. Menu names can vary slightly by version.
Open the Hardware tab. This tab lists the virtual devices assigned to the VM.

Add a network adapter

In the Hardware tab, select Add.
Choose Network Adapter from the hardware-device list.
Choose the required network connection mode: Bridged, NAT, or Host-only.
Complete the wizard or dialog to create the device.
Confirm that the new network adapter appears in the VM hardware inventory.
Check that the adapter is marked as connected if the settings window provides a connected or connect-at-power-on option.
Save the settings and start the VM.

Choose a network connection mode

The connection mode determines which network the new virtual NIC joins and what other systems can reach it.

Mode	Network visibility	IP addressing behavior	Typical use case	Key limitation
Bridged	The VM joins the physical network through a host network interface.	The guest can usually receive an address from the physical LAN's DHCP service.	Making the VM visible to other devices on a home, office, or test LAN.	The physical network may restrict additional clients or MAC addresses, especially on some Wi-Fi or managed networks.
NAT	The VM uses a private VMware-managed network. External traffic is translated through the host's external network identity.	The VMware NAT network commonly provides DHCP, a private address, and a gateway.	Providing outbound access without giving the VM a separate identity on the physical LAN.	Devices on the physical LAN normally cannot initiate direct connections to the guest without additional forwarding or configuration.
Host-only	The VM joins an isolated virtual network shared by the host and participating VMs.	The VMware host-only network may provide DHCP, or the lab can use manually assigned addresses.	Building a private lab for host-to-VM and VM-to-VM communication.	The network is not directly exposed to the physical LAN or internet.

Quick selection guide

Choose Bridged when the guest must be directly reachable on the physical LAN.
Choose NAT when the guest mainly needs outbound access while remaining behind the host's network identity.
Choose Host-only when you need a host-contained, isolated lab network.

Configure the guest operating system

After the VM starts, the guest operating system should detect the added virtual NIC as a new network interface. Each virtual adapter is shown separately in the guest's network settings, so the interface names or numbers may change when another adapter is added.

Open the guest's network settings or interface list.
Confirm that the new interface is present and enabled.
Give the interface a clear name, such as LAN, Lab, or Management, if the guest OS supports renaming interfaces.
Use DHCP when the selected VMware network provides automatic addressing.
For a static configuration, enter an address, subnet mask or prefix, gateway, and DNS values appropriate to the selected network and lab design.
Do not assign the same static IP address to multiple systems.

When a VM has multiple adapters, configure the correct interface. An address on the NAT adapter, for example, does not prove that the Host-only adapter is configured correctly.

Example: dual-homed lab VM

Add a second adapter to a Windows VM. Keep the first adapter on NAT for outbound updates, and connect the second adapter to Host-only for communication with the host and isolated lab VMs. The VM can then use separate interfaces for internet-capable traffic and private lab traffic.

Example: VM visible on a physical LAN

Add an adapter configured for Bridged networking and allow the guest to obtain an address from the physical network's DHCP service. Other devices on that LAN can then communicate with the VM, subject to firewall and network-policy rules.

Example: private testing network

Attach several test VMs to the same Host-only network. They can communicate with one another and with the host without placing the test systems directly on the physical LAN.

Verify the added adapter

Check	Where to verify	Expected result
Adapter appears in VMware hardware settings	VM settings, Hardware tab	The new Network Adapter is listed and has the intended connection mode.
Guest detects the interface	Guest network settings or interface list	A second, enabled network interface is visible.
Interface has expected IP configuration	Guest network details	The address, subnet, gateway, and DNS settings match the selected network design.
Connectivity test succeeds	Guest tools and reachable systems	The guest reaches the host on Host-only, its gateway or internet through NAT, or the physical LAN through Bridged mode.

On a Windows guest, ipconfig /all displays adapters and their addresses. On many Linux guests, ip addr displays interfaces and addresses. Use the guest's native network tools if these commands are unavailable.

Also test the original interface. Confirm that existing connectivity has not been unintentionally changed, especially routing and the default gateway. Multiple adapters can create competing routes if the guest assigns gateways automatically to more than one interface.

Troubleshooting

The new adapter is absent in the guest OS

Confirm that the hardware-addition process was completed and that the adapter is listed in VMware's Hardware settings.
Verify that the virtual device is connected and configured to connect at power-on when that option is available.
Restart the VM and inspect the guest's network-interface list again.
Check whether the guest OS requires a hardware rescan or an additional virtual-device driver.

The adapter has no IP address

Check whether the selected network is expected to provide DHCP.
Enable the interface in the guest OS.
Renew the DHCP lease, or enter a complete static configuration with a valid address, subnet, gateway, and DNS values.
Confirm that the address belongs to the selected virtual or physical network.

A Bridged VM cannot reach the physical network

Confirm that the guest address is in the same network range as the physical LAN.
Check host connectivity and the physical adapter selected for bridging.
Verify that the LAN's DHCP service assigned an address.
Some Wi-Fi networks and managed networks restrict bridged clients or additional MAC addresses. Test on an allowed network or consult the network administrator.

A NAT VM cannot access the internet

Verify that the host system itself can access the intended network.
Inspect the guest's IP address, default gateway, and DNS settings.
Reconnect the virtual adapter or restart the VM.
If the problem continues, investigate whether VMware NAT network services are available on the host.

Host-only machines cannot communicate

Confirm that all participating VMs use the same Host-only network rather than different isolated networks.
Compare their IP addresses and subnet settings.
Check guest firewalls and permit the protocol required by the test.

Key points

A virtual network adapter is a separate virtual NIC presented to the guest OS.
One VMware Workstation Player VM can have up to 10 virtual network adapters.
Power off the VM before changing hardware whenever possible.
Use Bridged for physical-LAN visibility, NAT for private outbound access through the host, and Host-only for an isolated host-and-VM lab.
After adding the adapter, verify VMware settings, guest detection, IP addressing, selected-interface configuration, and connectivity.