Cannot connect from host on AMD ryzen to VM

[Buks]

I am running Windows 10 Pro on an AMD Ryzen laptop as my host and my quest is an CentOS 7.7 VM on Virtualbox.
I have both a NAT and Host-only network adapter. From the Linux guest I can ping the internet (google for instance), but not my host. I can also not ping the guest from the Windows host. If I use the same VM with Vmware Workstation player then I can connect. Any suggestions?

[scottgus1]

Have you enabled ping (ICMP Echo Request) in the Windows host firewall?

If so, please provide the Virtualbox's .vbox file: Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)

Also provide the output of 'ifconfig' or 'ip address' from the VM's OS while it is running under Virtualbox.

On the Windows host run these two commands and provide the output:
cd "C:\Program Files\Oracle\Virtualbox"
vboxmanage list hostonlyifs

I don't grok VMware yet, so only output running under Virtualbox is needed.

[Buks]

Ping is enabled on my Windows host.
Other requested info attached.

[scottgus1]

Your VM appears to be properly connected to the NAT and Host-Only networks. You ought to be able to ping the host's LAN IP address (should have asked you for an 'ipconfig /all' on the host too) through the NAT connection. (NAT behaves like a router and the physical host LAN connection acts like part of the internet.)

You also ought to be able to ping the host's Host-Only adapter 192.168.56.1 from both host and VM. You should be able to ping the VM's Host-Only adapter enp0s8 at 192.168.56.112 from both host and VM.

Your VM has an extra network setup that I don't recognize, the virbr0, "br" meaning 'bridge"? I don't see things like this appearing automatically in a typical Linux setup. If this is something you added manually, it may be causing the glitch.

I note that your Host-Only has DHCP turned off, so you probably set the VM's Host-Only adapter to a static IP address. For the time being, turn the Host Only DHCP back on so static IP in the VM is not necessary, just in case there's something wrong in that setup too.

I'd suggest making a new test VM with NAT and DHCP-enabled Host-Only, and a fresh automatic-as-possible OS install. Just let it install itself and then try the ping. See if you can ping the VM and the host through the Host-Only IP addresses.

[fth0]

I note that your Host-Only has DHCP turned off

This assessment (and some of your conclusions from that) could be wrong:

If you create a new Host-Only network adapter and only enable the DHCP server, by default the host uses a fixed IP address for itself, and the output of VBoxManage list hostonlyifs indicates just that DHCP is disabled for acquiring the host's IP address. Try the command for yourself to verify this.

Your VM has an extra network setup that I don't recognize, the virbr0, "br" meaning 'bridge"?

The virbr0 interface (virtual bridge 0) often is created when using QEMU/KVM/libvirt ...

[Buks]

I've created a new VM and did a clean install of CentOS 7.9. Same issue. From my Windows host I can ping 192.168.56.1, but not from my Linux guest. I am using DHCP. In my network script (ifcfg-enp0s8) I did specify BOOTPROTO=dhcp

[Buks]

I have found the problem.
I cannot connect to my Virtualbox VM when I am connected to my customer's VPN via Citrix.
When I disconnect from Citrix then I can access my VM.
Not sure if there is a way to connect to my VM whilst connected via Citrix.