Destination port unreachable linux

What is the Destination Port Unreachable Error Message, and How to Fix it?

Team CoreNetworkZ explained various ICMP error messages in this blog. Today we are explaining one of the common ICMP error replies when you ping a remote device from your computer, Destination Port Unreachable message.

You can see this error while you ping a remote device or remote server from your PC if the ping operation could not succeed.

This tutorial discusses the reasons for getting the ICMP error Destination Unreachable (Port Unreachable) and explain how to resolve this issue.

What Does Destination Unreachable (Port Unreachable) Mean?
The Destination Port Unreachable error tells us that the ping packet we send failed to reach the desired destination and dropped.

Let me explain this with a real-world example. When someone pings a remote host, the ping packets will travel from his device to the destination.

Ping packets will reach the destination gateway, and the remote router redirects them to the exact host.

If the host is too busy or the device port does not support the type of packets we send, it will result in the reply Destination Port Unreachable.

It tells us the problem lies with the host, and the network route up to the remote host is working fine.

So, this reply is from the host (not from the remote gateway) and different from the following ICMP replies.

Now let us check what causes this problem.

Unaccepted Protocol Type-
One of the main reasons to receive Port Unreachable error is sending packets to a remote host without the required protocol to be accepted by the active port of the remote host.

How to Fix Destination Port Unreachable Error?
Troubleshooting the ICMP Port Unreachable error is a bit difficult because the issue lies with the remote device.

In most cases, this error reply is generated by the remote port due to protocol mismatch or security issues.

If you see the ICMP reply Destination Unreachable (Port Unreachable) when you ping an address, follow the steps provided below.

Ping a Different Address
Try to ping a different IP address or web URL.

For example, if you receive the ICMP reply Port Unreacbale when you ping https:www.corenetworkz.com, try to ping https://www.google.com.

If you get packet received messages from the destination, you can verify the source of the problem.

Theoretically, Port Unreachable message comes with UDP and TCP connection failure.

Alex George is a Computer Science and Engineering graduate. He completed networking courses CCNA, CCNP, and MSCE. Now, he works as a Senior Network Engineer in a leading MNC. Webmaster Skills: Alex has been a blogger since 2004. He has a working knowledge of HTML, CSS, PHP, and JavaScript.

• Get link
• Facebook
• Twitter
• Pinterest
• Email
• Other Apps

Источник

Thread: Destination Port Unreachable !!

Tea Glorious Tea!

Destination Port Unreachable !!

I ‘ve got a problem ! I could not see this page http://chinmaya_n.hyperphp.com/. I created that using Drupal ( actually learning Drupal ). Recently I changed my ISP (internet service provider) from then this page dont opens on my desktop.
I tried «$ ping chinmaya_n.hyperphp.com» in the terminal. It gives an error stating: From a.7.de.static.xlhost.com (206.222.7.10) icmp_seq=2 Destination Port Unreachable
I can see it in my friends system!! (having a different ISP)
I tried with all the browsers in my system but of no use.

edit: I found that this site is opening on my friends system who is having the same ISP as I ‘ve!!
Does the problem lies in my system.
Can anyone please help !

Ubuntu addict and loving it

Re: Destination Port Unreachable !!

Tea Glorious Tea!

Re: Destination Port Unreachable !!

Yes I’m able to ping other sites !

I hosted this on other server.

Tea Glorious Tea!

Re: Destination Port Unreachable !!

I observed that even in Win XP that site is opening, but the problem comes in ubuntu only !

Edit: I also observed that no subdomain of that is loading in my linux system ! but http://hyperphp.com/ is working fine.
I mean http://nchinmaya.hyperphp.com/ have the same problem!

chinmaya@chinmaya-desktop:~$ ping chinmaya_n.hyperphp.com PING chinmaya_n.hyperphp.com (209.190.24.9) 56(84) bytes of data. From a.7.de.static.xlhost.com (206.222.7.10) icmp_seq=1 Destination Port Unreachable From a.7.de.static.xlhost.com (206.222.7.10) icmp_seq=2 Destination Port Unreachable From a.7.de.static.xlhost.com (206.222.7.10) icmp_seq=3 Destination Port Unreachable From a.7.de.static.xlhost.com (206.222.7.10) icmp_seq=4 Destination Port Unreachable From a.7.de.static.xlhost.com (206.222.7.10) icmp_seq=5 Destination Port Unreachable From a.7.de.static.xlhost.com (206.222.7.10) icmp_seq=6 Destination Port Unreachable ^Z [1]+ Stopped ping chinmaya_n.hyperphp.com chinmaya@chinmaya-desktop:~$ ping google.com PING google.com (74.125.67.100) 56(84) bytes of data. 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=1 ttl=43 time=254 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=2 ttl=43 time=255 ms 64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=3 ttl=43 time=255 ms ^Z [4]+ Stopped ping google.com chinmaya@chinmaya-desktop:~$

Источник

Why can’t I ping the outside world from my ubuntu box?

I can’t seem to ping or ssh to an outside domain. Internal IP addresses work fine. It resolves the IP address, so I don’t think it is DNS. The local host seems to intercept my requests somehow. Curl works. This is ubuntu server 10.4. My internal IP is 192.168.1.14. EDIT: I stopped ufw via stop ufw and added some more info below.

matt@valkyrie:~$ ping google.com PING google.com (173.194.33.104) 56(84) bytes of data. From valkyrie (192.168.1.14) icmp_seq=1 Destination Port Unreachable From valkyrie (192.168.1.14) icmp_seq=2 Destination Port Unreachable From valkyrie (192.168.1.14) icmp_seq=3 Destination Port Unreachable From valkyrie (192.168.1.14) icmp_seq=4 Destination Port Unreachable From valkyrie (192.168.1.14) icmp_seq=5 Destination Port Unreachable From valkyrie (192.168.1.14) icmp_seq=6 Destination Port Unreachable ^C --- google.com ping statistics --- 6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 4999ms 

root@valkyrie:/etc/nagios3# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 eth0 

root@valkyrie:/etc/nagios3# traceroute google.com traceroute to google.com (173.194.33.104), 30 hops max, 60 byte packets 1 valkyrie (192.168.1.14) 0.409 ms 0.459 ms 0.481 ms 

root@valkyrie:/etc/nagios3# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination blockcontrol_in all -- anywhere anywhere state NEW mark match !0x14 Chain FORWARD (policy ACCEPT) target prot opt source destination blockcontrol_fw all -- anywhere anywhere state NEW mark match !0x14 Chain OUTPUT (policy ACCEPT) target prot opt source destination blockcontrol_out all -- anywhere anywhere state NEW mark match !0x14 Chain blockcontrol_fw (1 references) target prot opt source destination DROP all -- anywhere anywhere mark match 0xa RETURN all -- anywhere arbiter RETURN all -- 192.168.1.0/24 192.168.1.0/24 NFQUEUE all -- anywhere anywhere NFQUEUE num 92 Chain blockcontrol_in (1 references) target prot opt source destination DROP all -- anywhere anywhere mark match 0xa RETURN all -- anywhere anywhere RETURN all -- 192.168.1.0/24 anywhere NFQUEUE all -- anywhere anywhere NFQUEUE num 92 Chain blockcontrol_out (1 references) target prot opt source destination REJECT all -- anywhere anywhere mark match 0xa reject-with icmp-port-unreachable RETURN all -- anywhere anywhere RETURN all -- anywhere arbiter RETURN all -- anywhere 192.168.1.0/24 RETURN tcp -- anywhere anywhere tcp dpt:https RETURN tcp -- anywhere anywhere tcp dpt:www NFQUEUE all -- anywhere anywhere NFQUEUE num 92 

Источник