Windows PC and VirtualBox cannot ping each other.

[Eeyore]

I have a Windows 11 PC, and have stood up a VirtualBox environment running Windows 10 on the same PC. The objective is to use the VirtualBox environment as a sandbox to develop a better understanding of certain software programs and how they communicate with a host installed on the PC.

My PC has an address of 10.0.0.165.
The VirtualBox environment has an address of 10.0.0.163

The VirtualBox is set up with a Bridged Adapter.

When I try to ping the VirtualBox from a CMD prompt on my PC, I get:

Pinging 10.0.0.163 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.0.0.163:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I may be wrong (networks are NOT my strong point), but the VirtualBox environment should be seen as a separate machine and I should be able to send network traffic between my PC and the Virtual Machine, yes?

TIA for any assistance!

[mpack]

AFAIK, neither Win10 nor Win11 responds to ICMP (ping) messages by default, for security reasons.

[Eeyore]

Thanks, mpack...

Assuming that Windows 10 and Windows 11 will not respond to pings as you stated, I set up the sending/receiving applications (Sending from the PC, Receiving on the VM). The sending application is generating TCP Send errors (connect timed out). So it looks like there is an issue with the communications... I just don't know if what I am trying to do is even feasible or if I have a configuration issue.

Thanks to anyone who can help shed some light on this.

[scottgus1]

Ping can be turned on in Windows Firewall: enable ICMP Echo Request for at lease Private and Domain networks. If you have other security software, you might need to enable such in their firewall, too.

In both Windowses, please run this in the command prompt and post the output:

ipconfig /all

Please label which is which.

Also, Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. 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.)

[Eeyore]

This is the IPCONFIG /ALL from the PC:

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-7IUF31A
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.va.comcast.net

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : B4-B6-86-E0-12-9C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 0A-00-27-00-00-10
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80:43b3:80d0:b336%16(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 705298471
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-A9-F2-DC-B4-B6-86-E0-12-9C
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : D2-32-4B-33-99-21
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 92-32-4B-33-99-21
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : hsd1.va.comcast.net
Description . . . . . . . . . . . : Realtek RTL8822BE 802.11ac PCIe Adapter
Physical Address. . . . . . . . . : 90-32-4B-33-99-21
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2601:5c9aa00::ffd4(Preferred)
Lease Obtained. . . . . . . . . . : Wednesday, March 23, 2022 11:13:25 AM
Lease Expires . . . . . . . . . . : Sunday, March 27, 2022 4:22:56 PM
IPv6 Address. . . . . . . . . . . : 2601:5c9aa00:97c:a6a5f6b9(Preferred)
Temporary IPv6 Address. . . . . . : 2601:5c9aa00:45b2:93dc:5656:a6ff(Deprecated)
Link-local IPv6 Address . . . . . : fe80::97c:a6a5f6b9%4(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.165(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, March 23, 2022 11:13:23 AM
Lease Expires . . . . . . . . . . : Saturday, March 26, 2022 5:15:45 PM
Default Gateway . . . . . . . . . : fe80::4db:48ff:fe7d:898b%4
10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 43004491
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-A9-F2-DC-B4-B6-86-E0-12-9C
DNS Servers . . . . . . . . . . . : 2001:4860:4860::8888
2001:4860:4860::8844
75.75.75.75
75.75.76.76
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 90-32-4B-33-99-22
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes



This is the IPCONFIG /ALL from the VirtualBox:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-9DJNQ31
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.va.comcast.net

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : hsd1.va.comcast.net
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . . . . : 08-00-27-55-FA-80
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2601:5c9aa00::6d54(Preferred)
Lease Obtained. . . . . . . . . . : Friday, March 25, 2022 11:16:37 AM
Lease Expires . . . . . . . . . . : Tuesday, March 29, 2022 11:16:37 AM
IPv6 Address. . . . . . . . . . . : 2601:5c9aa00fe00:45cc:4245(Preferred)
Temporary IPv6 Address. . . . . . : 2601:5c9aa00:8123153:f(Preferred)
Link-local IPv6 Address . . . . . : fe80:fe00:45cc:4245%4(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.163(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, March 25, 2022 11:16:36 AM
Lease Expires . . . . . . . . . . : Sunday, March 27, 2022 11:16:36 AM
Default Gateway . . . . . . . . . : fe80::4db:48ff:fe7d:898b%4
10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 101187623
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-CD-4C-2E-08-00-27-55-FA-80
DNS Servers . . . . . . . . . . . : 2001:558:feed::1
2001:558:feed::2
75.75.75.75
75.75.76.76
2601:5c9aa00:4db:48ff:fe7d:898b
2001:558:feed::1
2001:558:feed::2
NetBIOS over Tcpip. . . . . . . . : Enabled


Again, TIA for all help.

[BillG]

It will make things clearer if you use the standard vm terms. The physical PC is the host, the vm is the guest. VirtualBox is the name of the virtualization program.

If the host and guest are bridged and both have 10.0.0.x IP addresses, VirtualBox is not really involved anymore. As far as the network protocols are concerned, they are just two devices on the LAN.

If you at looking at a sandbox setup, look at Scott's VirtualBox networking with pictures. viewtopic.php?t=96608

[scottgus1]

Your VM is Bridged, good, and the VM is getting its IP address from DHCP, so it looks like Bridged is working. Everything looks properly set up.

If you can ping 8.8.8.8 in the VM, then the network is working. Look at the Windows Firewalls in each OS.

[fth0]

VirtualBox uses the Ethernet MAC address of the host's wireless adapter when bridging to a wireless adapter, and this can be subject to possible misbehaviors of DHCP servers and routers.

Can you simultaneously ping -t 8.8.8.8 from the host and the guest?