3

I have a windows 10 Host machine running Virtual Box 5.2.22 the IpAdress is 192.168.1.24 mask 255.255.255.0 (class c). I have a guest OS windows 10 with IP 192.168.1.252 mask 255.255.255.0 (class c). The adapter is bridged to the wired ethernet NIC. I can not ping Host to Guest or Vice Versa.

If I set it up to NAT - I can ping host < > Guest. This does not work in my situation because I need it to pass Ethernet/IP (Ethernet/ Industrial Protocol) traffic and using NAT does not seem to allow this; as all my software that uses this protocol can not find the devices on the network and use the proprietary commands associated for device identification.

I would like to be able to set up a working bridged connection - where I can access everything just like it was the host machine.

Windows Firewall is off in the guest. In the host private network firewall is off, Inbound rules are set to allow pings.

So what do I need to do in order to accomplish two way communication and the guest to be able to bridge with the host?

Improve this question

2 Answers 2

Reset to default
1

In Virtual Box Machine Settings:

Set the WIFI as the first adapter [MTDesktop, AllowALL] Set the LAN WIRED [MTServer,AllowAll] as the second adapter.

In the Guest machine disable the First Adapter (which is bound to the wifi) in Adapter Settings.

Set your IP Address on the Guests Second Adapter. You can then ping internal, external whatever - using my guests second adapter.

One other issue can cause this: If you Locally Administer the MAC address in the Guest Image rather than via the VirtualBox settings you will also have the same issue of not being able to communicate with host (vice versa) or outside devices.

Virtual Box 5.2.22 other versions are probably affected.

Improve this answer
0

My solution is specific to wired network. If you have two computers on a subnet and each have static ip and if you are trying to ping virtual machine ip on the first computer from the second computer on same network.

From the Virtual Box go to Settings -> Network

Then choose Bridged Adapter from Attached To dropdown menu. Make sure to choose appropriate network hw adapter for Name.

The IPs for network hw adapter, the guest machine should lie on the same subnet. Now you should be able to ping HOST to Guest and vice versa, also from any external machine on same subnet.

Note: For this you may have to edit the adapter settings in the host and in the virtual machine edit Wired Connected settings.

Improve this answer
3
  • In my original question you will see they are both on the same network. You will see that the adapter is bridged to the wired network.
    – StixO
    Jun 16, 2021 at 15:13
  • Hi StixO, yes I agree..I just wanted to share my experience, just having a wired connection and adapter set to Bridged mode, it is perfectly possible to route all traffic between HOST and guest.
    – Kartik Javali
    Jun 17, 2021 at 9:56
  • Had similar issues - replacing the network card with a different one solved it, but have found it to be an intermittant problem with windows hosting VM's needing isolated LAN access in general, so no clear solution: It's quite possible that just installing a new adaptor replaced something that had bit-rotted to death, and the problem will just eventually recur. It does seem to be something broken specifically in windows IP: can get a situation where non-IP ethernet protocols work, but not IP. Usuallly this is some equipment software meant to set up hardware when IPs are misconfigured.
    – RGD2
    Jul 7, 2022 at 23:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.