VMware ESXi and vSphere Cluster Management

Configure Bridged Networking for a Virtual Machine in VMware Player

Learn how to switch an existing VMware Player virtual machine to bridged networking, configure guest addressing, verify LAN access, and troubleshoot common connection problems.

What bridged networking does

Bridged networking places a virtual machine on the physical network through a network adapter in the host system. The host system is the physical computer running VMware Player. The guest operating system is the operating system installed inside the VM.

VMware commonly represents the default bridged virtual network as VMnet0. VMnet0 connects the VM's virtual network adapter to a physical Ethernet or Wi-Fi adapter available on the host. The guest therefore operates as an independently addressable device on the same LAN as the host, when the physical network permits this.

A bridged guest has its own virtual network adapter and its own MAC address, which is the link-layer identifier used by that adapter. The physical network normally sees the guest as an additional client. DHCP, the service that automatically supplies network settings, can assign the guest its own IP address, subnet mask or prefix, default gateway, and DNS servers.

For example, a host might have address 192.168.1.20 while a bridged guest receives 192.168.1.45. Both can use the same subnet and gateway, but they remain separate network devices. Other LAN clients may be able to contact the guest directly if the guest firewall, service configuration, wireless policy, and other network controls allow it.

Bridged, NAT, and host-only networking

NAT networking translates guest traffic through the host. It is useful when the guest needs outbound Internet access but should not appear as a directly reachable peer on the physical LAN. Host-only networking creates an isolated network generally limited to the host and its VMs. It is useful for private labs.

Mode	Guest visibility on physical LAN	Typical IP source	Inbound access from other LAN devices	Best use case
Bridged	Guest appears as a separate device on the physical LAN	Physical network DHCP or guest static configuration	Usually possible when routing, firewalls, and LAN policies allow it	Guest must act like another physical computer
NAT	Guest is hidden behind the host's network identity from the LAN	VMware's virtual DHCP service	Not normally available without port forwarding or similar configuration	Outbound Internet access with reduced LAN exposure
Host-only	Guest is not normally connected to the physical LAN	Host-only virtual DHCP or static configuration	Usually limited to the host-only network	Isolated host-to-guest testing

How a bridged guest participates in the LAN

The communication path is: guest operating system, guest virtual network adapter, VMnet0, host physical network adapter, and then the Ethernet or Wi-Fi network. VMware presents the virtual adapter to the guest as network hardware, while the host supplies the connection to the physical network.

With DHCP, the guest normally receives:

An IP address unique to the guest.
A subnet mask or CIDR prefix that identifies the local subnet.
A default gateway for destinations outside the local subnet.
One or more DNS server addresses for translating names into IP addresses.

The guest can communicate with other LAN devices, and those devices can initiate connections to services in the guest when network policies allow it. A web server, SSH server, or file share in the guest can therefore be tested from another computer on the same LAN.

Wired and wireless connections

Bridging can use a wired Ethernet adapter or a Wi-Fi adapter on the host. Behavior on Wi-Fi depends on the adapter, driver, VMware installation, wireless access point, and network policy. Some corporate or public networks restrict multiple client identities behind one wireless connection or block peer-to-peer traffic. VPN and virtual adapters can also confuse automatic bridge selection.

When to choose bridged networking

Choose bridged mode when the VM should behave like another physical computer on the LAN.
Choose it when another system must initiate connections to a guest web server, SSH server, file share, or test application.
Choose NAT when the guest only needs outbound Internet access and should not be directly exposed to LAN clients.
Choose host-only networking for an isolated lab involving the host and one or more VMs.

A bridged guest is especially useful for testing software from a phone, workstation, or another physical computer. For example, a Linux guest can receive an address from a home router, run SSH, and accept a connection from another computer on the same Wi-Fi network.

Configure an existing VM in VMware Player

Open VMware Player and select the target virtual machine in the library.
Open the VM management menu and choose the virtual machine's settings. In many versions this is labeled Player > Manage > Virtual Machine Settings.
In the Hardware section, select Network Adapter.
Make sure the adapter is enabled and connected. If the VM is powered off, enable the option to connect the adapter when the VM powers on if that option is shown.
Under the network connection type, select Bridged. The interface may identify this as bridging to VMnet0.
Enable Replicate physical network connection state when the host is a laptop or frequently changes between Ethernet, Wi-Fi, or different networks.
Save the setting with OK or the equivalent confirmation button.
Start the VM, or restart its networking if it was already running.

The exact labels can vary between VMware Player releases, but the relevant path is the VM's hardware settings followed by Network Adapter and Bridged networking. If the VM has more than one adapter, change the adapter intended for LAN access and avoid accidentally altering a separate host-only or NAT adapter.

Replicate the physical connection state

The physical connection state option tells VMware to reflect changes in the host's physical link state in the guest's virtual adapter. This is useful when a portable host moves from office Ethernet to Wi-Fi, changes access points, or disconnects from one network and joins another.

When the host link changes, this setting can help the guest notice that its network has changed and request valid settings from the new network's DHCP service. Without it, the guest may retain an old address, route, or disconnected state.

Replication is not a guarantee of uninterrupted connectivity. After roaming, the guest may still need a manual adapter reconnect, DHCP renewal, NetworkManager restart, or guest restart. The new network may also prohibit additional bridged devices.

Configure the guest's IP address

Use DHCP by default

DHCP is normally the simplest and safest choice. Once the bridged adapter is connected, the guest requests an address from the physical LAN's DHCP service. This avoids manually entering values that belong to a different network.

After changing networks, renew the lease so the guest does not continue using settings from the previous subnet.

Use a static address only when appropriate

A static IP address is entered manually instead of being assigned by DHCP. Use one only when the network supports manual addressing or has a planned reservation and you know the active subnet's addressing rules.

A static configuration requires:

A unique IP address valid for the active LAN subnet.
The correct subnet mask or CIDR prefix length.
The correct default gateway.
Appropriate DNS server addresses.

Do not select an address already used by another device. Do not choose an address outside the permitted subnet or DHCP and reservation plan unless the network administrator has allocated it. A static address that worked on one Wi-Fi or Ethernet network may be invalid on another.

Verify the configuration inside the guest

First confirm that the guest's network adapter is enabled and connected. Then inspect its address, route, gateway, and DNS settings. The guest address should normally be in the same network range as other LAN clients, although routed networks can produce a different valid range.

Windows guest

ipconfig /all

Check the adapter's IPv4 address, subnet mask, default gateway, DHCP status, and DNS servers. If DHCP is expected but the values are missing or incorrect, renew the lease:

ipconfig /release
ipconfig /renew

Test the gateway and DNS separately:

ping <default-gateway>
nslookup <hostname>

Linux guest

ip addr
ip route
nmcli device status

Use these commands to check the interface state, assigned addresses, routes, and NetworkManager device status. Test the gateway, an Internet IP address, and name resolution independently:

ping -c 4 <default-gateway>
ping -c 4 1.1.1.1
getent hosts <hostname>

Validation checklist

Test each layer separately rather than treating “the Internet” as one test:

Confirm the guest has a valid address and the adapter is connected.
Ping the default gateway. Failure here usually indicates an adapter, subnet, VLAN, Wi-Fi isolation, or local firewall problem.
Test an external IP address such as 1.1.1.1. If the gateway works but this fails, inspect the route, gateway policy, and LAN Internet access.
Resolve a hostname with nslookup or getent hosts. If IP access works but name resolution fails, inspect DNS settings.
Test guest-to-LAN-device connectivity using a known device and service.
If inbound access is required, connect from a different LAN device, not only from the host. Confirm the service listens on the guest's LAN address rather than only on loopback, and allow its port through the guest firewall.

Item	Expected state	Where to verify
VM network adapter enabled	Adapter is enabled and connected	VMware Player hardware settings and guest network status
Bridged mode selected	Network connection type is Bridged, commonly using VMnet0	Network Adapter settings
Correct host adapter available	Intended Ethernet or Wi-Fi interface has physical network access	Host network settings and VMware bridge mapping
Physical connection state replication for mobile hosts	Option enabled when the host changes networks	Network Adapter settings
Guest IP configuration	Valid DHCP lease or planned, unique static values	Windows `ipconfig /all` or Linux `ip addr`
Gateway and DNS reachability	Gateway responds and hostnames resolve	`ping`, `nslookup`, or `getent hosts`

Troubleshoot common bridged networking problems

Symptom	Likely cause	Verification	Corrective action
Guest has no IP address or an automatic private address	Disconnected adapter, unavailable host link, unsuitable bridge, DHCP restriction, or exhausted DHCP scope	Check VMware adapter state, host connectivity, guest address, and DHCP availability	Enable and connect the adapter, renew DHCP, select the intended physical adapter, and check network restrictions
Guest reaches the gateway but not names	Missing or unusable DNS settings, or VPN/security software interference	Ping a known IP and run a hostname lookup separately	Inspect DNS settings, renew DHCP, correct DNS, and review VPN policies
Guest browses the Internet but is unreachable from the LAN	Guest firewall, service bound only to loopback, wireless isolation, or LAN inbound policy	Test from another LAN device and inspect the service listening address	Bind the service to the guest LAN interface, allow its port, and review LAN isolation rules
Networking fails after switching Wi-Fi networks	Old address or route, disabled link-state replication, or restrictions on the new network	Inspect the current address and route after roaming	Enable replication, reconnect the VM adapter, renew DHCP, restart guest networking, and confirm the new network permits bridged clients
Bridging selects the wrong host interface	Multiple Ethernet, Wi-Fi, VPN, docking, or virtual adapters	Compare the selected bridge with the host interface that reaches the desired LAN	Choose the intended physical interface in VMware's bridge controls, avoid VPN adapters, or temporarily disable unused adapters

No guest address

Confirm that the VM adapter is enabled, connected, and saved as Bridged. Confirm that the host itself can access the intended network. Renew the guest's DHCP lease. If that fails, inspect whether the physical network limits the number of clients, blocks unknown MAC addresses, requires authentication, or has no available DHCP addresses.

Address exists but Internet access fails

Compare the guest's address, prefix or subnet mask, and gateway with a known working client on the same LAN. Test the gateway before testing an external IP. Temporarily using DHCP can help distinguish a bad static configuration from a VMware or physical-network problem. Also inspect the guest route table and firewall.

IP connectivity works but DNS fails

If a ping to a known IP works but a hostname lookup fails, the problem is probably DNS rather than bridging. Inspect the configured DNS servers, renew DHCP, and check whether a VPN or endpoint-security product changed name-resolution behavior.

Other LAN devices cannot reach a guest service

Verify that the service listens on the guest's LAN interface. A service listening only on 127.0.0.1 or ::1 accepts local connections but not LAN connections. Then allow the required port in the guest firewall. Test from a second device on the same subnet and check wireless client isolation or corporate network rules.

Wrong adapter selected

Hosts often contain several interfaces: Ethernet, Wi-Fi, VPN adapters, virtual adapters, and docking-station interfaces. Automatic bridge selection may choose an interface that has no route to the desired LAN. Identify the active physical interface, select it through the VMware bridge controls where available, and avoid bridging through a VPN or unrelated virtual adapter.

Practical examples

Home LAN: A Linux guest uses Bridged mode and receives its own address from the home router. Another computer on the same Wi-Fi network connects to the guest's SSH service.
Local web application: A developer runs a web server in a VM and uses the guest's LAN address so a phone or separate workstation can open the application directly.
Laptop transition: A laptop moves from office Ethernet to Wi-Fi. Physical connection state replication helps the guest detect the transition and request settings for the new network.
Fixed lab server: A lab requires a stable server address. The guest receives an unused address with the correct prefix, gateway, and DNS servers for the active subnet.

Summary

To put an existing VMware Player VM on the physical LAN, open its settings, select Hardware > Network Adapter, choose Bridged, and save the change. Enable physical connection state replication for hosts that move between networks. Use DHCP unless the network provides a planned static-address configuration. Finally, verify the guest address, gateway, DNS, outbound connectivity, and inbound access from a separate LAN device. For comparison, see this bridged networking configuration guide.