Tracing the Network Path

Posted on 2014-01-07
Last Modified: 2015-09-23
I want to know what is the network path which is taken from Location A to Location B & the return path. What is the way to achieve this ?

Is there any way to identify the path taken from Location A to Location B is the same as the return path from Location B to Location A.

Let me know how to check it.
Question by:SrikantRajeev
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
  • +3

Expert Comment

by:Jordan Medlen
ID: 39762589
tracert (Windows) or tracepath (Linux) will be what you'll want to run. Do you have access to a system at both locations? You will need to in order to find the return path.
LVL 11

Expert Comment

ID: 39762590
Extended ping can do that from a cisco device.
LVL 50

Expert Comment

by:Don Johnston
ID: 39762594
Best way is to ping and use the record route function. But that only works up to 9 hops.

For example, for a windows PC, you can use "ping -r 9"
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

LVL 11

Expert Comment

ID: 39762599
Tracert/Traceroute will give the path info from source to destination but will not give return path info from destination to source.
LVL 25

Expert Comment

ID: 39762677
it also kind of depends on the path that your packet takes between the two locations and how much detail you want to know.  you won't see every hop if it goes thru a tunnel of any kind (by design of how the technology works though) or MPLS networks (which is label switching, not IP so again by technology design).

Just something to be aware of anyway if you "know" there should be more in the trace list than you see.  There could be technologies used that mask "real" hops due to encapsulation.

but yes, trace route is what you want as that is the most, from a purely clients perspective, way to tell the path your packet takes.
LVL 18

Expert Comment

ID: 39764154
pathping <destination ip or hostname>

Using a PC. This does not show return path either but you will have to assume or hope that the to and fro paths are the same. May not be the same if there are alternate paths, especially if traffic conditions or policy exist

Author Comment

ID: 39764244
ping -r9 <IP Addresss> gives me the ping response with the path from source to destination.
I am not able to find out the reverse path for the ping reply to confirm if it the same path or diff path.

The traceroute also does the same. Any idea how to achieve this....
LVL 25

Expert Comment

ID: 39764957
run the same commands from the other side.  there's really no other way without having direct insight into the routing environment between the two points.
LVL 18

Expert Comment

ID: 39765235
You can try the source route option with tracert. That will give you your return path but unfortunately, this is usually blocked as hackers take advantage of it.

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
               [-R] [-S srcaddr] [-4] [-6] target_name

    -d                                  Do not resolve addresses to hostnames.
    -h maximum_hops    Maximum number of hops to search for target.
    -j host-list                  Loose source route along host-list (IPv4-only).
    -w timeout                 Wait timeout milliseconds for each reply.
    -R                                  Trace round-trip path (IPv6-only).
    -S srcaddr                    Source address to use (IPv6-only).
    -4                                   Force using IPv4.
    -6                                   Force using IPv6.

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
            [-r count] [-s count] [[-j host-list] | [-k host-list]]
            [-w timeout] [-R] [-S srcaddr] [-4] [-6] target_name

    -t                             Ping the specified host until stopped.
                                   To see statistics and continue - type Control-Break;
                                   To stop - type Control-C.
    -a                            Resolve addresses to hostnames.
    -n count                 Number of echo requests to send.
    -l size                     Send buffer size.
    -f                            Set Don't Fragment flag in packet (IPv4-only).
    -i TTL                     Time To Live.
    -v TOS                    Type Of Service (IPv4-only. This setting has been deprecated
                                   and has no effect on the type of service field in the IP Head
    -r count                  Record route for count hops (IPv4-only).
    -s count                  Timestamp for count hops (IPv4-only).
    -j host-list          Loose source route along host-list (IPv4-only).
    -k host-list         Strict source route along host-list (IPv4-only).
    -w timeout             Timeout in milliseconds to wait for each reply.
    -R                        Use routing header to test reverse route also (IPv6-only).
                                    Per RFC 5095 the use of this routing header has been
                                    deprecated. Some systems may drop echo requests if
                                    this header is used.

    -S srcaddr          Source address to use.
    -4                              Force using IPv4.
    -6                              Force using IPv6.

Usage: pathping [-g host-list] [-h maximum_hops] [-i address] [-n
                [-p period] [-q num_queries] [-w timeout]
                [-4] [-6] target_name

    -g host-list                 Loose source route along host-list.
    -h maximum_hops       Maximum number of hops to search for target.
    -i address                      Use the specified source address.
    -n                                    Do not resolve addresses to hostnames.
    -p period                        Wait period milliseconds between pings.
    -q num_queries             Number of queries per hop.
    -w timeout                      Wait timeout milliseconds for each reply.
    -4                                     Force using IPv4.
    -6                                     Force using IPv6.
LVL 25

Expert Comment

ID: 39765281
source routing won't give reliable data though because you specify that list.  So it only pertains to that trace route test.  It's not the true return path for normal data.
LVL 50

Accepted Solution

Don Johnston earned 500 total points
ID: 39768447
The ICMP record route function is bi-directional. As long as there's room in the field (up to 9 entries), there should be entries for each hop in both directions.

Of course that assumes the destination and intermediate devices support the feature.

Author Comment

ID: 39774946
Will check this options

Author Comment

ID: 40992202
I've requested that this question be closed as follows:

Accepted answer: 0 points for SrikantRajeev's comment #a39774946

for the following reason:


Author Closing Comment

ID: 40992203

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Management of Huawei B315 2 62
mlppp with hsrp tracking? 2 19
Network bogged down - slowing down some client PCs 10 78
Questions on USB 4 ports hub 4 55
Before I go to far, let's explain HA (High Availability) and why you should consider it.  High availability is the mechanism used to provide redundancy to any service at the same site and appears as a single service to the users of that service.  As…
David Varnum recently wrote up his impressions of PRTG, based on a presentation by my colleague Christian at Tech Field Day at VMworld in Barcelona. Thanks David, for your detailed and honest evaluation!
Viewers will learn how to properly install and use Secure Shell (SSH) to work on projects or homework remotely. Download Secure Shell: Follow basic installation instructions: Open Secure Shell and use "Quick Connect" to enter credentials includi…
After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question