VMware Player online course

Virtual Networking Components in VMware Player

Learn how VMware Player virtual switches, VMnets, virtual NICs, DHCP, and NAT work together across bridged, host-only, and NAT networking.

VMware Player networking is built from several software components that work together. The main components are virtual switches, guest virtual network adapters, the VMware virtual DHCP service, and the NAT device. The familiar networking modes—bridged, host-only, and NAT—are combinations of these components rather than separate physical networks.

This lesson explains the default VMnet mappings, the role of each component, platform-specific limits, and practical troubleshooting approaches for Windows and Linux hosts.

How VMware Player Virtual Networking Fits Together

A guest operating system communicates through a virtual network adapter, also called a virtual NIC. This emulated network card is presented to the guest as hardware. The adapter connects to a VMnet, which is VMware's numbered name for a virtual network or virtual switch.

A virtual switch is a software-based connection point that links virtual machines, host-side virtual adapters, physical host adapters, and VMware services in a way comparable to an Ethernet switch. Services such as virtual DHCP or NAT may be associated with a particular VMnet.

The selected networking mode determines how the VMnet connects to other components:

• Bridged networking connects the guest through VMnet0 to a physical network adapter on the host.
• Host-only networking connects participating guests and a host-side virtual adapter on VMnet1. It is normally private to the host and those guests.
• NAT networking connects guests to VMnet8. VMware DHCP can assign private addresses, and the NAT device provides outbound access through the host.

The guest adapter is always the attachment point between the guest operating system and the selected virtual switch. Changing the adapter's networking mode changes which VMnet and surrounding services it uses.

Virtual Switches and VMnet Networks

A VMnet is the numbered name assigned to a VMware virtual network. Common names include VMnet0, VMnet1, VMnet2, and other subsequent numbered networks. The number identifies the virtual switch; it does not by itself describe every service configured on that network.

VMware Player provides standard mappings for the most common modes:

Additional numbered VMnets can support isolated or custom arrangements. For example, separate VMnets can represent different test segments so that guests on one segment do not automatically share a local network with guests on another.

Virtual switch limits

The supported limits depend on the host platform:

These limits matter when designing larger labs. On Linux, a single VMnet cannot have more than 32 attached virtual network devices. On Windows, the number of devices attached to one virtual switch is unlimited under the stated platform limit, but the host still has a maximum of 20 virtual switches.

Guest Virtual Network Adapters

A virtual network adapter is an emulated NIC presented to the guest operating system. VMware Player adds an adapter when a virtual machine is created unless the hardware configuration is changed. The guest detects the adapter much like it detects a physical network card and loads an appropriate driver.

Common emulated adapter types include:

• AMD PCNET PCI Adapter
• Intel PRO/1000 MT Server Adapter

A single virtual machine can have up to 10 virtual network adapters. Each adapter can connect to a different VMnet. This allows one guest to participate in multiple network segments, such as a private host-only test network and an external network reached through bridged or NAT networking.

To configure an adapter, open the VM's virtual hardware settings and choose one of the networking modes. To create multi-network connectivity, add additional virtual NICs and assign each one to the required VMnet.

For the hardware configuration procedure, see Add a Virtual Network Adapter.

Virtual DHCP Service

DHCP, or Dynamic Host Configuration Protocol, automatically supplies network settings such as an IP address, subnet mask, gateway, and sometimes DNS information. VMware's virtual DHCP server provides this automatic configuration to guests on host-only and NAT networks when DHCP is enabled for those networks.

Bridged guests normally use the DHCP infrastructure on the external physical network instead. For example, a bridged guest connected to a home or office LAN typically requests an address from that LAN's router or DHCP server, not from VMware's virtual DHCP service.

DHCP is not the same as connectivity. A guest may receive a valid private address from VMware DHCP but still fail to reach external networks if the NAT device, host connection, or routing path is unavailable.

NAT Device

Network Address Translation (NAT) allows guests on a private NAT VMnet to reach external networks through the host. The NAT device translates outbound traffic from private guest addresses into traffic using an address usable on the host's external network.

The NAT device tracks active connections. When a response returns, it uses that connection state to translate and deliver the packet to the guest that initiated the traffic. This is why several NAT guests can share the host's external connection without each guest being placed directly on the physical LAN.

NAT differs from bridged networking in an important way: a NAT guest remains behind the VMware NAT device and is not directly presented as another device on the physical LAN. Outbound access is generally straightforward, while unsolicited inbound access requires appropriate NAT or port-forwarding configuration.

How the Components Relate in Each Mode

Bridged networking: VMnet0

In bridged mode, the guest's virtual network adapter connects to VMnet0. VMnet0 bridges that virtual connection to a physical network adapter on the host. The guest therefore behaves like another device on the external network and normally obtains its IP configuration from the external network's DHCP service.

Conceptually, the path is:

Guest operating system → virtual NIC → VMnet0 → host physical network adapter → external LAN

Use Configure Bridged Networking when the guest needs normal access to the same LAN as the host.

Host-only networking: VMnet1

In host-only mode, guest adapters and a host-side virtual adapter join VMnet1. The host and participating guests can communicate over this private virtual segment. VMware DHCP may assign addresses, but host-only networking has no inherent connection to an external network.

Conceptually, the path is:

Guest operating system → virtual NIC → VMnet1 → host-side virtual adapter and other host-only guests

Use Configure Host-Only Networking for a private lab reachable from the host but separated from the physical LAN.

NAT networking: VMnet8

In NAT mode, the guest adapter connects to VMnet8. VMware DHCP supplies a private address when enabled. Traffic destined for an external network leaves VMnet8 through the NAT device, which uses the host's network connection and maps return traffic back to the correct guest.

Conceptually, the path is:

Guest operating system → virtual NIC → VMnet8 → NAT device → host network connection → external network

Use Configure NAT Networking when a guest needs outbound internet or LAN access without being directly exposed on the physical LAN.

Component Roles at a Glance

Practical Configurations

Guest needs the same LAN access as the host

1. Open the VM's network adapter settings.
2. Select bridged networking, which uses the default VMnet0 path.
3. Ensure VMnet0 is associated with the correct active physical host adapter.
4. Configure the guest to obtain an address from the external LAN's DHCP service, unless the LAN requires a manual configuration.

Private lab reachable from the host

1. Connect the lab VMs to host-only networking, using the default VMnet1 path.
2. Leave VMware DHCP enabled if automatic private addressing is desired.
3. Use the host-side virtual adapter to communicate with the guests.
4. Do not expect external-network access unless an additional routing arrangement is deliberately added.

Isolated guest with outbound internet access

1. Connect the guest adapter to NAT networking, using the default VMnet8 path.
2. Allow VMware DHCP to provide the guest's private address and related settings.
3. Verify that the host itself can reach the external network.
4. Allow the NAT device to translate outbound guest traffic.

One VM on two network segments

Add two virtual NICs to the VM. Attach one to a host-only VMnet for private testing and the other to bridged or NAT networking for external connectivity. The guest operating system will see two network interfaces, each with its own VMnet connection and potentially its own IP configuration.

Larger virtual topology

Use separate numbered VMnet switches for distinct segments. Keep track of which guests attach to each VMnet, and observe the host platform's virtual-switch and per-switch attachment limits. On Linux, especially, a segment with more than 32 attached virtual network devices exceeds the stated per-switch limit.

Troubleshooting Virtual Networking

NAT or host-only guest receives no IP address

The likely component is the virtual DHCP server. Check the following:

• Confirm that the guest adapter is connected to the intended NAT or host-only VMnet.
• Verify that DHCP is available for that virtual network.
• Check that the guest NIC is enabled and configured to obtain an address automatically.

NAT guest has a private address but cannot reach external networks

The likely component is the NAT device or its path to the host. Check the following:

• Confirm that the adapter is attached to VMnet8 or the intended NAT network.
• Verify that the host itself has working external connectivity.
• Check that the VMware NAT service or device is operational.

Bridged guest cannot communicate on the physical LAN

The likely component is the VMnet0 bridge path. Check the following:

• Confirm that bridged mode is selected.
• Verify that VMnet0 is bridged to the correct active physical host adapter.
• Check whether the external network permits another device or MAC address.

Guests expected to be isolated can communicate

The likely component is the virtual switch assignment. Compare the VMnet assignment of every guest adapter. If separate segments are required, move one group of guests to a different numbered VMnet.

A VM cannot be given another network connection

The likely component is an adapter or host-side limit. Count the VM's existing adapters and ensure it remains within the maximum of 10 virtual NICs. Also check the applicable host-side virtual-switch and per-switch device-attachment limits.

Exam-Relevant Notes

• VMnet0 is the default bridged network.
• VMnet1 is the default host-only network.
• VMnet8 is the default NAT network.
• VMware virtual DHCP applies to host-only and NAT networks; bridged guests normally use the external network's DHCP.
• NAT translates private guest traffic and tracks return packets; it does not put the guest directly on the physical LAN.
• Windows supports up to 20 virtual switches and an unlimited number of attached virtual network devices per switch.
• Linux supports up to 255 virtual switches and up to 32 attached virtual network devices per switch.
• A VM can have up to 10 virtual network adapters, and each adapter can attach to a different VMnet.

For the broader relationship between the three common modes, see Networking Configurations. For VM hardware changes, see Add a Virtual Network Adapter.