Bdtyktl

Basic background tech info:

1. Host: Windows 8.1


2. Guest: Linux Mint 17


3. VMWare Player version: 6.0.3 build-1895310


4. Host hardware: ASUS Laptop with broadcomm wifi chipset

In the past (earlier versions of Linux Mint, and earlier versions of VMWare Player), I could switch networking between NAT and Bridged, and both would work as expected. I settled on NAT. Recently, I had need to switch to Bridged, and the guest Linux OS failed to connect. Switch back to NAT, and everything reconnects and works fine.

I've updated VMWare Tools in the guest OS, with no effect. Alas, I don't know which Mint upgrade, or VMWare Player upgrade broke the functionality, or when.

Variations of this question seem to crop up frequently, but none of the questions I've read here on Superuser seem to directly address, or offer a fix for, this problem.

Happy to provide logfiles or other info to help debug the issue. Just let me know what you need. Since I can use NAT as a work-around, this isn't urgent. However, I'd like to understand what's wrong and fix it.

Thanks.

There is another, not so 'brutal' approach to fixing this. This has bit me more than once. Go to the VMWare Virtual Network Editor, and in the VMNet Information section for "Bridged", pull the drop down "Bridged to:" and change from Automatic to your physical adapter name. This allows both VMWare and VirtualBox to play together on the same host. (I'm surprised that VMWare does not detect this where the host has more than 1 VM application installed)

Found a solution for my version of the problem. Hope it helps someone else.

Previously, I had been using VirtualBox. Switching over to VMWare (using NAT) worked just fine, but VirtualBox had left a host-only adapter in Windows Networking, which was (silently) making "bridged" mode in VMWare not work.

I hit a similar issue installing "boot2docker" (which uses VirtualBox) on an other machine which had VMWare working, which then stopped after installing "boot2docker". Diagnosis of that led me to VirtualBox being the culprit.

SOLUTON:

On the windows host, go to Networking Connections, and "disable" any VirtualBox network entries there. Your "Bridged" VMWare connections will start working again.

You don't have to disable the VirtualBox adapters in Windows. You can fix this within VMWare Player directly. Go into your VM Network settings, select Bridged, and then click the Configure Adapters button. Uncheck "VirtualBox Host-Only Ethernet Adapter".

This will fix your problem and leave the VirtualBox adapters functional in Windows so that you can use both VB and VMWare on the same system without having to constantly switch settings.

The only thing that fixed my connection was to add another network adapter (NAT) on top of the existing one.

Manage -> Virtual Machine Settings -> Add -> Network Adapter -> Finish.

I found that in VMware Player, there is no network editor. However, you can specify which adapter to bridge to, and that resolved the problem for me. In the screen below, both adapters were selected. De-select the Hyper-V, leaving only the physical adapter.

I would also like to mention in addition to these answers that host Firewall Particularly Firewall Clients/Software (in my case AVG Firewall) may interfere with the Bridge adapter for Vmware, try disabling the firewall software

I have a similiar problem, and it was caused by that I have 2 network card(eth/wifi) on my host and both connected to internet. When I disabled one, the problem was gone.

I was using a bridged connection for a Kubuntu VM. It suddenly stopped working, no idea why. I fixed it by entering the console command "nmcli networking on".

I have absolutely no idea why this worked.