On Tue, 26 Oct 2010, in the Usenet newsgroup comp.os.linux.redhat, in article
Post by Muruganandam ChandrasekaranI just need to know reason behind this.
Not enough detail, and what information is there is ambiguous
Post by Muruganandam ChandrasekaranI am able to ping the destination of same network
but i am not able to traceroute a destination. what would be a reason
behind this.
Depends. What version of traceroute? What options used? What
firewall rules on both systems? Any routers involved - if so, what
forwarding rules?
Start by reading RFC0792 which you can find using any search engine
0792 Internet Control Message Protocol. J. Postel. September 1981.
(Format: TXT=30404 bytes) (Obsoletes RFC0777) (Updated by RFC0950,
RFC4884) (Also STD0005) (Status: STANDARD)
Then study the rather extensive man page for traceroute
[compton ~]$ whatis traceroute
traceroute (8) - print the route packets take to network host
[compton ~]$
The page for the Van Jacobson version from LBL is about 330 lines or
about 5 1/2 pages complete with a lot of examples. Then fire up a
packet sniffer such as
Accurate Network Monitor EtherDetect Packetyzer
AiroPeek EtherPeek PRTG
Analyzer Ettercap Sniff'em
Anasil GreedyDog Snoop
CommView IPDump2 TracePlus/Ethernet
dSniff LinkFerret WinDump
EtherApe OmniPeek Wireshark
or the UNIX standard grand-daddy of them all
[compton ~]$ whatis tcpdump
tcpdump (8) - dump traffic on a network
[compton ~]$
Old guy