Add a Virtual Network Adapter in VMware Player

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

Why add a virtual network adapter?

A virtual network adapter is a virtual network interface card attached to a virtual machine (VM). The guest operating system sees it as a network device, much like a physical computer sees an Ethernet or wireless adapter.

Adding another adapter allows one VM to connect to more than one network. Common reasons include:

Connecting a lab server to an isolated network while retaining internet access for updates.
Separating management traffic from application or test traffic.
Connecting a VM to the physical LAN so other devices can reach it.
Creating a private connection between the host system and the guest operating system.
Testing routing, firewalls, gateways, or services across multiple network segments.

For example, a test server can use one NAT adapter for outbound updates and a second Host-only adapter for communication with the host and other lab VMs.

VMware virtual machines generally support up to 10 virtual network adapters, although the exact limit can depend on the virtual hardware version, VMware Player release, and guest operating system. The guest OS may also impose its own limits.

Plan the network before changing the VM

The host system is the physical computer running VMware Player. The guest operating system is the operating system installed inside the VM. Before adding hardware, decide which networks the guest must reach and which interface should provide its default route.

Do not select a connection mode merely because it is available. Decide whether the VM should be visible on the physical LAN, receive outbound access through the host, or remain on a private network. For a multi-adapter VM, document each adapter's purpose, network, IP address, DHCP behavior, and routing role.

Before adding the adapter

Select the target VM in the VMware Player library.
Make sure you are editing the intended VM. Hardware changes apply only to the selected machine.
If the VM is running, shut it down unless your VMware Player version and guest support safe hardware changes while powered on. Powering off is the safest and most predictable method.
Open Player, choose Manage, and select Virtual Machine Settings.
Review the existing network adapters and note which one is currently used for the default gateway or internet access.

Virtual Machine Settings is the VMware Player configuration area for managing virtual hardware such as memory, disks, USB controllers, and network adapters.

Add a virtual network adapter

In Virtual Machine Settings, open the Hardware tab.
Select Add to start the hardware-add workflow.
Choose Network Adapter from the hardware list.
Select the required connection type: Bridged, NAT, or Host-only.
Enable Connect at power on if the adapter should automatically be connected whenever the VM starts.
Complete the wizard, review the new adapter in the Hardware list, and save the settings.
Start or restart the VM as needed.

Adding an adapter and connecting an adapter are separate concepts. The hardware can exist in the VM configuration while its virtual cable is disconnected. An adapter marked to connect at power on should become available automatically when the VM starts, but its actual link state should still be checked in VMware Player and in the guest.

Choose the network connection type

The connection type determines which virtual or physical network the adapter uses and what systems can normally reach the guest.

Connection type	Network reachability	External network identity	Host-to-guest communication	Typical use case
Bridged	Can reach and participate in the physical LAN, subject to LAN policies.	The VM appears as a separate device with its own network identity and usually its own IP address.	Usually available through the LAN path, subject to firewalls and network rules.	A VM that must be reachable by other physical devices.
NAT	Can normally reach external networks through the host; unsolicited inbound access is restricted by default.	Outbound traffic is translated through the host's external network identity.	The host can communicate with the VM through the private NAT network, subject to configuration.	Internet access for a desktop or test VM without direct LAN exposure.
Host-only	Private virtual network; external access is isolated by default.	The VM uses an address on the host-only network rather than the physical LAN.	Designed for host-to-guest and guest-to-guest communication on that private network.	Private labs, service testing, and isolated management networks.

Bridged networking

Bridged networking connects the VM to the physical network through a network adapter on the host. The VM can appear as a separate device on the home, office, or other physical LAN. It may obtain an IP address from the physical network's DHCP service.

Use Bridged when other physical devices need to initiate connections to the VM or when the VM must participate directly in the same LAN as the host. Physical-network firewalls, wireless restrictions, port security, DHCP limits, and authentication policies still apply.

NAT networking

NAT networking places the VM on a private VMware virtual network and translates its traffic through the host's external network identity. The guest can usually access the internet or other external networks without appearing as a separate device on the physical LAN.

Use NAT when the VM needs outbound access but does not need direct inbound connections from physical LAN devices. The guest normally receives a private IP address, gateway, and DNS configuration from the NAT network's DHCP service.

Host-only networking

Host-only networking creates a private virtual network between the host and connected VMs. It remains isolated from the physical network by default, so it does not normally provide internet access.

Use Host-only for an isolated test environment, host-to-guest service testing, or communication among lab VMs. If the VM also needs internet access, add a separate NAT adapter and configure routing carefully.

Choosing a network mode by requirement

Requirement	Recommended mode	Reason	Considerations
VM needs to appear on the physical LAN	Bridged	It gives the VM direct participation in the physical network through the host.	Check LAN DHCP, firewall, Wi-Fi restrictions, and whether unknown devices are allowed.
VM needs outbound internet access while remaining behind the host	NAT	Traffic leaves through the host's network identity.	Inbound connections from the physical LAN are not normally available without additional configuration.
VM should communicate only with the host or isolated lab systems	Host-only	It provides a private virtual network without direct external-network access.	Use suitable host-only addresses and DHCP, or configure static addresses within the private range.
VM requires multiple network segments	A combination of modes	Each adapter can serve a different network purpose, such as NAT for updates and Host-only for lab traffic.	Use one intended default gateway and add specific routes for other networks.

Configure connection state

In the network adapter settings, enable Connect at power on when the guest should always see the adapter after startup. Also check the adapter's connected state in the VM window after startup. A disconnected virtual cable can prevent the guest from detecting a link even when the adapter hardware is present.

After starting the VM, open the guest operating system's network settings and confirm that the new interface reports an active link. If the interface is disabled in the guest, enable it there as well.

Verify the adapter in the guest operating system

Open the guest's device, network, or connection-management tools.
Identify the additional network interface. Compare its hardware address, interface name, or order with the existing adapter so you do not configure the wrong device.
Confirm that the interface is enabled and has link state up or connected.
Check its assigned IP address, subnet or prefix, default gateway, and DNS settings.
Determine whether the address came from DHCP or was configured statically.
Test only the destinations appropriate for the selected mode.

An IP address is the network address assigned to an interface. DHCP is the service that automatically supplies IP configuration. A successful test should match the network design:

For Host-only, test the host-only address on the host and another connected lab VM.
For NAT, test the NAT gateway, then an external IP address, and finally DNS name resolution.
For Bridged, test another device on the physical LAN and the LAN gateway, then test external access if required.

When two adapters have similar names, use the interface's IP subnet, MAC address, connection order, or temporarily disconnect one adapter in VMware Player to identify the other. Avoid changing the default route on the wrong interface.

Practical configurations

Dual-network lab VM

Suppose a test server already has a NAT adapter for updates and package downloads. Add a second Network Adapter, choose Host-only, and enable Connect at power on. The server can use NAT for outbound resources while communicating with the host and other lab VMs over the isolated Host-only network.

Give the Host-only interface an address from the host-only network's available range if DHCP is not being used. Do not assign the Host-only interface a competing default gateway unless the lab specifically requires custom routing.

VM exposed to a home or office LAN

If physical devices must connect to a service in the VM, add or configure a Bridged adapter. Confirm that the guest receives a valid address from the physical LAN or assign a static address that matches the LAN design. The VM is then subject to the LAN's DHCP, firewall, access-control, and security policies.

Internet access without direct LAN exposure

For a desktop test VM that needs outbound access but does not need to accept connections from the physical LAN, use NAT and leave Connect at power on enabled. The guest uses a private address and reaches external resources through the host.

Host-and-guest testing only

For testing a service from the host without placing the VM on the external network, use Host-only. Configure addresses from the Host-only range through DHCP or static settings. The host and guest can then communicate over the private virtual network.

Multi-adapter routing considerations

Each connected adapter creates another path into or out of the guest. The guest operating system chooses a path using its routing table. If two interfaces advertise default gateways, the result can be unpredictable: replies may leave through a different interface, connections may fail intermittently, or isolated traffic may be sent to the wrong network.

Choose one interface for general outbound traffic and its default gateway.
Leave the isolated interface without a default gateway when it only serves local lab traffic.
Add specific routes for networks reachable through the second interface.
Avoid overlapping IP ranges on different adapters.
Use DHCP where the network is designed to provide it; use static addresses only within the correct subnet and address plan.
Record each adapter's VMware mode, guest interface name, IP range, gateway, and purpose.

Troubleshooting

The adapter does not appear in the guest

Confirm that Network Adapter is listed in Virtual Machine Settings and that the hardware-add workflow was completed and saved.
Ensure the adapter is marked connected and that Connect at power on is enabled when appropriate.
Restart the guest. Some operating systems detect newly added hardware only during startup.
Check the guest device manager or network manager for a disabled device or missing driver.
Install or update suitable guest integration or network drivers if the guest does not support the presented virtual device.

A Bridged VM has no address or network access

Verify that the host itself has network connectivity.
Confirm that the adapter uses Bridged mode and, where VMware Player provides the choice, the intended physical host interface.
Check whether the physical network supplies DHCP and permits additional devices or leases.
Check guest IP settings, subnet, gateway, and firewall rules.
Use a static address only when it is valid for the physical LAN and does not conflict with another device.

A NAT VM reaches the host but not the internet

Test external connectivity from the host first.
Review the guest's NAT-network IP address, gateway, and DNS settings.
Reconnect the virtual adapter or restart the VM.
Review host firewall, VPN, endpoint-security, and other software that may interfere with virtualization networking.

A Host-only VM cannot reach the internet

This is normally expected. Host-only mode creates a private host-and-VM network and does not provide direct external-network access by default. Add a separate NAT or Bridged adapter if the VM needs external connectivity, then configure the guest's routes so the correct interface is used for each destination.

Connectivity is intermittent in a multi-adapter VM

Inspect the guest routing table for multiple default gateways.
Use one intended default gateway for general outbound traffic.
Add routes for isolated networks through the appropriate interface.
Check that the adapters do not use overlapping or incorrectly configured networks.
Document and test each interface separately before testing traffic between networks.

Summary

To add an adapter, power off the VM when possible, open Player > Manage > Virtual Machine Settings, select Hardware > Add, choose Network Adapter, select Bridged, NAT, or Host-only, and enable Connect at power on when required. Then verify the new interface, address, gateway, link state, and connectivity inside the guest. The correct mode depends on whether the VM must join the physical LAN, use the host for outbound access, or remain on an isolated private network.

For related background, see Virtual Networking Components and Networking Configurations. Detailed mode-specific guidance is available for Bridged networking, NAT networking, and Host-only networking.