Ping works only one-way to host in VM virtualbox



Show first post

32 replies

Userlevel 7
I should also ask if the Windows firewall is causing your woes. Have you checked to make sure it is either off or is allowing ICMP/Ping?
Userlevel 1
I should also ask if the Windows firewall is causing your woes. Have you checked to make sure it is either off or is allowing ICMP/Ping?
I have exclusively added a rule to accept ICMP-requests to both directions. I also tried to ping without firewall.
Userlevel 1
I should also ask if the Windows firewall is causing your woes. Have you checked to make sure it is either off or is allowing ICMP/Ping?
And I was talking about host machine's firewall, I now realized you were talking about windows firewall inside VM. You were totally right!

Damn I feel stupid.
Userlevel 7
I should also ask if the Windows firewall is causing your woes. Have you checked to make sure it is either off or is allowing ICMP/Ping?
Don't feel stupid, I'm just glad it works now :)
In our labs, we use a lot of virtualization for customer issue replications and I see it often.
Userlevel 1
OKAY I must've have a typo somewhere, because now the hosts can actually reach each other when I use switches as hosts.

But some reason windows-hosts cannot. There must be problem with the windows then!
Userlevel 1
OKAY I must've have a typo somewhere, because now the hosts can actually reach each other when I use switches as hosts.

But some reason windows-hosts cannot. There must be problem with the windows then!
It was windows firewall in the VM! Now everything works!
Userlevel 6
Petteri,

Since you are doing complex labs, you may be interested in using all 8 adapters available in the EXOS VM.

Only the first 4 adapters can be managed throgh the GUI. The remaining 4 adapters (corresponding to ports 4 to 7 in the switch) must be configured using vboxmanage.

Here's the list of commands needed to enable and configure these adapters:
  • vboxmanage modifyvm --nicX bridged | intnet (to definer adapter X as Bridged or Internal Network)
  • vboxmanage modifyvm --intnetX (to define the name of the internal network connected to adapter 😵
  • vboxmanage modifyvm --nictypeX Am79C973 (to define the adapter’s nic type as PCnet-FAST III)
  • vboxmanage modifyvm --nicpromiscX allow-all (to configure adapter X promiscuous mode)
  • vboxmanage modifyvm --cableconnectedX on |off (to configure adapter X cable connected status)
  • vboxmanage modifyvm --macaddressX (to configure adapter X MAC address)
So, if you want to configure Adapter 5 of a VM named sw1 so that it connects to link15 the commands would be:
vboxmanage modifyvm sw1 --nic5 intnet
vboxmanage modifyvm sw1 --intnet5 link15
vboxmanage modifyvm sw1 --nictype5 Am79C973
vboxmanage modifyvm sw1 --nicpromisc5 allow-all
vboxmanage modifyvm sw1 --cableconnected5 on
vboxmanage modifyvm sw1 --macaddress5 00:11:22:33:44:55:66

Additional adapters configured through the CLI will appear in the GUI, but you will not be able to configure them or view detailed information.



To get detailed information about these adapters you'll need to use

vboxmanage showvminfo

Vboxmanage is very useful if you plan to write scripts to automate tasks...

Reply