Virtualbox - Internal network configuration problem

[Lanstack]

Hello,

I don't know if I'm posting in the right place but it's about the network...

I installed VirtualBox and created 2 virtual machines with internal network
I put the same internal network name as each VM

Impossible to ping the VMs between them, I admit that I do not understand my mistake. Do you have an idea of ​​the problem?

If I'm on VM1 and I want to ping VM2
Response from 192.168.20.1: Unable to reach destination host

If I'm on VM2 and I want to ping VM1
Response from 192.168.20.2: Unable to reach destination host

my 2 VMs are Windows Server 2022 Version Core
I disabled the firewall of each VM with this command :

Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False

[scottgus1]

Internal is only a virtualized piece of Ethernet cable, with possibly an unmanaged network switch added in. See Virtualbox Networks: In Pictures: Internal Network. There is no DHCP server on the network, though one can be added if desired.

So if your VMs are on the same Internal network, then you'd configure the network settings in the OS's same as if you took two PCs and connected them with an Ethernet cable.

Check that the VMs' network "cables" are connected, and that the Internal network's name is identical in each VM. Also check that the virtual network card inside each VM is being recognized and usable by the OS. Then the rest would be config issues in the OS's inside the VMs.

Server 2022 Version Core

You might want to try this with a GUI OS first, to get the configuration correct.

I disabled the firewall of each VM

I can't speak regarding the command you used, whether it does what it's hoped it would do. But enabling ICMP Echo Request allows Windows to respond to Ping while the firewall is running.

[Lanstack]

On each VM, I configured a fixed IP address.

The virtual network card: Intel PRO/1000 MT Desktop (82540OEM) is recognized by my Windows Server 2022 Core version VMs

I disabled windows firewall on each VM

[Lanstack]

I tried the same configuration with VMWorkstation. I have no problem.
So VirtualBox is the problem.

[BillG]

Then stay with VMWare.