Solved

Reading a Tracert Report

Posted on 2001-06-18
6
873 Views
Last Modified: 2012-05-04
I'm only asking in this area cuz I'm figuring folks here have deepest expertise regarding internet connectivity issues.

I'm running a dedicated Win2K box hosted by a Web Service Provider. I've had a couple clients who have experienced extreme lag lately and have asked them for a tracert. (below).

I don't know how to read tracert reports well enough to be 100% certain that I'm getting reliable information from the folks that host my site...though I have no outstanding complaints about them...I just want verification of what I'm being told.

As they read this trace report they tell me the bottleneck is at AmeriTech.

Resolving DNS hostname www.TTSTRAIN.COM. Please wait...
_________________________________________________________
Trace Route (Results logged to file: SYS:\ETC\IPTRACE.LOG)
Max Hops: 30 Max Wait: 5 seconds Dest Port: 40001
From: 166.73.220.34 (HOSTNAME UNKNOWN)
To: 216.64.209.111 (www.TTSTRAIN.COM)
 
Hop          RTT       IPAddress
  1        2.000ms     64.108.239.225 (HOSTNAME UNKNOWN)
  2        5.009ms     206.141.192.121 (BAS0-0.CHICAGO.IL.AMERITECH.NET)
  3        6.000ms     206.141.192.230 (FA3-1-CORE0.CHICAGO.IL.AMERITECH.NET)
  4     3960.006ms     127.0.0.1 (LOOPBACK)
  5       65.000ms     216.64.209.111 (www.TTSTRAIN.COM)
 

The thing that looks a like strange to me is that I'm used to seeing the last hop or two as internal to my provider...inside thier domain mask (i'm betting I'm displaying a fair bit of ignorance with my termonology.) Here's the end of a tracert from my own connection:

17   200 ms   201 ms   200 ms  dcr02-g6-0.ekgv01.exodus.net [216.64.194.20]
18   260 ms   201 ms   200 ms  csr01-ve240.ekgv01.exodus.net [216.64.194.34]
19   210 ms   200 ms   201 ms  216.64.206.132
20   210 ms   190 ms   211 ms  216.64.209.111

I've never experienced the sort of lag that my client is...so the problem _probably _is not with my host...but I'd like to be 100% I'm doing everything I can.

thankx
--steve...
0
Comment
Question by:juststeve
6 Comments
 
LVL 17

Expert Comment

by:mikecr
Comment Utility
Line number 4 says 3960ms on Loopback? Is that correct? Someones routing isn't correct and this is why they are having problems. You should never see the loopback in a trace route unless someones routing is goofy!
0
 

Expert Comment

by:bbast
Comment Utility
I ran a tracert on the site from my location. There were no problem with the tracert. You should never see a loopback address in a tracert. It looks as if there was a routing table problem, but that it has now been cleared.
0
 

Author Comment

by:juststeve
Comment Utility
When I work backwards...sending a tracert from my server to the client's address I'm getting consistant and constant 'Request Timeouts' at:
[clip]
16   220 ms   220 ms   221 ms  193.ATM7-0.GW7.PHL1.ALTER.NET [152.63.39.61]
17   250 ms   281 ms   250 ms  fiserv-gw.customer.alter.net [157.130.51.62]
18     *        *        *     Request timed out.
[more clipped]


This is going on more than a week with this problem.

So it seems as though the original tracert from the client folded those timeouts into a loopback...for whatever reason. It appears my host is on the level and that we have to figure out how to shake the tree at 157.130.51.62. Yes?

thankx
--steve...
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 17

Expert Comment

by:mikecr
Comment Utility
Yes, if a route can't find it's destination sometimes Admins will send it to the loopback to keep it alive until it goes thru the routing table again until finally reaching it's destination. In this case it sounds like there is a bad route. I would go to them and have them correct this in their routing table. You also normally only see this when people start putting some static routes in the router. Static takes precedence over dynamically learned routes.
0
 

Author Comment

by:juststeve
Comment Utility
bbast...I'm curious about the phrase...'It looks as if there was a routing table problem, but that it has
now been cleared. '

Though you mention 'it looks as though the problem's been cleared' things are reporting to my tracert exactly as they've been for the duration of the problem.

any clarifications are much appreciated.

thankx
--steve...
0
 
LVL 79

Accepted Solution

by:
lrmoore earned 50 total points
Comment Utility
A router's address that it is known by, or it's "handle" if you will, is the highest address assigned to any interface -- unless there is a loopback address assigned. It looks like somebody goofed up and put a loopback interface on a router with the ip address of 127.0.0.1, the same as the loopback interface address on every PC in the world. It's no wonder the packet gets bounced back and forth in a traceroute, but should be OK otherwise...
Ping times to 216.64.209.111 are all <90 ms from me..

You will see in this trace "loopback0.core1.Atlanta...." One more pointer to someone setting that looback address to 127.0.0.1 -- big time no no on the router...

C:\WINNT>tracert 216.64.209.111

Tracing route to 216.64.209.111 over a maximum of 30 hops

  1    16 ms    15 ms   <10 ms  user-24-214-92-1.knology.net [24.214.92.1]
  2   <10 ms    15 ms    16 ms  24.214.0.150
  3    15 ms    16 ms    31 ms  24.214.0.21
  4    31 ms    32 ms    31 ms  216-248-128-93.deltacom.net [216.248.128.93]
  5    16 ms    31 ms    31 ms  10.4.1.9
  6    15 ms    32 ms    31 ms  pos3-1-hsa2.atl.level3.net [63.210.88.169]
  7    15 ms    32 ms    31 ms  loopback0.core1.Atlanta1.Level3.net [209.244.3.1
]
  8    16 ms    31 ms    31 ms  ibr01-p4-2.atln01.exodus.net [216.32.173.93]
  9    32 ms    31 ms    63 ms  bbr01-g6-0.atln01.exodus.net [216.35.162.19]
 10    78 ms    78 ms    94 ms  bbr02-p1-0.ftwo01.exodus.net [206.79.9.190]
 11    78 ms    79 ms    78 ms  bbr01-p6-0.dlls01.exodus.net [206.79.9.197]
 12    78 ms    94 ms    93 ms  bbr02-p3-0.ekgv01.exodus.net [206.79.9.54]
 13    78 ms    94 ms    78 ms  dcr02-g2-0.ekgv01.exodus.net [216.64.194.4]
 14    78 ms    94 ms    94 ms  csr01-ve240.ekgv01.exodus.net [216.64.194.34]
 15    78 ms    94 ms    94 ms  216.64.206.132
 16    78 ms   109 ms    94 ms  216.64.209.111

Trace complete.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Tired of waiting for your show or movie to load?  Are buffering issues a constant problem with your internet connection?  Check this article out to see if these simple adjustments are the solution for you.
In the world of WAN, QoS is a pretty important topic for most, if not all, networks. Some WAN technologies have QoS mechanisms built in, but others, such as some L2 WAN's, don't have QoS control in the provider cloud.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), 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…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), 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…

744 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

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now