How to Set Up Bridged Networking in VMware Workstation Player

Configure bridged networking in VMware Workstation Player so a Linux or Windows guest receives its own address on the same physical LAN as the host.

Bridged networking connects a virtual machine to an external physical network through one of the host computer's network adapters. The host operating system is the operating system running VMware Workstation Player. The guest operating system is the operating system installed inside the virtual machine.

In bridged mode, the guest behaves like a separate computer on the local-area network (LAN). It normally receives its own IP address from the LAN's DHCP service, rather than sharing the host's address. This makes bridged mode useful when another computer on the LAN must initiate a connection to the guest.

When to Choose Bridged Networking

Use bridged networking when the guest should participate directly in the same network as the host. Typical examples include a Linux server that must accept SSH connections from another home-lab computer, or a Windows guest that must be tested from another device using Remote Desktop.

Bridged mode is generally preferable to NAT when inbound connections from other LAN devices must reach the guest. NAT is often simpler when the guest only needs outbound internet access. Host-only networking is appropriate for an isolated lab between the host and virtual machines. Disconnected networking disables the virtual adapter's network connectivity.

VMware Workstation Player Network Modes Compared

Mode	Guest gets separate LAN IP	Internet access	Reachable from other LAN devices	Typical use case
Bridged	Usually yes	Yes, through the selected physical adapter	Usually yes, subject to firewalls and LAN policy	Guest must appear as a separate computer on the LAN
NAT	No direct LAN address; the guest uses a private virtual network	Usually yes, through the host	Usually no without additional configuration	General guest internet access with less LAN exposure
Host-only	No address on the physical LAN	Normally no	No; communication is limited to the host and participating virtual machines	Private testing and isolated labs
Disconnected	No usable network connection	No	No	Testing software while completely offline

Prerequisites

Make sure the host has an active Ethernet or Wi-Fi connection.
Power off the VM before changing its hardware settings, unless you know that changing the adapter state while running is safe.
Identify the host's active physical network adapter. This may be an Ethernet adapter, a particular Wi-Fi adapter, or an adapter in a docking station.
Confirm that the physical network permits an additional device. Some corporate, campus, guest, and managed networks restrict virtual machines or multiple devices.
Confirm that DHCP is available if the guest is expected to receive its address automatically.
Know the host and guest operating systems well enough to open network settings and inspect an interface.

Configure Bridged Mode in VMware Workstation Player

Open VMware Workstation Player and select the virtual machine.
Open the VM's settings, commonly through Virtual Machine Settings.
Select the virtual Network Adapter hardware device.
Select Bridged as the network connection type.
Enable Connect at power on. Also confirm that the adapter is currently connected when the VM is running.
If physical-adapter selection is available, choose the active host Ethernet or Wi-Fi adapter. Otherwise, leave automatic selection enabled and verify the result after booting.
Save the settings, then start or restart the guest operating system.

The virtual network adapter is the VM hardware device that provides network connectivity to the guest. Bridged mode associates that virtual device with a physical adapter on the host. The host and guest still have separate network interfaces and normally receive different IP addresses.

Configure the Guest's IP Address

DHCP addressing

DHCP is a network service that automatically supplies an IP address, subnet information, a default gateway, and often DNS servers. In most home networks, leaving the guest's IPv4 configuration set to DHCP is the simplest choice.

After the guest starts, inspect its interface and confirm that its address belongs to the same LAN as the host. For example, a host at 192.168.1.20 and a guest at 192.168.1.50 may be on the same subnet. The exact addresses depend on the router and network configuration.

Static addressing

A static IP address is a manually assigned, fixed address. It can be useful for a lab server whose address must not change. Before assigning one, choose an unused address that complies with the network's policy. Prefer a DHCP reservation or an address outside the DHCP pool when the router or administrator recommends it.

A static IPv4 configuration requires:

An unused IP address.
A subnet mask or CIDR prefix, which defines which addresses are local. For example, 255.255.255.0 is commonly written as /24.
A default gateway, usually the router address used to reach networks outside the local subnet.
One or more DNS servers. DNS resolves names such as example.com to IP addresses.

Never reuse an address already assigned to another device. An address conflict can cause intermittent connectivity for both systems.

Verify the Connection

Test in layers. First identify the guest address, then test the gateway, a public IP address, name resolution, and finally access from other devices.

Windows guest

ipconfig /all
ping <default-gateway>
ping 8.8.8.8
nslookup example.com

ipconfig /all shows the adapter address, subnet mask, gateway, DHCP state, and DNS servers. A successful gateway test confirms local connectivity. A successful test to 8.8.8.8 tests routed internet access without relying on DNS. nslookup tests name resolution.

Linux guest

ip addr
ip route
ping -c 4 <default-gateway>
ping -c 4 8.8.8.8
getent hosts example.com

ip addr displays interface addresses, while ip route shows the default route. The remaining commands test the gateway, internet routing, and DNS resolution.

Test access to the guest

From the host, ping or connect to the guest's IP address.
From a second device on the same LAN, test the guest when LAN access is required.
Test the actual service, such as SSH, RDP, or a web server.

Network reachability alone does not make a service accessible. The service must be running, listening on the guest's network address rather than only on loopback, and allowed through the guest firewall. For example, enable the SSH service and its firewall rule before testing SSH to a Linux guest.

Bridged Networking Setup Checklist

Check	Expected result	Where to verify	If not correct
Host connection	Ethernet or Wi-Fi is active	Host network settings	Connect to the network and identify the active adapter
VM adapter mode	Bridged is selected	VM settings, Network Adapter	Change the connection type to Bridged
Adapter connection	Connected and set to connect at power on	VM settings and running VM status	Enable both connection options and reconnect the adapter
Bridge target	Correct active physical adapter is selected	Bridged adapter selection	Choose the active Ethernet or Wi-Fi adapter
Guest address	LAN address obtained by DHCP or correctly assigned statically	`ipconfig /all` or `ip addr`	Renew DHCP or correct the static settings
Connectivity	Gateway, public IP, and DNS tests succeed	Guest terminal or command prompt	Test each layer and inspect routes, DNS, and firewalls
Service access	Required port is listening and permitted	Guest service and firewall settings	Start the service, bind it to the LAN interface, and allow its port

Wireless Bridging Considerations

Wi-Fi bridging can depend on the wireless adapter driver, VMware's support for that adapter, the access point's policy, and the hardware's capabilities. Ethernet is often more predictable because wired networks commonly handle additional bridged MAC addresses more consistently.

When several adapters exist, select the active Wi-Fi adapter rather than a disconnected adapter, VPN interface, virtual adapter, or old dock connection. If a laptop changes between docked Ethernet and Wi-Fi, automatic selection may work, but always recheck the guest's IP address after the host changes networks.

Some wireless networks enable client isolation, which prevents wireless clients from communicating with one another. Others restrict multiple MAC addresses or unmanaged devices. In either case, the guest may have internet access while remaining unreachable from another LAN device.

Common Failure Scenarios

The guest has no IP address or receives 169.254.x.x

An address in the 169.254.x.x range is typically self-assigned after DHCP failed. Check that the VM adapter is connected, that Connect at power on is enabled, and that the guest interface and driver are available. Verify that bridging uses the host's active physical adapter, then renew the guest's DHCP lease. If the problem continues, check whether the LAN permits the guest and whether its DHCP service is available.

The guest can access the internet but not local devices

Compare the guest's address, prefix or subnet mask, and gateway with those of the target device. Test the gateway separately from the target. Client isolation, guest firewalls, different VLANs, or different subnets can block local traffic even when internet routing works.

The guest has no internet access

Test the gateway first. If the gateway fails, inspect the bridge target, guest address, subnet, and adapter connection. If the gateway works but 8.8.8.8 fails, inspect the default route and LAN policy. If the public IP test works but the DNS test fails, correct the guest's DNS configuration.

Other devices cannot connect to a guest service

Confirm the current guest IP address and verify that the service is running and listening on the LAN interface. A service bound only to 127.0.0.1 or ::1 accepts local connections but not LAN connections. Permit the required port in the guest firewall, then test from the host and from a second LAN device.

The wrong host adapter is being bridged

Bridging can select a VPN adapter, disconnected Wi-Fi adapter, virtual adapter, or inactive docking-station adapter. Inspect host adapters with the applicable command, select the active physical adapter in the VM settings, and obtain a fresh guest address.

Windows host:
ipconfig /all
Get-NetAdapter

Linux host:
ip addr
nmcli device status

Use only the commands applicable to the host operating system. These commands inspect the host, not the guest. On Windows, ipconfig /release and ipconfig /renew can refresh the host's DHCP lease when appropriate, but they do not replace correcting the VM's bridge selection.

Bridging stops after a network change

Switching between Wi-Fi, Ethernet, a docking station, or a VPN can change which adapter is active. Security software may also change network bindings. Reidentify the active physical adapter, update the bridged selection, reconnect the guest adapter, and renew its lease. Disconnect conflicting VPN or security software only when permitted by the system owner or organization.

The guest interface is disabled or missing

Check the guest's network settings for a disabled interface. If the interface is absent, install or repair the guest network driver or the VM integration components appropriate for that guest. Then reconnect the virtual adapter and restart the guest network service if necessary.

Security and Network Policy

Treat a bridged guest like another physical computer on the LAN.
Apply guest operating-system updates before exposing services.
Enable an appropriate guest firewall and allow only required ports.
Use strong credentials and secure protocols such as SSH rather than unprotected remote services.
Respect organization, campus, and managed-network rules about unmanaged devices, virtual machines, extra MAC addresses, and server services.

Exam-Relevant Notes

Bridged networking places the guest on the physical LAN as a separate participant, normally with its own IP address.
NAT shares the host's external connection and usually prevents direct inbound LAN connections to the guest.
Host-only networking is limited to the host and participating virtual machines; disconnected networking provides no network access.
Successful internet access does not prove that another LAN device can reach the guest. Firewalls, service listeners, VLANs, client isolation, and network policy still matter.
When DHCP fails, inspect the virtual adapter state, selected physical adapter, guest interface, and LAN permissions before assigning a static address.