HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- tracert but cannot ping host
Operating System - HP-UX
1834107
Members
2277
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2006 10:16 PM
10-16-2006 10:16 PM
tracert but cannot ping host
I had a case the other day where I could traceroute to a host but could not ping.
And I wondered why?
Can anyone explain?
Thanks.
And I wondered why?
Can anyone explain?
Thanks.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2006 10:21 PM
10-16-2006 10:21 PM
Re: tracert but cannot ping host
Shalom,
Based on the information provided there is no way anyone can explain this.
I can try and help with diagnosis:
1) Check the system nic light and see that the link light is lit.
2) Check the switch for errors, by looking at it or loggin on.
3) Check with networking and see if tracert has been diabled. Its pretty common to stop this servivce because it can be used for denial of service.
4) Check /var/adm/syslog/syslog.log
SEP
Based on the information provided there is no way anyone can explain this.
I can try and help with diagnosis:
1) Check the system nic light and see that the link light is lit.
2) Check the switch for errors, by looking at it or loggin on.
3) Check with networking and see if tracert has been diabled. Its pretty common to stop this servivce because it can be used for denial of service.
4) Check /var/adm/syslog/syslog.log
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2006 10:38 PM
10-16-2006 10:38 PM
Re: tracert but cannot ping host
Hi SM,
ping command sends "ICMP echo request" and receives "ICMP echo reply" these might be blocked.
Traceroute works different:
It sends some UDP-Packets with a ascending TTL and receives "ICMP time exceeded in-transit" while on the road or
"ICMP 192.151.52.241 udp port 33440 unreachable".
rgds
HGH
ping command sends "ICMP echo request" and receives "ICMP echo reply" these might be blocked.
Traceroute works different:
It sends some UDP-Packets with a ascending TTL and receives "ICMP time exceeded in-transit" while on the road or
"ICMP 192.151.52.241 udp port 33440 unreachable".
rgds
HGH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2006 11:22 PM
10-16-2006 11:22 PM
Re: tracert but cannot ping host
Hi,
According to ping(1M):
The ping command sends ICMP Echo Request (ECHO_REQUEST) packets to
host once per second. Each packet that is echoed back via an ICMP
Echo Response packet is written to the standard output, including
round-trip time.
And according to traceroute(1):
This program attempts to trace the route an IPv4/IPv6 packet would
follow to some internet host by launching UDP probe packets with a
small ttl (time to live) or hop-limit then listening for an ICMPv4 or
ICMPv6 "time exceeded" reply from a gateway. We start our probes
with a ttl of one and increase by one until we get an ICMPv4 or ICMPv6
"port unreachable" (which means we got to "host") or hit a max (which
defaults to 30 hops and can be changed with the -m flag). Three
probes (change with -q flag) are sent at each ttl setting and a line
is printed showing the ttl, address of the gateway and round trip time
of each probe. If the probe answers come from different gateways, the
address of each responding system will be printed. If there is no
response within a 5 sec. timeout interval (changed with the -w flag),
a "*" is printed for that probe.
So, by default, ping sends ICMP packets and traceroute sends UDP packets. Moreover, the destination ports are different. A firewall could deny packets based on any of these criteria.
PCS
According to ping(1M):
The ping command sends ICMP Echo Request (ECHO_REQUEST) packets to
host once per second. Each packet that is echoed back via an ICMP
Echo Response packet is written to the standard output, including
round-trip time.
And according to traceroute(1):
This program attempts to trace the route an IPv4/IPv6 packet would
follow to some internet host by launching UDP probe packets with a
small ttl (time to live) or hop-limit then listening for an ICMPv4 or
ICMPv6 "time exceeded" reply from a gateway. We start our probes
with a ttl of one and increase by one until we get an ICMPv4 or ICMPv6
"port unreachable" (which means we got to "host") or hit a max (which
defaults to 30 hops and can be changed with the -m flag). Three
probes (change with -q flag) are sent at each ttl setting and a line
is printed showing the ttl, address of the gateway and round trip time
of each probe. If the probe answers come from different gateways, the
address of each responding system will be printed. If there is no
response within a 5 sec. timeout interval (changed with the -w flag),
a "*" is printed for that probe.
So, by default, ping sends ICMP packets and traceroute sends UDP packets. Moreover, the destination ports are different. A firewall could deny packets based on any of these criteria.
PCS
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP