Virtualbox problem internal network setup

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Sanderif
Posts: 6
Joined: 2. Dec 2020, 14:44

Virtualbox problem internal network setup

Post by Sanderif »

Hi everybody,

I've followed a tutorial to setup an internal network between two VMs to use it for a school project. I've created the two VMs and placed them on the same LAN. I turned them both on and when I ping from VM1 to VM2 and vice versa it gives me "Host destination unreachable".

I have some networking experience but i'm not an expert. Can you guys fix my problem? It would be much appreciated!

Some specific details about the host system/software:
- Windows 10 Home
- VirtualBox Version 6.1.22 r144080
- Disabled the Windows Virtual Machine Platform feature on my host (gave me a guru meditation error when i start up the VM)
- Disabled,the Windows Hypervisor Platform feature on my host (gave me a guru meditation error when i start up the VM)

Some specific details about the VMs:
- Both VMs are newly made in the latest version of VirtualBox
- Both VMs have exactly one Internal Network adapter with promiscuous mode on allow all

VM1
- Windows Server 2019
- ipconfig /all
Windows IP Configuration

Host Name . . . . . . . . . . . . : WIN-KF3FA2KUJUU
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . . . . : 08-00-27-D1-39-FF
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.19(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

VM2
- Windows 10 Pro
- ipconfig /all
Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-VBBNCSB
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . . . . : 08-00-27-32-AE-49
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

What have I tried?
- Enabled FIle and Printer Sharing (Echo Request - ICMP - In) for private/public/domain on both machines
- Enabled Network discovery on both machines
- Opened CMD in Administrator mode
- Turned off the Firewalls entirely
- Changed both IPs to another range
- Checked the MAC addresses of the adapters (they are different)

Kind regards,
Stephen
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Virtualbox problem internal network setup

Post by scottgus1 »

This was the first thig I was going to suggest to look at:
Sanderif wrote:Enabled FIle and Printer Sharing (Echo Request - ICMP - In) for private/public/domain on both machines
Windows firewall defaults to block ping, and both VMs are Windows. Confirm that ping is enabled, per a web-search how to do it.
Sanderif wrote:placed them on the same LAN.
See Virtualbox Networks: In Pictures: Internal Network. To have them both in the same LAN they both need to be connected to the same Internal network name.

If neither of these helps, please right-click each VM in the main Virtualbox window's VM list, choose "Show in Explorer/Finder/File Manager". In the window that opens, zip the VM's .vbox file, and post the zip file, using the forum's Upload Attachment tab. (Please make sure all file extensions are shown, so you will be able to see the .vbox extension easier.)
Sanderif
Posts: 6
Joined: 2. Dec 2020, 14:44

Re: Virtualbox problem internal network setup

Post by Sanderif »

scottgus1 wrote:the same Internal network name.
Well that was a stupid mistake from me :lol:

I've had two different Internal Network names setup on both Internal Network adapters therefore not being able to ping to each other because the VMs were not on the same LAN.

Thanks for the super fast reply! I Appreciatie it!
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Virtualbox problem internal network setup

Post by scottgus1 »

Hey don't be embarrased, I've been there done that. I have told my boss for certain that the thing he wanted me to go get is absolutely not there and he goes and lays his hand on it and it was right in front of me. :oops: Best place to hide something from me is right in front of my face, purloined-letter-style. :lol:

Glad you're up and running!
Post Reply