VMware ESXi and vSphere Cluster Management

Configure Host-Only Networking in VMware Player

Learn how to connect an existing VMware Player VM to a private host-only network for host-to-guest communication without external network access.

Host-only networking connects a virtual machine to a private network on the physical host. The guest can communicate with the host and with other virtual machines attached to the same host-only network, but it normally cannot reach the Internet or the external physical LAN through that adapter.

This guide explains how to configure an existing VMware Player virtual machine, select a custom host-only network, verify connectivity, and troubleshoot common problems.

What host-only networking does

Host-only networking is a VMware virtual networking mode that creates a private network between the host computer and attached virtual machines. The host operating system is the operating system running VMware Player. The guest operating system is the operating system installed inside the virtual machine.

The guest uses a software-defined virtual network adapter. VMware also installs a host-side virtual adapter, which gives the host an address on the same private subnet. Traffic can pass between these adapters without using the host's physical Ethernet or Wi-Fi network.

The guest can normally communicate with the host through the host-only network.
Guests attached to the same host-only network can normally communicate with one another, subject to firewall rules.
The guest normally cannot access the Internet or the physical LAN through a host-only adapter.
Host-only networking does not automatically make every service secure; host and guest firewalls still control which traffic is accepted.

Typical uses include isolated development labs, local service testing, private management access, and training environments that must not contact external networks. Malware-analysis or security-training environments require additional controls, such as safe snapshots, restricted file sharing, and careful handling of samples; host-only mode alone is not a complete safety guarantee.

Host-only network components

A typical VMware Player installation creates a default host-only network named VMnet1. The exact available networks can vary by VMware installation and host operating system.

Guest virtual network adapter: The virtual hardware interface presented to the VM.
Host-side virtual adapter: The software interface installed in the host operating system. It represents the host on the private network.
Virtual DHCP server: VMware's DHCP service can automatically assign IP addresses to guests on the host-only subnet.
Private subnet: The internal IP address range used by the host-only network. It is intended for local virtual-network communication rather than direct public-Internet routing.

For example, the host-side adapter and guest might receive addresses such as 192.168.###.1 and 192.168.###.20 on the same subnet. The exact range depends on the VMware network configuration. Do not assume that a particular example address is present on your computer.

Prepare before changing the VM

Confirm that VMware Player is installed and that the target VM appears in the Player library.
Shut down the VM, or ensure that its virtual hardware settings can be changed safely. Avoid changing network hardware while important guest services are running.
Record the current network mode. A VM using NAT or bridged networking may currently depend on Internet or physical-LAN access.
Make sure the guest's network adapter is enabled.
Plan to use DHCP in the guest unless you intentionally need a static address. A static address must belong to the selected host-only subnet and must not conflict with VMware DHCP assignments.

Configure an existing VM with the default host-only network

Select the virtual machine in the VMware Player library.
Open Player > Manage > Virtual Machine Settings.
On the Hardware tab, select Network Adapter.
Under Network connection, select Host-only: A private network shared with the host.
Click OK to save the setting.
Start or resume the VM.
Allow the guest operating system to obtain an IP address automatically, or apply a compatible static configuration.

When the standard Host-only option is selected, VMware Player normally connects the adapter to the default host-only network, commonly VMnet1.

Use a custom host-only network

A custom virtual network is a specifically selected VMware network rather than the default choice. Custom host-only networks are useful when separate labs must be isolated from one another or when a lab requires a predefined private subnet.

Open Player > Manage > Virtual Machine Settings.
Select Hardware > Network Adapter.
Choose Custom under Network connection.
Use the specific virtual-network list to select the intended host-only network.
Confirm that the selected network is configured as host-only, not NAT or bridged.
Confirm that its address range is compatible with the guest's DHCP or static IP configuration.
Click OK, start the VM, and verify its address.

Selecting Host-only normally uses the default host-only network. Selecting Custom lets you choose a particular host-only network, such as a separately configured VMnet network. If two labs use different host-only networks, machines in one lab are separated from machines in the other unless an intentional routing path is added.

Configure a new VM during creation

When creating a new virtual machine, its virtual hardware can be customized before creation is complete.

In the New Virtual Machine wizard, proceed to Customize Hardware.
Select Network Adapter.
Set Network connection to Host-only, or choose Custom and select the required host-only virtual network.
Complete the wizard and configure the guest operating system's network interface.

Verify addressing, connectivity, and isolation

Verification should check both sides of the virtual link: the guest interface and the host-side virtual adapter.

Check a Windows guest

ipconfig /all
ping <host-only-peer-IP>

ipconfig /all displays the guest adapter's address, subnet mask, DHCP information, and other details. Replace <host-only-peer-IP> with the host's host-only adapter address when testing guest-to-host communication.

Check a Linux guest

ip addr
ip route
ping -c 4 <host-only-peer-IP>

ip addr shows interface addresses, while ip route shows the routes selected by the guest. The host-only subnet should be associated with the intended virtual interface.

Perform the tests

Confirm that the guest received an address on the expected private subnet.
Inspect the host's host-only virtual adapter and confirm that it has an address on the same subnet.
Ping the host from the guest, or test another permitted local service.
Optionally test the guest from the host. A failed ping may be caused by guest or host firewall rules blocking ICMP.
Confirm that Internet access is unavailable when the VM has only a host-only adapter and no additional routing arrangement.

Item	Expected state	How to verify
VM network adapter setting	Host-only or the intended custom host-only network	Open Virtual Machine Settings and inspect Network Adapter
Selected virtual network	The expected default or custom VMnet network	Inspect the Network connection selection
Guest IP address	An address on the selected private subnet	Use `ipconfig /all` or `ip addr`
Host virtual adapter IP address	An address on the same private subnet	Inspect the host's virtual network adapters
DHCP availability	VMware virtual DHCP is available when DHCP is intended	Check the guest's DHCP result and VMware networking configuration
Host-to-guest connectivity	Ping or an allowed local service works	Test from either side while accounting for firewalls
External connectivity behavior	No Internet access through the only host-only adapter	Test deliberately and confirm the result matches the security design

Compare VMware network modes

Mode	Host-to-guest communication	Guest Internet access	Physical LAN visibility	Typical use case
Host-only	Normally available through the private host-only network	Normally unavailable through that adapter	Normally isolated from the physical LAN	Private labs and host-to-guest development
NAT	Usually available through VMware's virtual NAT arrangement, subject to configuration and firewalls	Normally available outbound through host address translation	Not usually presented as a direct physical-LAN participant	Guest Internet access without direct LAN participation
Bridged	Usually available as communication on the physical network	Normally available if the physical network provides it	Guest participates directly on the same physical network as the host	Testing a VM as a device on the LAN
Custom host-only network	Available to the host and VMs attached to that selected private network	Normally unavailable through that adapter	Normally isolated from the physical LAN	Separate labs or a chosen private subnet

A VM can have more than one virtual network adapter. For example, one adapter can provide private host-only management while a second adapter uses NAT for updates. This is no longer a fully isolated guest: services, routes, DNS settings, and firewall rules must be designed deliberately.

Practical configurations

Single isolated development VM

Attach one existing VM adapter to standard Host-only, normally VMnet1. The host and guest should receive addresses on the same private subnet and communicate locally. The guest should not have Internet connectivity through that adapter.

Separated training labs

Attach the VMs for each lab to a different custom host-only network. Machines on one selected network should not communicate directly with machines on another selected network unless you intentionally add routing.

Private management plus Internet access

Keep one adapter on host-only for host-to-guest management and add a second adapter using NAT for outbound access. This supports updates but changes the isolation model. Do not add the second adapter unless its exposure is intended.

Static guest addressing

A guest can use a static address if it belongs to the selected host-only subnet, uses the correct subnet mask, and does not conflict with DHCP leases or another device. A wrong subnet mask, duplicate address, or incompatible route can prevent communication even when the adapter is connected correctly.

Troubleshoot common problems

The guest has no address or an unexpected address

Reopen Virtual Machine Settings and confirm Host-only or the intended Custom network is selected.
Verify that the guest network interface is enabled.
Renew the guest's DHCP lease where applicable.
Confirm that the VMware host-only network and virtual DHCP components are present and active.
If using a static address, correct the IP address, subnet mask, and gateway for the selected network design.

The host and guest have addresses but cannot communicate

Compare the host virtual adapter and guest interface prefixes. They must be on compatible subnets.
Check host and guest firewall rules. ICMP ping may be blocked even when another permitted TCP service works.
If the VM has multiple adapters, inspect its routing table to ensure traffic for the host-only subnet uses the intended interface.
Test an allowed local service instead of relying only on ping.

The guest cannot reach the Internet after the change

This is normally expected when the only adapter is host-only, especially if the VM previously used NAT or bridged mode. If Internet access is required, choose NAT or bridged networking as appropriate, or add a second adapter while accepting the resulting exposure.

The custom network is not listed

Verify that the custom network exists and is configured as host-only in the applicable VMware networking configuration tools.
Use the default VMnet1 network when a separate custom network is not required.
If the host-only adapter or VMware networking services are missing, repair or reinstall the VMware networking components according to local administrative policy.
Check whether permissions prevent changes to host networking configuration.

Operational and security checklist

Use clear VM and network names when managing multiple isolated labs.
Record the selected network mode before making changes.
Do not assume host-only provides Internet access.
Do not assume host-only makes guest services secure; configure host and guest firewalls.
Keep sensitive services bound to the intended interface where possible.
Add NAT or bridged adapters only when the resulting network exposure is understood and required.
Verify both connectivity and isolation after every network-mode change.

Exam-relevant notes

Host-only: private communication between the host and attached VMs; no external access by default.
VMnet1: the commonly preconfigured VMware host-only network.
NAT: normally gives the guest outbound network access through host address translation.
Bridged: places the guest directly on the physical network.
A custom network must actually be configured as host-only and must use an address range compatible with the guest.
Firewall rules can prevent ping even when virtual networking and IP addressing are correct.