[Solved] From Windows10 to Window10 Reply from Ip Destination host unreachable

Discussions related to using VirtualBox on Windows hosts.

[Solved] From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby sergorl » 17. Aug 2019, 22:34

My host is Windows 10 and my target (guest) is Windows 10 too.

In network settings inside virtual image for guest I choose "Network bridge".

ping host from guest gives me:
Reply from IpGuest: Destination host unreachable.

and ping guest from host gives me the next info:
Reply from IpHost: Destination host unreachable.

I want to use guest for windows kernel debugging, so I try to turn connection via ping at first.

How can I fix it?
Last edited by socratis on 1. Sep 2019, 12:41, edited 1 time in total.
Reason: Marked as [Solved].
sergorl
 
Posts: 7
Joined: 17. Aug 2019, 22:25

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby socratis » 18. Aug 2019, 02:11

Take a look at ch. 6.2. Introduction to Networking Modes, especially the Overview of Networking Modes table. See what connections you have available to talk between host and guest: HostOnly and Bridged. I would choose HostOnly, it's always available.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
 
Posts: 27285
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby scottgus1 » 18. Aug 2019, 02:47

Also, Windows may (does?) not allow responses to ping by default. You have to turn it on in the Windows firewall, "File and Printer Sharing (Echo Request - ICMPv4-In)", on Private networks at least, domain & public too if your Virtualbox network connection is not "private" type in either OS.
Human government is like that crazy uncle who hides a quarter in his fist behind his back, then asks you to guess which fist the quarter is in...
No matter which side you choose, Left or Right, both Sides are empty.
scottgus1
Volunteer
 
Posts: 4876
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Win7

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby sergorl » 18. Aug 2019, 13:17

@socratis, Im my Virtual Box I have no "HosOnly". Instead I have "Host-only adapter" and using this option with ping gives me
"Request timed out."
for both machines.
sergorl
 
Posts: 7
Joined: 17. Aug 2019, 22:25

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby sergorl » 18. Aug 2019, 14:29

@scottgus1, no, It doesn't work.
sergorl
 
Posts: 7
Joined: 17. Aug 2019, 22:25

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby socratis » 19. Aug 2019, 04:16

sergorl wrote: I have "Host-only adapter" and using this option with ping gives me "Request timed out." for both machines

That's not enough information to continue I'm afraid, we need some numbers. We need to see the output, from both the host and the guest, of the command:

    ipconfig /all
and from the host of the command:

    "C:\Program Files\Oracle\VirtualBox\VBoxManage" list hostonlyifs
    "C:\Program Files\Oracle\VirtualBox\VBoxManage" list dhcpservers
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
 
Posts: 27285
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby sergorl » 22. Aug 2019, 11:35

socratis, here is requirment output

ipconfig inside the host machine gives me:
Code: Select all   Expand viewCollapse view
C:\Users\sergorl>ipconfig

Настройка протокола IP для Windows

Адаптер Ethernet Ethernet:
   Состояние среды . . . . . . . . . : Среда передачи недоступна.
   DNS-суффикс подключения . . . . . :


Адаптер Ethernet VirtualBox Host-Only Network:
   DNS-суффикс подключения . . . . . :
   Локальный IPv6-адрес канала . . . : some MAC
   Автонастройка IPv4-адреса . . . . : 169.254.247.17
   Маска подсети . . . . . . . . . . : 255.255.0.0
   Основной шлюз . . . . . . . . . . :


Адаптер беспроводной локальной сети Подключение по локальной сети* 1:
   Состояние среды . . . . . . . . . : Среда передачи недоступна.
   DNS-суффикс подключения . . . . . :


Адаптер беспроводной локальной сети Подключение по локальной сети* 2:
   Состояние среды . . . . . . . . . : Среда передачи недоступна.
   DNS-суффикс подключения . . . . . :


Адаптер беспроводной локальной сети Беспроводная сеть:
   DNS-суффикс подключения . . . . . :
   Локальный IPv6-адрес канала . . . : some MAC
   IPv4-адрес. . . . . . . . . . . . : 192.168.1.81
   Маска подсети . . . . . . . . . . : 255.255.255.0
   Основной шлюз . . . . . . . . . . : 192.168.1.1

Адаптер Ethernet Сетевое подключение Bluetooth:
   Состояние среды . . . . . . . . . : Среда передачи недоступна.
   DNS-суффикс подключения . . . . . :

Unfortunately, I don't know how to change on english output of ping.

ipconfig inside guest virtual windows 10 gives me:
Code: Select all   Expand viewCollapse view
C:\Users\User>ipconfig

Windows IP Configuration

Ethernet adapter Ethernet 3:
   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::4d88:568c:aa97:2b42%13
   Autoconfiguration IPv4 Address. . : 169.254.43.66
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

Code: Select all   Expand viewCollapse view
C:\Users\sergorl>"C:\Program Files\Oracle\VirtualBox\VBoxManage" list hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            e275bfc6-9767-4505-a51c-cdff73deb56e
DHCP:            Enabled
IPAddress:       169.254.247.17
NetworkMask:     255.255.0.0
IPV6Address:     fe80::90aa:8071:6a9b:f711
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:11
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


C:\Users\sergorl>"C:\Program Files\Oracle\VirtualBox\VBoxManage" list dhcpservers
NetworkName:    HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
IP:             192.168.56.100
NetworkMask:    255.255.255.0
lowerIPAddress: 192.168.56.101
upperIPAddress: 192.168.56.254
Enabled:        Yes
Global options:
   1:255.255.255.0
Last edited by socratis on 22. Aug 2019, 12:21, edited 1 time in total.
Reason: Enclosed the information in [code] tag for better readability
sergorl
 
Posts: 7
Joined: 17. Aug 2019, 22:25

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby socratis » 22. Aug 2019, 12:36

sergorl wrote:Адаптер Ethernet VirtualBox Host-Only Network:
Локальный IPv6-адрес канала . . . : some MAC
Some MAC? No, that's not some MAC, that's the IPv6 address. And even if it was a MAC address, are you are obfuscating a fake, random, useless-except-your-host MAC? Security is a good thing, paranoia is not.

sergorl wrote: Автонастройка IPv4-адреса . . . . : 169.254.247.17
That's an APIPA address. It looks like your HostOnly adapter is not set up properly. Go to File » Host Network Manager. Make sure that the "Properties" is enabled, and in the "Adapter" tab at the bottom select "Configure Adapter Manually" » IPv4 Address = 192.168.56.1. Restart your computer, restart your VM.

sergorl wrote:C:\Users\sergorl>ipconfig
When I'm asking for the output of the command "ipconfig /all" I expect that command, not the one you thought would be good enough (ipconfig). Please pay closer attention to what's asked of you next time...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
 
Posts: 27285
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby sergorl » 23. Aug 2019, 00:27

socratis, no, it doesn't work:

[img]
https://ibb.co/1dQT54V
[/img]

From host:
Code: Select all   Expand viewCollapse view
C:\Users\sergorl>ipconfig /all

Настройка протокола IP для Windows

   Имя компьютера  . . . . . . . . . : DESKTOP-7VNJ58H
   Основной DNS-суффикс  . . . . . . :
   Тип узла. . . . . . . . . . . . . : Гибридный
   IP-маршрутизация включена . . . . : Нет
   WINS-прокси включен . . . . . . . : Нет

Адаптер Ethernet Ethernet:

   Состояние среды. . . . . . . . : Среда передачи недоступна.
   DNS-суффикс подключения . . . . . :
   Описание. . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Физический адрес. . . . . . . . . : B4-B6-86-DB-58-5F
   DHCP включен. . . . . . . . . . . : Да
   Автонастройка включена. . . . . . : Да

Адаптер Ethernet VirtualBox Host-Only Network:

   DNS-суффикс подключения . . . . . :
   Описание. . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Физический адрес. . . . . . . . . : 0A-00-27-00-00-11
   DHCP включен. . . . . . . . . . . : Нет
   Автонастройка включена. . . . . . : Да
   Локальный IPv6-адрес канала . . . : fe80::90aa:8071:6a9b:f711%17(Основной)
   IPv4-адрес. . . . . . . . . . . . : 192.168.56.1(Основной)
   Маска подсети . . . . . . . . . . : 255.255.0.0
   Основной шлюз. . . . . . . . . :
   IAID DHCPv6 . . . . . . . . . . . : 520749095
   DUID клиента DHCPv6 . . . . . . . : 00-01-00-01-22-A2-83-D6-B4-B6-86-DB-58-5F
   DNS-серверы. . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBios через TCP/IP. . . . . . . . : Включен

Адаптер беспроводной локальной сети Подключение по локальной сети* 1:

   Состояние среды. . . . . . . . : Среда передачи недоступна.
   DNS-суффикс подключения . . . . . :
   Описание. . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Физический адрес. . . . . . . . . : 96-B8-6D-76-A8-FE
   DHCP включен. . . . . . . . . . . : Да
   Автонастройка включена. . . . . . : Да

Адаптер беспроводной локальной сети Подключение по локальной сети* 2:

   Состояние среды. . . . . . . . : Среда передачи недоступна.
   DNS-суффикс подключения . . . . . :
   Описание. . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
   Физический адрес. . . . . . . . . : 94-B8-6D-76-A8-FF
   DHCP включен. . . . . . . . . . . : Да
   Автонастройка включена. . . . . . : Да

Адаптер беспроводной локальной сети Беспроводная сеть:

   DNS-суффикс подключения . . . . . :
   Описание. . . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8265
   Физический адрес. . . . . . . . . : 94-B8-6D-76-A8-FE
   DHCP включен. . . . . . . . . . . : Да
   Автонастройка включена. . . . . . : Да
   Локальный IPv6-адрес канала . . . : fe80::94f6:50c6:d10e:7fd4%3(Основной)
   IPv4-адрес. . . . . . . . . . . . : 192.168.1.81(Основной)
   Маска подсети . . . . . . . . . . : 255.255.255.0
   Аренда получена. . . . . . . . . . : 22 August 2019 22:16:46
   Срок аренды истекает. . . . . . . . . . : 23 August 2019 22:16:46
   Основной шлюз. . . . . . . . . : 192.168.1.1
   DHCP-сервер. . . . . . . . . . . : 192.168.1.1
   IAID DHCPv6 . . . . . . . . . . . : 60078189
   DUID клиента DHCPv6 . . . . . . . : 00-01-00-01-22-A2-83-D6-B4-B6-86-DB-58-5F
   DNS-серверы. . . . . . . . . . . : 192.168.1.1
   NetBios через TCP/IP. . . . . . . . : Включен

Адаптер Ethernet Сетевое подключение Bluetooth:

   Состояние среды. . . . . . . . : Среда передачи недоступна.
   DNS-суффикс подключения . . . . . :
   Описание. . . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Физический адрес. . . . . . . . . : 94-B8-6D-76-A9-02
   DHCP включен. . . . . . . . . . . : Да
   Автонастройка включена. . . . . . : Да


from guest:
Code: Select all   Expand viewCollapse view
C:\Users\User>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : WinDev1905Eval
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Mixed
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter #2
   Physical Address. . . . . . . . . : 08-00-27-3D-39-77
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4d88:568c:aa97:2b42%13(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.43.66(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 319291431
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-78-7F-77-00-15-5D-24-F4-80
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
sergorl
 
Posts: 7
Joined: 17. Aug 2019, 22:25

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby fth0 » 23. Aug 2019, 02:57

sergorl wrote:   IPv4-адрес. . . . . . . . . . . . : 192.168.56.1(Основной)
   Маска подсети . . . . . . . . . . : 255.255.0.0

Just a quick note: The network mask of your Host-Only adapter is wrong, and should be 255.255.255.0. It conflicts with your wireless network this way.
fth0
Volunteer
 
Posts: 309
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby socratis » 23. Aug 2019, 04:28

There might be some confusion in there, you're right fth0, brings another recent topic in memory: Host-only network stops working, when connecting to 192.168.x.x IP-network...

But more importantly, the guest didn't receive an IP address, it's still using APIPA addressing:
sergorl wrote:
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::4d88:568c:aa97:2b42%13(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.43.66(Preferred)

@sergorl,
What happens if you open a Command Prompt window in the guest, and you enter the command:

    ipconfig /renew
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
 
Posts: 27285
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby sergorl » 26. Aug 2019, 15:15

When I did inside guest this :
Code: Select all   Expand viewCollapse view
ipconfig /renew

I saw:
Code: Select all   Expand viewCollapse view
C:\Users\User>ipconfig /renew

Windows IP Configuration

An error occurred while renewing interface Ethernet 3 : unable to contact your DHCP server. Request has timed out.

Also changing mask on 255.255.255.0 inside Host Network manager has no positive effect.
sergorl
 
Posts: 7
Joined: 17. Aug 2019, 22:25

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby fth0 » 27. Aug 2019, 00:54

@socratis:
I do not trust the Host Network Manager dialogs further than I can throw a rock ;) (see viewtopic.php?f=6&t=92547&p=452797&hilit=DHCP#p452797 for the details). Therefore I would recommend to Remove the existing Host-Only adapter, reboot the host, Create the Host-Only adapter anew, configure it, thereby verifying every step :!:, reboot the host again, and verify the Host-Only adapter again before using it.
fth0
Volunteer
 
Posts: 309
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, macOS, ...

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby socratis » 29. Aug 2019, 10:22

fth0 wrote:I do not trust the Host Network Manager dialogs

I'm using the "brute force solution", when I learned how to edit the VirtualBox.xml file... ;)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis
Site Moderator
 
Posts: 27285
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: From Windows10 to Window10 Reply from Ip Destination host unreachable

Postby sergorl » 1. Sep 2019, 12:17

@fth0, you are my saver! It works now: I did everything you wrote. I wonder to be a windows driver-kernel developer, but at first stage (tuning the connection between two machine for debugging) I meet such trouble, but you help me very much! Thank you :)
sergorl
 
Posts: 7
Joined: 17. Aug 2019, 22:25

Next

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Google [Bot] and 43 guests