- How to Solve a Destination Host Unreachable Error
- Reconnect with the rest of the web
- What to Know
- How to Fix a Destination Host Unreachable Error
- Cause of a Destination Host Unreachable Error
- How to Add the Correct Gateway Address for a Destination Host
- How to Check if Destination Host Unreachable Error Is Resolved
- Destination host unreachable, как достучаться до другой сети?
- Windows destination host unreachable
- Answered by:
- Question
- Answers
- Windows destination host unreachable
- Answered by:
- Question
- Answers
- маршрутизация «Destination Host Unreachable»
How to Solve a Destination Host Unreachable Error
Reconnect with the rest of the web
:max_bytes(150000):strip_icc()/TomWilton-85e2fcd3dc0e4ecfa54a8d137b2254d9.jpg)
What to Know
- Test the IPv6 connection to determine the default gateway IP, then compare it to the device’s configured gateway via netshell IP settings.
- Add a gateway: LAN settings >Internet Protocol Version 6 (TCP/IPv6) >Properties. Change Default Gateway to the correct address.
- To check if the error is resolved, enter a ping test in Command Prompt: C:\Users\Me>ping -6 151.101.194.114.
Receiving a destination host unreachable error in a Command Prompt network ping test can be frustrating. In this guide, we show you how to fix a destination host unreachable error on Windows devices, as well as how to add the correct gateway address for a destination host, and how to check if the error is resolved.
How to Fix a Destination Host Unreachable Error
In diagnosing the error, it’s useful to follow the steps to fix an IPv6 error first to see if they resolve your networking issues. If the problem persists, you need to look at your network infrastructure to establish where the issue is.
For this example, we’re going to check our Default Gateway settings, then follow the steps to fix them.
To start, we need to check our internet connection via a browser. For this example, we’ll check google.com to see if it loads on our device. If it does, we know there’s a problem on our local network, rather than a broader connection issue.
Next, we’re going to test our IPv6 connection to see if that’s where the issue lies. To do this, open the Command Prompt and use the following command to ping your original IP address, but type «ping -6» to isolate the IPv6 line.
You should get a reply in the Command Prompt, which looks like this:
The above reply comes from IP address 151.101.194.1.241, which seems to relate to the remote gateway handling our request. To check this, run a traceroute using the following command:
You should get a response, and it should resemble the following:
From this, we can make a judgment that 151.101.194.1.241 is configured as the default gateway. To check if this is as it should be, we can look at our IP settings via the netshell. To launch netshell, enter the following command:
With netshell open, enter this command:
The response will show our Local Area Connection details, with a reference line for the Default Gateway. In our example we see the following:
This confirms that 151.101.194.1.241 is currently configured as the default gateway, but when we look at our actual device’s IP address, we see it’s slightly different: 151.101.194.1.244.
Cause of a Destination Host Unreachable Error
There are many possible reasons for getting a “destination host unreachable” error, including things as simple as erroneously connected cables or an overly aggressive firewall. As you can see from the details below, we’re trying to ping a specific network device IP address, but the response we’re getting doesn’t provide much detail beyond the error itself:
C:\Users\Me>ping 151.101.194.114
Pinging 151.101.194.114 with 64 bytes of data:
Reply from 151.101.194.114: Destination host unreachable.
Reply from 151.101.194.114: Destination host unreachable.
Reply from 151.101.194.114: Destination host unreachable.
Reply from 151.101.194.114: Destination host unreachable.
So, what’s going on here? In simple terms, we’re trying to communicate with a device at the specified IP address, but the remote gateway is unable to direct our ping request to the host itself, and so it sends an echo message back to say that it can’t be found.
How to Add the Correct Gateway Address for a Destination Host
From the information gained above, we can see we need to add the correct gateway address via our Local Area Network (LAN) settings. To do this, follow these steps.
Select Settings > Network and Internet > Network Connections.
Right-click the relevant Local Area Network. Then, select Properties.
From the list, select Internet Protocol Version 6 (TCP/IPv6). Next, select Properties.
In the Properties tab, change the Default Gateway to the correct address. So, in this example, we change «151.101.194.1.241» to «151.101.194.1.244.»
Press OK to save the changes.
How to Check if Destination Host Unreachable Error Is Resolved
To check if the issue is resolved, go back to the Command Prompt and exit the netshell using the following command:
Now, we’re ready to try our ping test once more, using this command:
Just as before, the ping should come back with a reply showing the new Default Gateway.
As we can see, our ping test is now working and our connection is running as expected.
Destination host unreachable, как достучаться до другой сети?
Не могу достучаться до другого компьютера все перепробовал бошка кипит от этого уже 
Destination host unreachable
Всем привет Делаю простенькое задание по маршрутизации сети и выскакивает ошибка «Destination host.
Cisco Packet Tracer. Destination host unreachable
Только начал изучать cisco, вот такая лаба, вроде сделал, но не пингуется, подскажите пожалуйста
Cisco Packet Tracer. Destination host unreachable
Всем добрый вечер. Помогите разобраться.. Дано задание. Схема сети:два маршрутизатора Cisco1841.
Cisco Packet Tracer. Destination host unreachable
Настройка маршрутизации через OSPF. Как видите, 3 роутера, у каждого своя подсеть. Если все.
вот сижу и путаюсь я не пойму как прописать
Добавлено через 1 минуту
каждый компьютер должен автоматический получать пинг, сеть анонсировал через OSPF путаться начал 
в самом начале закинул
Добавлено через 1 час 14 минут
вот только что закончил,как сказал также прописал через ip route на каждый роутер, теперь вопрос а мог бы я другим способом поступить не прописывая ? просто тогда зачем ospf?
| Тематические курсы и обучение профессиям онлайн Профессия Cпециалист по кибербезопасности (Skillbox) DevOps-инженер (Нетология) Профессия DevOps-инженер PRO (Skillbox) |
да блин все работает.
вот вам с двумя областями:
а) одна — backbone, вторая — nssa (как у вас было)
б) одна — backbone, вторая — normal
Вложения
 | NSSA _7 LaB OSPF.rar (57.7 Кб, 2 просмотров) |
| Normal _7 LaB OSPF.rar (57.8 Кб, 2 просмотров) |
Заказываю контрольные, курсовые, дипломные и любые другие студенческие работы здесь или здесь.
Cisco Packet Tracer ошибка Destination host unreachable
Здравствуйте. Столкнулся с такой проблемой: верхняя часть сети (пк1-с1 и пк2-с2 в роутер 1) не.
Destination host unreachable
Настроил с одной стороны EIGRP с другой OSPF , но никак не могу понять как настроить DCE/DTE и при.
Не удается инициализировать интерфейс Windows Sockets. Destination address unreachable
Здравствуйте. Собственно, из названия темы вы уже могли понять суть вопроса. Не могу выйти в.
IoT девайс, destination host unreacheble
Добрый день. Помогите, пожалуйста, выяснить: почему не пингуется смартфон и IoT девайс с.
Packet Tracer. Destination host unreachabl
Доброго времени суток, уважаемые форумчяне. Прошу помощи с настройкой сети. Не получается.
Как достучаться с одного компа на другой
Ps сразу прошу прощения если не в ту ветку форума, не нашел куда нужно(если что перенесите плиз) .
Windows destination host unreachable
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I have a weird issue. I think.
I just noticed that on my servers (all HP and setup by someone else), if I would ping an IP address of a downed machine or an IP not in use all in the same subnet, I get a message of «Reply from 10.10.10.20: Destination host unreachable and the server IP that I am pinging from is the 10.10.10.20.
From my experience, I should be getting a «request timed out message» only if it’s on the same subnet. Anyone know why I’m getting the Destination host unreachable message when I’m not trying to reach a different subnet and why is it coming from my machine?
Answers
The response «Reply from 10.10.10.20: Destination host unreachable.» actually is the correct one. When pinging a host on your own subnet the sender will first send an ARP request for the MAC address of the associated IP address. Since the host does not exist, the sending station is reporting to you that the destination host is unreachable because the ARP request was not completed. The actual ICMP echo was never sent which is why you aren’t getting a «request timed out» message. You can’t send a layer 3 packet if you can’t resolve the layer 2 address of the host (or the gateway if the destination is on another network).
The reason why you would not get this same message if you were pinging hosts on a different subnet is that the sender would ARP for the gateway address since the target is on a different subnet. The ARP completes properly and the ICMP echo is sent but the timeout value is reached since the destination host never responded with an echo-reply.
It seems that Win7/2008 just gives more specific failure reasons now than Windows XP does. This is a good thing in my estimation.
Matt W. CCNP, CCDA, CCNA-S, RHCT, MCSE, MCSA, MCP+I, A+
Windows destination host unreachable
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I have a weird issue. I think.
I just noticed that on my servers (all HP and setup by someone else), if I would ping an IP address of a downed machine or an IP not in use all in the same subnet, I get a message of «Reply from 10.10.10.20: Destination host unreachable and the server IP that I am pinging from is the 10.10.10.20.
From my experience, I should be getting a «request timed out message» only if it’s on the same subnet. Anyone know why I’m getting the Destination host unreachable message when I’m not trying to reach a different subnet and why is it coming from my machine?
Answers
The response «Reply from 10.10.10.20: Destination host unreachable.» actually is the correct one. When pinging a host on your own subnet the sender will first send an ARP request for the MAC address of the associated IP address. Since the host does not exist, the sending station is reporting to you that the destination host is unreachable because the ARP request was not completed. The actual ICMP echo was never sent which is why you aren’t getting a «request timed out» message. You can’t send a layer 3 packet if you can’t resolve the layer 2 address of the host (or the gateway if the destination is on another network).
The reason why you would not get this same message if you were pinging hosts on a different subnet is that the sender would ARP for the gateway address since the target is on a different subnet. The ARP completes properly and the ICMP echo is sent but the timeout value is reached since the destination host never responded with an echo-reply.
It seems that Win7/2008 just gives more specific failure reasons now than Windows XP does. This is a good thing in my estimation.
Matt W. CCNP, CCDA, CCNA-S, RHCT, MCSE, MCSA, MCP+I, A+
маршрутизация «Destination Host Unreachable»
  | Список форумов SYSAdmins.RU -> NETWORKS | На страницу 1, 2 След. |
| Автор | |||||
|---|---|---|---|---|---|
| $kat Новичок Зарегистрирован: 09.08.2009
|
| ||||
| Вернуться к началу |
| ||||
 | |||||
| Зарегистрируйтесь и реклама исчезнет! | |||||
| |||||
| Rainmib Старожил форума Зарегистрирован: 28.09.2010 |
| ||||
| Вернуться к началу |
| ||||
| |||||
| -=chelovek=- Почетный житель
Зарегистрирован: 14.11.2009 |
| ||||
| Вернуться к началу |
| ||||
| |||||
| $kat Новичок Зарегистрирован: 09.08.2009
|
| ||||
| Вернуться к началу |
| ||||
| |||||
| $kat Новичок Зарегистрирован: 09.08.2009
|
| ||||
| Вернуться к началу |
| ||||
| |||||
| 6PATyCb Активный участник Зарегистрирован: 19.02.2009
|
| ||||
| Вернуться к началу |
| ||||
| |||||
| $kat Новичок Зарегистрирован: 09.08.2009
|
| ||||
| Вернуться к началу |
| ||||
| |||||
| lex_shadow Новичок Зарегистрирован: 04.12.2008
|
| ||||
| Вернуться к началу |
| ||||
| |||||
| vlaryk Networks guru  Networks guru » title=» Networks guru » border=»0″/>
Зарегистрирован: 28.01.2009 |
| ||||
| Вернуться к началу |
| ||||
| |||||
| lex_shadow Новичок Зарегистрирован: 04.12.2008 | |||||
