VMware ESXi and vSphere Cluster Management
VMware Workstation Player Networking Configurations Overview
Learn how bridged, NAT, host-only, and custom VMware Workstation Player networks work, including VMnet defaults, adapter setup, isolation, troubleshooting, and use cases.
VMware Workstation Player gives each guest virtual machine (VM) one or more simulated network interfaces. Each interface can attach to a different virtual network type. The selected mode determines how the guest receives an IP address, which systems can reach it, whether it can access the internet or physical LAN, and how isolated it is.
The host system is the physical computer running VMware Workstation Player. The guest virtual machine is the operating system and virtual hardware running inside Player. The external physical network is the host's Ethernet or Wi-Fi network, including its LAN, router, and internet connection. VMware also creates virtual networks and supporting services inside the host.
Virtual networking components
A VM's virtual network adapter is a simulated network interface presented to the guest operating system. In the VM settings, you connect this adapter to a networking mode such as bridged, NAT, host-only, or a selected custom VMnet.
- VMnet identifiers: Names such as VMnet0, VMnet1, and VMnet8 identify VMware virtual networks.
- Host virtual adapters: Host-only and some NAT configurations provide virtual interfaces in the host operating system so that the host can communicate with private guest networks.
- Virtual DHCP: VMware DHCP can automatically assign IP addresses, subnet masks, gateways, and related settings on applicable private virtual networks.
- NAT service: The VMware NAT service translates traffic from guests on the NAT network so they can use the host's external network connection.
These components cooperate as a path: the guest sends traffic through its virtual adapter, VMware connects that adapter to the selected VMnet, and the VMnet either bridges the traffic to a physical adapter, keeps it on the host, or routes and translates it through a VMware service.
Default VMware virtual networks
| Virtual network | Default role | Primary connectivity model |
|---|---|---|
| VMnet0 | Bridged | Connects the guest to a selected physical network adapter on the host. |
| VMnet1 | Host-only | Provides a private network between the host and VMs attached to it. |
| VMnet8 | NAT | Provides a VMware-managed private subnet with outbound traffic translated through the host. |
Bridged networking
Bridged networking connects the guest to an external network through a physical network adapter on the host. The guest behaves like a separate device on the same LAN as the host, rather than sharing the host's LAN address through NAT. The default bridged network is VMnet0.
In a typical bridged setup, the guest obtains an address from the physical LAN's DHCP service. It can also use a static address if that address, subnet mask, gateway, DNS settings, and any required access controls are appropriate for the LAN.
- Use bridged mode when a VM must join a home or office LAN.
- Use it when permitted LAN devices must reach a service running in the guest.
- Use it when testing software that must appear as a separate network host.
Bridged mode gives the guest more direct LAN visibility, but it also exposes the guest to the physical network's rules and threats. Other permitted devices may discover or connect to it, and network controls may restrict it. The host must have a usable physical adapter. If the host has Ethernet, Wi-Fi, VPN, or other adapters, the bridge must use the intended one. An incorrect selection can leave the guest without a usable LAN connection.
NAT networking
NAT, or Network Address Translation, places the guest on a VMware-managed private network and translates its outbound traffic through the host's external network identity. The default NAT network is VMnet8, and Workstation Player supports one NAT network.
The guest normally receives a private-subnet address from VMware's virtual DHCP service. Its default gateway is associated with the VMware NAT service. When the guest connects outward, NAT replaces the guest's private source address with an address usable through the host's physical network.
- The guest does not have its own independently visible IP address on the physical LAN.
- The guest can usually access the internet and external LAN resources when the host can access them.
- Other physical-LAN devices generally cannot initiate connections directly to the guest's private address.
NAT is useful when a VM needs web access, software updates, or outbound LAN access without appearing as a separate addressed machine on the physical network. This normally provides less inbound exposure than bridged mode, but it does not replace guest firewalling or secure application configuration.
To publish a service inside a NAT guest, configure port forwarding. A port-forwarding rule maps a listening port on the host side to the guest's private IP address and service port. For example, a host-side TCP port can be directed to the guest's TCP web-service port. Validate the guest service, guest firewall, host firewall, and forwarding rule together.
Host-only networking
Host-only networking creates an isolated virtual network contained on the host computer. The default host-only network is VMnet1. A host-side virtual adapter appears in the host operating system, allowing the host to communicate with guests on that network.
Guests attached to the same host-only network can communicate with one another, and the host can communicate with them. Host-only networking does not inherently provide access to the physical LAN or internet. Additional routing or sharing would change that isolation and should be planned deliberately.
- Build private test labs without exposing test services to the physical network.
- Create isolated training or malware-analysis environments, while still following safe handling practices.
- Provide a private management network between the host and appliances.
- Develop and test systems that should communicate only with the host or selected local VMs.
Custom virtual networks
A custom virtual network is a selected or user-defined VMnet used for specialized connectivity or segmentation. Instead of attaching every adapter to the standard defaults, you can assign VM adapters to a chosen VMnet and use that network to separate groups of systems or construct a multi-network lab.
Before creating or selecting a custom network, plan:
- The private subnet and whether it overlaps with the host LAN, VPNs, or other VMnets.
- Whether VMware DHCP should assign addresses or whether guests will use compatible static addresses.
- Whether the host needs a virtual adapter for host-to-guest management.
- Whether the network is associated with NAT where applicable, or must remain isolated.
- Which VMs belong to each segment and what routing, firewall, or isolation boundary is required.
For example, one custom VMnet can represent an internal server segment while another represents a test-client segment. A router VM with adapters in both networks can then be used to test routing and firewall policies without placing every lab system directly on the physical LAN.
Comparison of VMware Workstation Player networking modes
| Mode | Default VMnet | Guest address source | Physical LAN visibility | Host-to-guest connectivity | Internet/external access | Common use cases |
|---|---|---|---|---|---|---|
| Bridged | VMnet0 | Usually the physical LAN DHCP service, or an appropriate static configuration. | Guest appears as a separate permitted device on the LAN. | Normally available through the LAN. | Uses the physical network directly. | Joining an office or home LAN; testing independently reachable services. |
| NAT | VMnet8 | VMware virtual DHCP on a private subnet, or a compatible static configuration. | Guest is not independently addressed on the physical LAN. | Usually available through the host-side virtual network. | Usually available through VMware NAT when the host has connectivity. | Updates and internet access with reduced direct LAN exposure. |
| Host-only | VMnet1 | Usually VMware virtual DHCP or a compatible static configuration. | No inherent physical LAN visibility. | Available through the host's virtual adapter. | Not provided inherently. | Private labs, management, development, and isolated testing. |
| Custom virtual network | User-selected VMnet | Depends on the custom network's DHCP or static-address plan. | Depends on the network's configuration and associations. | Depends on whether a host virtual adapter is present. | Depends on NAT, routing, or other deliberate configuration. | Separated VM groups and multi-network topologies. |
Selecting the right network mode
| Requirement | Recommended mode | Reason | Important limitation or consideration |
|---|---|---|---|
| Guest must be independently reachable on the LAN | Bridged | The guest joins the physical network as a separate device. | It depends on the selected physical adapter and is subject to LAN access controls. |
| Guest needs outbound access without an independent LAN identity | NAT | Private guest traffic is translated through the host. | Inbound access requires port forwarding or a different design. |
| Guest must communicate only with the host or local VMs | Host-only | Traffic stays on a host-contained virtual network. | It has no inherent internet or physical-LAN access. |
| Lab requires multiple isolated segments | Custom virtual network | Selected VMnets can separate systems and represent different network zones. | Subnet, DHCP, host-adapter, routing, and isolation settings require deliberate planning. |
Consider security as well as convenience. Bridged mode has the greatest direct LAN exposure. NAT commonly allows outbound access while limiting unsolicited inbound connections. Host-only provides the strongest default separation from the physical network. Custom networks can provide precise segmentation, but their behavior depends on how they are configured.
Using more than one virtual network adapter
A VM can need multiple adapters when it must participate in separate networks. A test appliance might use one adapter on VMnet8 for outbound updates and a second adapter on VMnet1 for private host management. A router or firewall VM might use separate adapters for two custom lab segments.
Multiple adapters introduce routing and security considerations. Configure the guest's routes, gateways, DNS behavior, and firewall rules intentionally. Avoid assigning competing default gateways unless the guest operating system is configured to use them correctly.
Adding and configuring a virtual network adapter
- Open the target VM's settings in VMware Workstation Player.
- Locate the existing virtual network adapter.
- Choose Bridged, NAT, Host-only, or a custom virtual network.
- If the VM needs another connection, add a virtual network adapter and configure the new adapter separately.
- Enable the connection option that connects the adapter when the VM starts if immediate network access is required.
- Start or resume the guest and configure its operating system for DHCP, or assign a static address compatible with the selected network.
After changing modes, the guest may retain an old address, route, or DNS configuration. Disconnect and reconnect the adapter, renew the guest's DHCP lease, restart its network stack, or restart the guest when necessary. A static configuration that worked on a bridged LAN will usually be wrong on a VMware private subnet, and vice versa.
Practical configuration examples
Separate computer on an office LAN
Attach the VM's adapter to bridged networking using VMnet0. The guest should obtain an address from the office LAN's DHCP service or use an approved static address. Permitted LAN devices can then reach the guest as they would another network host.
Internet access without separate LAN addressing
Attach the adapter to NAT using VMnet8. VMware DHCP supplies a private address, and the NAT service translates outbound traffic through the host. This is appropriate for updates and browsing when direct inbound LAN access is not required.
Private development server
Attach the server to host-only networking using VMnet1. The host and guest communicate over the host-only virtual adapter, while the server remains separated from the physical LAN unless additional routing is intentionally added.
Isolated multi-VM lab
Assign participating VM adapters to a custom virtual network. Systems on that VMnet can communicate within the planned segment while remaining separated from unrelated networks. Add a second network or a router VM only when the lab requires controlled communication between segments.
NAT plus private management
Give an appliance two adapters: one attached to VMnet8 for outbound access and one attached to VMnet1 for host management. The host uses the private management address, while the appliance uses NAT for external resources.
Troubleshooting networking problems
A bridged guest cannot obtain an address or reach the LAN
- Verify that the host's intended Ethernet or Wi-Fi adapter is active and has LAN connectivity.
- Confirm the VM is bridged and that the bridge uses the intended adapter when multiple adapters exist.
- Check whether the physical network restricts unknown devices, additional MAC addresses, or wireless bridging.
- Check that the guest has a valid LAN address, subnet mask, default gateway, and DNS configuration.
- Use a static address only when it is permitted and matches the physical network's addressing plan.
A NAT guest has no internet access
- Confirm that the host itself can reach the intended external network.
- Verify that the guest has an address on the NAT private subnet and a valid default route.
- Test IP connectivity separately from DNS resolution to distinguish routing from name-service problems.
- Confirm that NAT networking is selected and the adapter is connected.
- Check whether host firewall or security software is blocking VMware NAT or DHCP components.
A host-only guest cannot communicate with the host
- Verify that the guest is attached to the intended host-only VMnet.
- Confirm that the host-side virtual adapter exists and is enabled.
- Compare the host and guest addresses and subnet masks.
- Check guest and host firewalls.
- Test basic reachability before testing application ports.
An external device cannot connect to a NAT guest service
- Remember that NAT does not make the guest directly visible on the physical LAN.
- Use bridged mode if the service must be directly reachable as a LAN host and the network permits it.
- If NAT is required, configure a port-forwarding rule from a host-side listening port to the guest's private IP and service port.
- Verify that the guest service is listening on the expected interface and port and that guest and host firewalls allow the connection.
Summary
Choose bridged networking when the VM must appear on the physical LAN, NAT when it mainly needs outbound access through the host, host-only when communication should remain between the host and local VMs, and a custom VMnet when the lab requires deliberate segmentation. Review addressing, DHCP, host adapters, NAT behavior, firewall rules, and exposure whenever you change a network mode.
For the related configuration overview, see Networking Configurations Overview.