Configure Bridged Networking for a Virtual Machine in VMware Player

Learn how to configure bridged networking in VMware Player, verify guest IP settings, support laptop roaming, and troubleshoot DHCP, Wi-Fi, DNS, and LAN access.

What bridged networking does

Bridged networking connects a guest operating system directly to a physical network adapter in the host system. The host system is the physical computer running VMware Player; the guest operating system is the operating system inside the virtual machine.

VMware normally uses VMnet0 for bridged networking. VMnet0 associates the virtual network adapter in the guest with a physical Ethernet or Wi-Fi adapter in the host. As a result, the guest appears on the same network segment as other physical devices, such as computers, phones, printers, and routers.

Bridging is different from simply sharing the host's Internet connection. The guest has its own network identity, including a distinct virtual MAC address and its own IP address. Other devices on the local network can communicate with the guest directly when network policy and firewalls allow it.

How addressing works

When the guest uses DHCP, a DHCP server—usually the local router or an organization’s network service—provides the guest with an IP address, subnet mask or prefix, default gateway, and DNS server settings. The guest commonly receives an address in the same subnet as the host and other LAN devices, but it is not assigned the host's address.

MAC address: The guest adapter's hardware-style local-network identity. It is separate from the host adapter's MAC address.
IP address: The guest's network-layer address, used by other devices to reach it.
Default gateway: The router address used to reach destinations outside the local subnet.
DNS: The service that resolves names such as internal or Internet host names to IP addresses.

You can also configure a static IP address inside the guest operating system. This does not replace selecting Bridged in VMware Player. The guest still needs bridged mode, while its address, subnet mask or prefix, gateway, and DNS settings are entered in the guest. Use an approved, unused address and follow the local network administrator's rules.

When to use bridged mode

Choose bridged networking when the virtual machine must behave like a separate computer on the local network. Typical examples include:

Hosting a development web application that another LAN computer must open using the guest's IP address.
Testing services, LAN discovery, or client-server communication.
Joining a home or office domain or accessing systems that require the guest to have its own LAN address.
Performing remote administration of the guest from another physical computer.
Testing network services from another device on the same subnet.

For example, a Linux guest using DHCP might receive an address such as 192.168.1.45, while the host has 192.168.1.20 and the router has 192.168.1.1. The three devices are separate network participants.

VMware Player network modes compared

Mode	Guest LAN visibility	IP address source	Inbound reachability from LAN	Typical use case
Bridged	Guest appears directly on the physical LAN	Usually the physical network's DHCP server, or guest-side static configuration	Usually possible, subject to firewalls and network isolation	A guest that needs its own LAN identity or must host reachable services
NAT	Guest traffic is translated through the host	VMware's private virtual network and NAT service	Not normally reachable directly from the LAN without additional forwarding	Internet access when direct LAN presence is unnecessary
Host-only	Guest is limited to the host and its private virtual network	Private virtual DHCP or guest-side static configuration	Normally limited to the host and connected host-only guests	Isolated labs and host-to-guest testing

See Configure NAT Networking for the translated-network alternative and Configure Host-Only Networking for an isolated virtual network.

Supported host connection types

Bridging can use a wired Ethernet adapter or a Wi-Fi adapter. On a desktop, Ethernet is often the simplest option. On a laptop, the active adapter may change as you disconnect a cable, join another wireless network, or move between locations.

Wireless bridging can be limited by the Wi-Fi driver, access point behavior, captive portals, enterprise authentication, endpoint-security software, or a policy that allows only one device identity behind a connection. Some managed networks restrict multiple MAC addresses or require each device to authenticate separately.

Configure bridged networking for an existing VM

Open VMware Player and select the target virtual machine in the library.
Open Player > Manage > Virtual Machine Settings.
On the Hardware tab, select Network Adapter.
Select Bridged: Connected directly to the physical network.
If this is a laptop that changes adapters or networks, consider selecting Replicate physical network connection state.
Save the change by selecting OK.
Start the guest, or restart its network connection if it was already running.
Confirm that the guest adapter is connected and enabled and that the guest receives a valid configuration.

If the VM has no network adapter, use Add a Virtual Network Adapter first. The adapter must be connected in VMware Player and enabled inside the guest operating system.

Laptop roaming and connection-state replication

Replicate physical network connection state helps a bridged guest react when the host's physical connection changes. It is useful when a laptop switches between office Ethernet and Wi-Fi or moves between networks. After the host changes connection state, the guest can reconnect or renew its DHCP configuration and obtain settings appropriate for the new network.

This option does not make unrelated networks compatible. A static address from one location may be invalid at another location, and a new Wi-Fi network may block additional devices. After roaming, verify the guest's subnet, gateway, DNS settings, and route.

Verify networking inside the guest

First check the VMware setting and the guest adapter:

Network Adapter is set to Bridged.
The adapter is marked connected in VMware Player.
The guest operating system reports the adapter as enabled.
The host has an active Ethernet or Wi-Fi connection.

Then verify the address and route in the guest. On a Windows guest, open a command prompt and run:

ipconfig /all
ipconfig /release
ipconfig /renew
ping <default-gateway>
nslookup <hostname>

Use ipconfig /all before renewing to record the current address, subnet mask, gateway, and DNS servers. Replace <default-gateway> and <hostname> with values appropriate to your network.

On a Linux guest, use:

ip addr
ip route
ping -c 4 <default-gateway>
ping -c 4 1.1.1.1
getent hosts <hostname>
resolvectl status

The guest IP address should belong to the expected physical-network subnet. Test in layers: the default gateway, another permitted LAN device, and an external IP address where allowed. Finally test DNS name resolution. A gateway that responds proves local routing, but it does not by itself prove Internet access or DNS operation.

Static IP configuration considerations

Use DHCP unless the network requires or approves manual addressing. For a static configuration, enter the settings in the guest operating system:

An unused IP address in the correct subnet.
The correct subnet mask or prefix length.
The correct default gateway.
Valid DNS server addresses.

Never guess a static address on a managed network. An address already assigned to another device can cause intermittent connectivity or make both devices unreachable. Confirm the assignment with the network administrator, and update the static settings when moving the VM to a different subnet.

Security and operational limitations

A bridged guest is exposed to the LAN similarly to a separate physical computer. Keep the guest operating system updated, enable its firewall, and expose only the services required for the lab or workload. A service that listens on all interfaces may become reachable by more LAN devices than intended.

Public, hotel, captive-portal, enterprise, and managed networks may block or limit bridged guests.
Wi-Fi client isolation may prevent other wireless devices from reaching the guest even when the guest has a valid IP address.
MAC-address restrictions or authentication controls may reject the guest as an additional device.
Host firewalls, VPN clients, endpoint-security tools, and network filters may interfere with bridging.

If direct LAN visibility is not required, NAT is often a safer and more compatible fallback. A guest that can browse through NAT but cannot obtain a bridged DHCP lease may be encountering a wireless or network-access policy rather than a guest operating-system error.

Bridged networking verification checklist

Check	Expected result	What a failure may indicate
VMware network mode	Network Adapter uses Bridged and is connected	Incorrect mode, disconnected adapter, or wrong virtual device
Guest IP address	A valid address from the expected LAN subnet	DHCP failure, static configuration error, or network policy restriction
Subnet and gateway	Subnet matches the active physical network and gateway is present	Stale settings, incorrect static values, or bridging to the wrong adapter
Gateway ping	Default gateway responds when ICMP is permitted	Local link, route, firewall, isolation, or address problem
DNS resolution	Guest resolves permitted host names	Incorrect DNS servers, DNS filtering, or a DNS-only failure
Access from another LAN device	Permitted services respond at the guest IP	Guest firewall, service binding, client isolation, or network policy

Common bridged networking problems

Symptom	Likely causes	Recommended checks or fix
No IP address	Disconnected guest adapter, inactive host link, DHCP failure, or blocked extra device	Confirm Bridged and Connected, check the host adapter, renew DHCP, and ask whether the network permits another MAC address
Guest has a self-assigned address	The guest could not obtain a DHCP lease	Renew the lease, verify the selected physical adapter, inspect DHCP availability, and test the network's device restrictions
Internet access unavailable	Wrong subnet or gateway, routing failure, firewall, VPN, or network policy	Compare host and guest settings, test the gateway, test an external IP, and inspect security software and VPN clients
Gateway reachable but names fail	DNS server or resolver configuration problem	Inspect DNS settings and use `nslookup`, `getent hosts`, or `resolvectl status`
Works on Ethernet but not Wi-Fi	Wrong adapter selected, driver limitation, Wi-Fi isolation, captive portal, or enterprise restriction	Select the active wireless adapter, check driver and VMware bridge binding, authenticate the guest if required, or use NAT
Fails after moving to another network	Stale DHCP lease, wrong adapter, or static settings from the previous subnet	Enable connection-state replication, reconnect or renew the guest adapter, and replace invalid static settings

Structured troubleshooting

The guest receives no address

Confirm that the VM Network Adapter is set to Bridged and connected.
Confirm that the host has an active Ethernet or Wi-Fi connection.
Renew the guest DHCP lease or disconnect and reconnect the guest adapter.
Check whether VMware is bridging to the active physical adapter rather than a disconnected, virtual, VPN, or otherwise incorrect adapter.
Check whether the network blocks extra MAC addresses or unauthenticated devices.

The guest has an address but cannot reach outside networks

Compare the guest subnet and gateway with the host's current physical-network configuration. Ping the guest's default gateway first, then test an external IP address such as 1.1.1.1 where the network permits it. If the gateway fails, investigate local addressing, adapter selection, firewall, VPN, and Wi-Fi isolation. If the gateway works but the external test fails, investigate routing or network policy.

IP access works but host names fail

Inspect the guest's DNS server settings. Test with nslookup on Windows or getent hosts and resolvectl status on Linux. Correct DHCP or static DNS values, and check whether a VPN or security product is changing DNS behavior.

Other LAN devices cannot reach a guest service

Confirm that the guest has a valid bridged address.
Verify that the service is listening on the intended guest interface and port, not only on loopback.
Allow the service through the guest firewall.
Check the client firewall, Wi-Fi client isolation, and other network access controls.

For a broader overview of virtual network components, see Virtual Networking Components. To compare other VMware network arrangements, see Networking Configurations.

Practical configuration examples

Development server reachable from the LAN

Select Bridged for the VM's Network Adapter, let DHCP assign the guest an address, and configure the development server to listen on the guest's LAN interface. From another computer, connect to the guest IP address. The guest firewall must permit the application port.

Lab machine joining a home or office subnet

Use DHCP in the guest and verify that its address, gateway, and DNS settings match the physical subnet. This allows the guest to communicate with permitted LAN services as its own device.

Laptop moving between office Ethernet and Wi-Fi

Enable Replicate physical network connection state. After switching connections, reconnect or renew the guest adapter and confirm that it received an address for the new network.

Approved manual addressing

Configure the approved unused address, subnet mask or prefix, gateway, and DNS values inside the guest. Verify that the address does not conflict with DHCP leases or another static device.

Restricted Wi-Fi fallback

If bridged mode cannot obtain a lease but NAT provides browsing, the Wi-Fi network may reject the guest's separate identity. Use NAT when other LAN devices do not need to initiate connections to the guest.