This guide provides a "Zero to Hero" overview of virtual networking. It covers the theory and practical application of the four most popular network modes in VMware Workstation Pro: LAN Segment, Host-Only, NAT, and Bridged.
A LAN Segment represents the most basic networking setup. It creates a pure Layer 2 network that is completely isolated.
In this mode, there are no gateways and no DHCP servers provided by the virtualization software. It acts as an isolated broadcast domain, making it ideal if you do not want your Virtual Machines (VMs) to interact with your host PC or your physical network.
Since there is no DHCP, you must manually configure static IP addresses on your VMs (e.g., configuring Windows and Linux clients to use the 172.16.1.x range).
Host-Only networking is very similar to a LAN segment in that it is an isolated environment, but with one key difference: the Host PC is brought into the network.
The Host PC can communicate with the VMs, and the VMs can communicate with the Host. However, the Host does not act as a gateway, meaning there is still no internet access for the VMs. A significant advantage of this mode is that VMware can provide a DHCP server for this network.
To configure this, you use the Virtual Network Editor in VMware (typically VMnet1). You can define the subnet IP (e.g., 172.16.2.x) and enable the local DHCP service.
NAT mode is the standard way to give VMs internet access while keeping them behind a private IP address.
In this scenario, the Host PC acts like a home router. It performs Network Address Translation (NAT) between the virtual network and the physical network. The VMs sit behind the Host, using the Host's IP to traverse out to the internet.
This is configured via VMnet8 in the Virtual Network Editor. You can set the Subnet IP, Gateway IP (often ending in .2), and DHCP settings.
When configured correctly, a VM can ping external addresses (like google.com) because the Host routes the traffic.
Bridged mode connects the VM directly to the physical network, bypassing the Host's NAT functions.
The Host PC effectively "clones" its network adapter for the VM. The VM becomes a first-class citizen on your physical LAN, receiving its own IP address directly from your physical home router.
In the Virtual Network Editor (VMnet0), it is recommended to select the specific physical adapter you are using (e.g., Intel Wi-Fi) rather than leaving it on "Automatic".
If you check the IP address inside the VM, it should match your physical network range (e.g., 192.168.1.x) rather than a virtual private range.
ipconfig /release
ipconfig /renew
You can combine these modes to create complex labs. For example, when setting up a firewall VM (like pfSense):
This allows client VMs (like Linux Mint) to sit on the isolated LAN Segment while using the virtual firewall to route traffic out to the internet.