VMware Workstation Player Networking Configurations Overview

Learn how bridged, NAT, host-only, and custom VMware Workstation Player networks work, when to use each mode, and how to verify connectivity.

A virtual machine (VM) is a guest computer running on a host system: the physical computer and operating system running VMware Workstation Player. A VM connects to a virtual network through a simulated virtual network adapter, rather than using a physical network adapter as an ordinary computer does.

The selected network configuration determines whether the guest operating system can reach the internet, communicate with the host, appear on the local-area network (LAN), or remain isolated. VMware Workstation Player provides three primary modes: bridged, NAT, and host-only. Where supported by the installed VMware networking tools, custom VMnet networks can also be selected or created.

VMware virtual networking at a glance

A VM's network adapter connects to a VMware virtual switch or virtual network. That virtual network may connect onward to a host physical adapter, provide NAT and DHCP services, or remain entirely within the host computer.

Bridged: connects the VM to the same external LAN as the host.
NAT: places the VM on a private subnet and translates its outbound traffic through the host.
Host-only: creates an isolated segment for the host and selected VMs.
Custom: assigns a VM to a particular VMnet for a segmented or specialized topology.

Mode	Default VMnet	Connection scope	External LAN visibility	Internet access	Host-to-VM communication	Typical address source	Typical use case
Bridged	VMnet0	Host physical network and LAN	Yes; separate LAN device	Usually, through the LAN	Usually, through the LAN	LAN DHCP or static LAN address	Services or systems that must participate directly on the LAN
NAT	VMnet8	Private VM subnet through host NAT	No direct presence	Usually yes, outbound	Often yes, through the private network	VMware virtual DHCP or compatible static address	Updates, downloads, and general outbound access
Host-only	VMnet1	Host and attached VMs only	No	No, unless another routing design is added	Yes, through a host virtual adapter	VMware virtual DHCP or compatible static address	Isolated labs and host-to-VM administration
Custom	Selected VMnet	Depends on its configuration	Depends on its configuration	Depends on its configuration	Depends on its configuration	Configured DHCP or static addressing	Separate lab segments and controlled topologies

Bridged networking

Bridged networking connects a VM through the host's physical network adapter to the same external LAN used by the host. The VM appears to other LAN devices as a separate computer and normally receives its own LAN address from DHCP or uses a manually assigned address.

The default bridged virtual network is VMnet0. Bridging is appropriate when the VM must access local network resources, communicate directly with other LAN devices, or provide a service that should be reachable from the LAN.

Bridged networking dependencies and cautions

The host must have a usable wired or wireless network connection.
The LAN must provide DHCP, or the guest must have correct static IP, subnet, gateway, and DNS settings.
Some networks restrict additional devices through MAC filtering, 802.1X, endpoint controls, or network access policies.
Wireless adapters may handle bridging differently from wired adapters, depending on the host operating system and driver.
Corporate VPN software can redirect traffic, disable bridging, or select an unexpected host interface.
Public or untrusted networks may expose the VM to other devices. Use host firewalls and guest firewalls, and avoid bridging when direct LAN exposure is unnecessary.

NAT networking

Network Address Translation (NAT) places the VM on a private subnet whose address is not directly exposed on the external network. The host translates guest traffic so the VM can commonly reach external networks while sharing the host's external network identity.

The default NAT network is VMnet8. VMware's virtual DHCP service can automatically assign the guest an address and other IP settings on this private network. NAT is a suitable default when a VM needs outbound internet access for package downloads, software updates, or testing but does not need to be an independently reachable LAN device.

Inbound connections from the physical network generally cannot reach a NAT guest directly. Where supported, configure port forwarding: traffic arriving at a host-side port is sent to a specified private guest address and service port. The guest service and its firewall must also permit the connection. VMware Workstation Player supports one NAT network limitation described for the product, so separate NAT segments may not be available as they are in more extensive VMware networking configurations.

Host-only networking

Host-only networking creates an isolated virtual network contained on the host computer. The host and VMs attached to that network can communicate, but the network does not directly connect those VMs to the physical LAN or internet.

The default host-only network is VMnet1. VMware creates a host virtual network adapter that is visible to the host operating system and makes the host a participant in the segment. A virtual DHCP service may assign addresses to attached guests.

Use host-only networking for isolated labs, host-to-VM administration, testing, and controlled communication among VMs attached to the same host-only network. Host-only mode alone does not provide normal external network or internet access; adding routing, internet sharing, NAT, or another adapter changes that design.

Custom virtual networks

A custom virtual network is a separately defined or selected VMware VMnet used to separate lab segments, assign VMs to distinct virtual networks, or build a controlled topology. In a VM's network adapter settings, you select a particular VMnet rather than choosing the standard Bridged, NAT, or Host-only label.

Custom networks are distinct from the default VMnet0, VMnet1, and VMnet8 networks. Their availability and management options vary with the VMware Workstation Player version, host operating system, installed virtual networking components, and administrative permissions. A custom VMnet might be isolated, connected to a host adapter, or connected through another configured service.

Virtual networking components

Component	Bridged	NAT	Host-only	Purpose
VM virtual network adapter	Required	Required	Required	Simulated network interface inside the guest
VMware virtual switch or VMnet	VMnet0	VMnet8	VMnet1	Connects the guest adapter to the selected virtual network
Host physical adapter	Used for external LAN access	Used indirectly by NAT	Not used directly	Connects the host to a wired or wireless physical network
Virtual DHCP service	Usually the LAN DHCP service	Commonly assigns private guest settings	Can assign isolated-network settings	Automatically supplies IP configuration where enabled
NAT service	Not normally involved	Translates private guest traffic	Not normally involved	Provides outbound access through the host
Host virtual adapter	Not essential	May be present for host access	Provides host participation	Network interface created in the host operating system

Network settings exist on both sides of the connection. VMware settings determine how the virtual adapter connects, while the guest operating system must enable its adapter and use DHCP or a compatible static configuration. The host operating system may display VMware-created virtual adapters for applicable networks.

Adding and assigning a VM network adapter

Power off the VM when adding or changing virtual hardware, unless the product and guest support the change while running.
Open the VM's settings and add or select a Network Adapter device.
Choose Bridged, NAT, Host-only, or a specific custom VMnet.
Ensure the adapter is enabled, marked Connected, and configured to connect when the VM starts.
Start the VM and configure its guest adapter for DHCP or a compatible static IP address.

A VM can have multiple virtual adapters. This is useful when a lab requires connections to more than one network segment. Each adapter should have a deliberate role, and the guest operating system must be configured so that gateways and routes do not accidentally defeat the intended isolation.

VM adapter 1: NAT       - outbound updates and downloads
VM adapter 2: Host-only - isolated lab communication
Lab VM adapters: Host-only only

Choosing the correct networking mode

Requirement	Recommended mode	Reason	Important caveat
Behave as an independent device on the office or home LAN	Bridged	Receives or uses an address on the physical LAN	LAN policy, wireless behavior, VPNs, and firewalls may restrict it
Reach the internet for updates without direct LAN exposure	NAT	Uses a private subnet and host translation	Inbound access requires port forwarding or another design
Communicate with the host and selected VMs only	Host-only	Keeps traffic on an isolated host segment	No normal internet access by itself
Build separate internal lab segments	Custom VMnet	Allows controlled VM-to-VM topology	Management features depend on the installed tools and permissions
Provide updates while preserving an isolated lab network	Dual adapter: NAT plus host-only	Separates outbound access from internal lab traffic	Configure guest routes and firewalls carefully

Practical configurations

Office-LAN web server: use bridged networking through VMnet0. The VM should receive an address appropriate for the physical LAN and be treated as a separate device.
Linux update workstation: use NAT through VMnet8 with guest DHCP enabled. The VM can generally make outbound connections using the host's connectivity.
Isolated practice lab: use host-only networking through VMnet1. The host and VM can communicate on an isolated segment.
Security lab: give an administrative VM one NAT adapter and one host-only adapter; attach target VMs only to the host-only network. The administrative VM can obtain updates while the internal lab remains separate.
NAT-hosted service: use supported NAT port forwarding to map a host port to the guest service port, or choose bridged networking when direct LAN presence is required.

Basic verification

Open the VM settings and verify the selected mode or VMnet.
Confirm that the virtual adapter is enabled, connected, and set to connect at startup.
Inside the guest, inspect the IP address, subnet mask or prefix, default gateway, and DNS servers.
Test the communication path relevant to the design: guest-to-host, guest-to-LAN, guest-to-internet, or guest-to-other-VM.
Test DNS separately from basic IP connectivity. A working IP route does not prove that DNS is configured correctly.

# Illustrative guest checks; command names vary by guest OS
ip address
ip route
ping <default-gateway>
ping <known-IP-address>
nslookup example.test

For inbound NAT access, map a host listening port to the guest's private IP address and service port in the VMware NAT configuration where available. Confirm that the guest service is listening and that both host and guest firewall rules permit the connection.

Troubleshooting common failures

NAT guest has no address or an unexpected private address

Confirm the adapter is set to NAT, connected, and enabled in the guest.
Confirm guest DHCP is enabled if automatic addressing is intended.
Check whether the VMware DHCP and NAT services are running.
Compare any static guest configuration with the VMnet8 subnet and gateway.

Bridged guest cannot reach the LAN

Verify that the host has a working physical connection.
Confirm that bridging uses the appropriate host adapter, especially when both wired and wireless adapters exist.
Try guest DHCP or validate the static LAN address, subnet, gateway, and DNS values.
Check wireless restrictions, VPN state, 802.1X, MAC filtering, and corporate network policy.

Host-only guest cannot access the internet

This is normally expected. Host-only networking provides isolation, not ordinary external access. Add a NAT or bridged adapter only when the lab design requires external connectivity.

Host cannot contact a host-only guest

Compare host and guest addresses to confirm they are on the same host-only subnet.
Confirm the host virtual adapter is enabled.
Confirm the VM is attached to VMnet1 or the intended custom VMnet.
Check host and guest firewall rules and ensure the tested protocol is allowed.

LAN device cannot reach a service in a NAT guest

NAT hides the guest's private address from the external network.
Use bridged networking for direct LAN presence, or configure supported NAT port forwarding.
Verify the guest service is listening on the intended port.
Check firewall rules on the host and guest.

Exam-relevant notes

VMnet0 is the default bridged network.
VMnet8 is the default NAT network.
VMnet1 is the default host-only network.
Bridged mode gives the VM separate LAN visibility; NAT gives private outbound connectivity; host-only provides an isolated host-and-VM segment.
DHCP address assignment and NAT translation are separate functions: DHCP supplies IP settings, while NAT translates traffic between private and external networks.
A virtual adapter must be connected in VMware and configured inside the guest before network tests can succeed.

For related VM configuration topics, see the VMware Workstation Player Course, VMware Workstation Player Preferences Menu, and How To Limit Network Bandwidth For A VM.