Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Host unable to communicate with guest machines and vice versa

  • Please log in to reply
1 reply to this topic

#1 johnnyseq


  • Members
  • 1 posts
  • Local time:03:17 PM

Posted 12 November 2018 - 03:27 PM


I have VMware Workstation 15, and I have Windows 10 pro installed on the host computer.

For some strange reason the host computer is unable to communicate with any of the guest machines and vice versa, nor matter what OS they have loaded.

So, here what I have setup:


On the Virtual Network Editor of Workstation I have setup a VMnet0 to be bridged to the host's physical network interface.

My router has the network of, and my virtual machines have ips within that same subnet.....(eg: one of them have Windows 2012 R2 and its ip is

So, within the "Settings" of all these virtual machines I have selected the "Custom" option for the network and then selected VMnet0 for all of them, so they can point to the host's network.


On all these VMs I am able to ping the gateway, have internet, and I can also ping all the rest of the VMs without any problem, but strangely I cannot ping the host nor any other asset that is not "virtual". Also, if I try to ping from the host another physical computer within the same network I am NOT able to ping it either and vice versa. On the host OS I have disabled the firewall, antivirus.

Also on the Windows 2012R2 VM I have permanently disabled the firewall as I need it that way.


Have anyone faced this kind of thing? How could I resolve this problem and what is keeping me from being able to communicate back and forth, from host and VMs?

If you need anymore information please let me know.


Thank you

BC AdBot (Login to Remove)


#2 sflatechguy


  • BC Advisor
  • 2,266 posts
  • Gender:Male
  • Local time:04:17 PM

Posted 18 November 2018 - 08:21 AM

The "bridge" is simply using the interface for communication on the subnet. You need to configure the bridge to NAT or route to the subnet the host machine is on, or use a host-only network for the VMs.


Even though the bridge is on the host, that doesn't mean the host machine can communicate with VMs on that subnet. You need something to route the traffic between the host machine and the bridge.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users