1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Trace Route From Windows

Discussion in 'Bits & Bytes' started by ethics, Nov 22, 2002.

  1. ethics

    ethics Pomp-Dumpster Staff Member

    Background: In my constant war with the ISP that took over the one that I signed a contract with, I am trying to explain to them that the site is slower than it used to be. Some days it's great, some days it's unbearable. They are asking for trace routes.

    Now, I can run tracert on a command window but... Well, I think it there's gotta be something better for running and LOGGING ( so I can email it to them) the tracert.

    Any suggestions?
     
  2. mikeky

    mikeky Member

    You might find <a href="http://www.visualware.com/visualroute/index.html">Visual Route</a> and <a href="http://www.pingplotter.com/">Ping Plotter</a> useful for this.
     
  3. Advocat

    Advocat Viral Memes a Speciality Staff Member

    Ping Plotter, definitely. Let's you see which router is causing the holdup.
     
  4. ethics

    ethics Pomp-Dumpster Staff Member

    Excellent, thanks guys! :)
     
  5. Sir Joseph

    Sir Joseph Registered User

    you can also log it to a text file.
    tracert www.globalaffairs.org > c:\temp\trace.txt
     
  6. ethics

    ethics Pomp-Dumpster Staff Member

    Next question, how do I do this through a firewall?
     
  7. jamming

    jamming Banned

    You either have to authorize the program to bypass or remove the No-Ping Rules.
     
  8. Sir Joseph

    Sir Joseph Registered User

    It should still work. The first couple of numbers might be your computer followed by the IP of the router. I'm behind a firewall (through NAT) and I can still do this. If the site has a firewall it might be blocked at a certain point.
     
  9. ethics

    ethics Pomp-Dumpster Staff Member

    I get three hops before it stops. Forum is up but according to tracert, the site is down. Weird.
     
  10. jamming

    jamming Banned

  11. ethics

    ethics Pomp-Dumpster Staff Member

    Excellent, seems to be working. Thanks. :)
     
  12. Advocat

    Advocat Viral Memes a Speciality Staff Member

    The forum's server may be set not to respond to ICMP requests (pings). Check with your ISP.
     
  13. ethics

    ethics Pomp-Dumpster Staff Member

    Thanks Advocat. I got the full report and actually saw where the bottle-neck is.

    The forum's server is in Houston, so I THINK, most of the people affected are on the east coast.
     
  14. mrRT

    mrRT Tech Mod

    Let me know if there is anything you need. I am way East Coast...NorthEast actually
     
  15. -Ken

    -Ken Guest

    We were down this morning 11/29 from the time I
    got up ~5:00AM until well after 7:00AM.

    I ran a Tracert to the IP with the following results:

    Tracing route to 66.227.76.55 over a maximum of 30 hops



    1 1 ms 1 ms 1 ms new-isp129.greenmountainaccess.net [65.19.87.129]

    2 21 ms 18 ms 19 ms new-isp1.greenmountainaccess.net [65.19.87.1]

    3 27 ms 26 ms 31 ms interfaces113.greenmountainaccess.net [65.19.95.113]

    4 33 ms 25 ms 25 ms richmond-1.greenmountainaccess.net [65.19.64.1]

    5 34 ms 36 ms 34 ms sl-gw14-nyc-1-0-1.sprintlink.net [144.228.178.57]

    6 34 ms 35 ms 41 ms sl-bb20-nyc-0-0.sprintlink.net [144.232.13.225]

    7 34 ms 34 ms 34 ms pos6-2.core1.NewYork1.Level3.net [209.244.160.153]

    8 34 ms 34 ms 44 ms ae0-54.mp2.NewYork1.Level3.net [64.159.17.98]

    9 * 78 ms 79 ms so-0-1-0.mp2.Houston1.Level3.net [209.247.11.166]

    10 81 ms 82 ms 95 ms gige9-1.hsipaccess1.Houston1.Level3.net [209.247.11.190]

    11 81 ms 94 ms 87 ms unknown.Level3.net [209.247.121.218]

    12 79 ms 78 ms 78 ms 66.7.180.134

    13 79 ms 77 ms 80 ms o0-2jp2.hou002bd02.yipes.com [66.7.143.182]

    14 80 ms 85 ms 81 ms o0-2bd2.hou003bd02.yipes.com [66.7.143.158]

    15 90 ms 79 ms 80 ms o5-3bd2.hou005ap01.yipes.com [66.7.143.54]

    16 86 ms 78 ms 79 ms summittrading.com [66.54.158.66]

    17 85 ms 88 ms 95 ms 66.227.76.55



    Trace complete.

    The report from MyVitalAgent looks like this:

    Application Name: Web
    Your attempt to connect to port 80 on the server at 66.227.76.55 failed.

    The server appears to be unavailable at the moment. This condition may be caused by a network problem or firewall between you and the server. First, make sure that you are trying to contact the right server and try again. If this condition persists, wait a short while and then try again.

    Hope this helps.
     
  16. ethics

    ethics Pomp-Dumpster Staff Member

    Hi Leon,
    Sorry for the downtime.I was making some changes for the server's web
    server and it caused the problem.
    Regards
    Lijoe
     

Share This Page