Announcement

Collapse

UPDATES

Welcome to The Cheat Police. Please bear with us as we rebuild the site. We know there are a lot of issues with the site and we are working on them. Badge lists and front page are the priority. TSA Applications and Updates will be online later. The forums are working.
See more
See less

How to do a traceroute

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to do a traceroute

    Replace the ip with the server you want to ping. it will write a txt file to C: that you can copy/paste.

    Provides a ping and path of each nameserver to ip specified, and writes a txt file called tracert to c:
    tracert 74.221.208.75 > c:trace.txt

    Pings ip specified with 32 bytes of data and writes a txt file called ping.txt to c:
    ping 74.221.208.75 > cing.txt

    Provides the path of each nameserver in numerical order to ip specified, pings the path with 100 bytes of data for 250 seconds,
    and writes a txt file called pathping to c:. Shows Lost/sent data when complete.
    pathping 74.221.208.75 > cathping.txt

    Pings the IP specified with 32 bytes of data 50 times, writes a txt file called ping50.txt to c:
    ping -n 50 74.221.208.75 > cing50.txt

    Running a Traceroute on Windows XP:

    1) Go to Start (start button on the lower left of the desktop)
    2) Choose 'Run'
    3) Type: "cmd" (no quotes)
    4) This should bring up a DOS prompt. Once there, type: "tracert domain.com" (without quotes)

    This should result in a series of hops from your computer to the server you are tracing

    example: tracert -h 30 69.65.45.172

    the -h 30 is the number of hops, depending on where you are located, you may not reach the ending ip address. From my house it's 20 hops to the 172 server.
    C:UsersShadivar>tracert -h 30 69.65.45.172

    Tracing route to 69.65.45.172 over a maximum of 30 hops

    1 10 ms 2 * * * Request timed out.
    3 12 ms 9 ms 8 ms ge-1-20-ur01.arlington.va.bad.comcast.net [68.87.129.217]
    4 9 ms 9 ms 9 ms te-9-1-ur02.arlington.va.bad.comcast.net [68.87.128.158]
    5 8 ms 9 ms 9 ms te-9-3-ur01.reston.va.bad.comcast.net [68.87.128.162]
    6 11 ms 9 ms 13 ms te-9-2-ur01.manassas.va.bad.comcast.net [68.87.129.113]
    7 9 ms 9 ms 11 ms te-7-2-ar01.manassascc.va.bad.comcast.net [68.87.129.189]
    8 20 ms 18 ms 19 ms po-10-ar01.howardcounty.md.bad.comcast.net [68.87.129.29]
    9 18 ms 21 ms 21 ms po-10-ar02.whitemarsh.md.bad.comcast.net [68.87.129.34]
    10 23 ms 23 ms 23 ms te-0-3-0-1-cr01.philadelphia.pa.ibone.comcast.net [68.86.90.77]
    11 27 ms 42 ms 28 ms pos-0-9-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.85.14]
    12 25 ms 24 ms 23 ms 204.70.144.1
    13 25 ms 26 ms 25 ms cr2-pos-0-7-3-1.newyork.savvis.net [204.70.195.97]
    14 51 ms 56 ms 52 ms cr1-loopback.chd.savvis.net [208.172.2.70]
    15 47 ms 47 ms 47 ms ber1-tengig-9-0-0.Chicago.savvis.net [204.70.195.114]
    16 59 ms 212 ms 206 ms ber1-vlan-241.chicagoequinix.savvis.net [204.70.196.22]
    17 55 ms 54 ms 55 ms v52-er1.Chi2.Servernap.net [66.252.3.114]
    18 55 ms 54 ms 54 ms v990-ae0.er1.Chi1.Servernap.net [69.39.239.178]
    19 56 ms 63 ms 56 ms pos2-1.csr1.Chi3.Servernap.net [69.39.239.170]
    20 56 ms 54 ms 55 ms 69.65.45.172

    Trace complete.

    As you can see everything is pretty good till chicago then my ping doubles. I also see that comcast don't like me by putting me on the "bad" routers.


    Apple users (probably not in here)
    1. Double-click the Hard Drive icon > Applications folder > Utilities folder > Network Utility program.
    2. Select the trace route tab and enter the domain name
    3. Press the
Working...
X