Strange behavior with ping and tracert on Win10 guest

[apo2]

I have used VirtualBox 6.0.22 for Windows to VM host, and Windows 10 guest is running on it.
I want to get working of SMB file sharing with VM guest and NAS on the local-net, but latest version of Windows 10 Insider Preview build is failed to connect with SMB.
(SMB file sharing with VM guest and NAS had worked before ver.2004 build 19645.1)

I investigate nat networking is working collect or not. I tried ping and tracert with default router and other local-net network resources.

ping for default router(192.168.1.1) is working with collect response, but ping for NAS(192.168.1.8 ) is strange response from VM guest.
(Oracle Host only Adapter is assigned to 192.168.1.100, and is replying Destination host unreachable form this adapter!)

Code: Select all

C:\Users\apo2>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63
Reply from 192.168.1.1: bytes=32 time=1ms TTL=63

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\Users\apo2>ping 192.168.1.8

Pinging 192.168.1.8 with 32 bytes of data:
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.8: bytes=32 time=2ms TTL=63
Reply from 192.168.1.8: bytes=32 time=2ms TTL=63
Reply from 192.168.1.8: bytes=32 time=2ms TTL=63

Ping statistics for 192.168.1.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 2ms, Average = 2ms

C:\Users\apo2>ping 192.168.1.3

Pinging 192.168.1.3 with 32 bytes of data:
Reply from 192.168.1.3: bytes=32 time<1ms TTL=127
Reply from 192.168.1.3: bytes=32 time<1ms TTL=127
Reply from 192.168.1.3: bytes=32 time<1ms TTL=127
Reply from 192.168.1.3: bytes=32 time<1ms TTL=127

Ping statistics for 192.168.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

default router and VM host ip-address(192.168.1.3) on local-net are collect responding.
What is not working properly?

[apo2]

The results of tracert for default router and other local-net resources as the attached figure.

results of tracert

tracert unreachable.PNG (34.67 KiB) Viewed 878 times

[scottgus1]

The only thing I see unusual in your ping reports is:

C:\Users\apo2>ping 192.168.1.8

Pinging 192.168.1.8 with 32 bytes of data:
Reply from 192.168.1.100: Destination host unreachable.
Reply from 192.168.1.8: bytes=32 time=2ms TTL=63
Reply from 192.168.1.8: bytes=32 time=2ms TTL=63
Reply from 192.168.1.8: bytes=32 time=2ms TTL=63

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

Seems unusual to have a different reply in a ping report, and an 'unreachable' with 0% loss.

Bit of editing gone awry?

All the pings have 0% loss. What is the problem that the Pings are supposed to show?

If you can ping the NAS from the guest OS then the Virtualbox network is working and the problem lies elsewhere in the setup.

FWIW WannaCry forced a turn-off of SMB version 1 in Windows 10. If the NAS is old, it may only have SMB1, or might need SMB2 or 3 turned on.

The mention of 10.0.2.2 in the tracerts implies that your guest is on NAT. Your guest should be able to see the host LAN and access the LAN's NAS, if you can ping the NAS from the guest. See Virtualbox Networks: In Pictures


Please right-click the guest in the main Virtualbox window's guest list, choose "Show in Explorer/Finder/File Manager". In the window that opens, zip the guest's .vbox file, and post the zip file, using the forum's Upload Attachment tab, so we can see the guest's setup.

Also please post an 'ifconfig /all' from the host and guest.

[apo2]

Ping/tracert did not work because the Oracle Host Only Adapter was enabled with a halfway setting.
NAS has been enabling sharing by SMBv2 already. and now disable Oracle Host Only Adapter in VM host settings.

SMB file share between VM guest (Win10 Insider Preview build 20185.1000) and NAS on the local-net are going well again.

Thanks.

[scottgus1]

OK, thanks for letting us know.

If you were trying to connect the guest to the LAN & NAS via Host-Only, that wouldn't work. Host-Only traffic does not leave the host PC.