OT: Tracer/routing question

Sat Jun 15 08:02:26 PDT 2013

Thanks for your reply, David.

I don't know what may lie between the last accessible IP 
(74.202.159.238) and my target IP (168.244.164.134). Isn't that the 
purpose behind (dynamic) routing? An end user doesn't need to know 
the route to their destination.

I assume a "real" OS == linux. I'll try tcptraceroute on my linux box 
when I get home Sunday evening.

When you say I need a baseline to go from. what do you mean?

The only real information I have is that I need to connect my browser 
to www.myloweslife.com and that attempt fails.  I tried tracert in 
order to try to determine what was going on behind the scenes. 
Obviously, that form of troubleshooting is (no longer) reasonable.

Do you have any suggestions on how to figure out why I may not be 
able to browse to that site? HR tells me there shouldn't be a problem 
and claims nobody else has connection problems. I'm stumped.

~Rick

At 6/14/2013 11:53 PM, you wrote:
>Hey Rick,
>
>This depends.  Do you know where the IP is you're trying to reach in 
>relation to the last IP shown?
>
>It is common today for clueless admins to block ping packets (M$ 
>uses ping vice UDP packets for tracing).  You might also be hitting 
>transit routes for the last hop or two.  These transit routes are 
>private IPs that can't respond back to you, but do pass packets 
>through (those that haven't reached their TTL/hop limit).
>
>So there may be no "block" to get past.  You really do need to have 
>a baseline to go from.  Try using a tcp trace (a la tcptraceroute), 
>they usually have less problems, but you'll need a real OS for that.
>
>Ciao,
>
>David A. Bandel
>
>
>On Fri, Jun 14, 2013 at 10:41 PM, Rick Bowers 
><<mailto:rwbowers at gmail.com>rwbowers at gmail.com> wrote:
>Off-topic question, but I know there is expertise here on this list.
>
>I've been trying to connect to 
><http://www.myloweslife.com>www.myloweslife.com but the site
>continually times out.  I've tried multiple times over the past week
>with no success.
>
>I tried running a tracert (Windows version of traceroute) several
>times and seem to always time out at the same point. (output below)
>
>I'm not sure exactly what this means, or who to contact to get past
>the "block".
>
>- Does this indicate a broken route? Down system?
>- Can I contact someone to help? Who? My ISP (Verizon
>FIOS)?  <http://twtelecom.net>twtelecom.net (Time Warner)?
>
>C:\>tracert <http://myloweslife.com>myloweslife.com
>
>Tracing route to <http://myloweslife.com>myloweslife.com [168.244.164.134]
>over a maximum of 30 hops:
>
>    1     2 ms     3 ms     3
>ms 
><http://Wireless_Broadband_Router.somewhereunknown.net>Wireless_Broadband_Router.somewhereunknown.net 
>[192.168.1.1]
>    2     5 ms     5 ms     5 
> ms 
> <http://L100.BSTNMA-VFTTP-77.verizon-gni.net>L100.BSTNMA-VFTTP-77.verizon-gni.net
>[98.110.224.1]
>    3     8 ms    10 ms     9
>ms 
><http://G0-14-2-6.BSTNMA-LCR-22.verizon-gni.net>G0-14-2-6.BSTNMA-LCR-22.verizon-gni.net 
>[130.81.217.110]
>    4     6 ms     5 ms     6 
> ms  <http://ae0-0.BOS-BB-RTR2.verizon-gni.net>ae0-0.BOS-BB-RTR2.verizon-gni.net
>[130.81.209.94]
>    5    22 ms    22 ms    22 
> ms 
> <http://0.xe-10-0-0.XL2.IAD8.ALTER.NET>0.xe-10-0-0.XL2.IAD8.ALTER.NE 
> T [152.63.7.61]
>    6    22 ms    22 ms    22 
> ms  <http://0.xe-11-1-0.GW12.IAD8.ALTER.NET>0.xe-11-1-0.GW12.IAD8.ALTER.NET
>[152.63.35.126]
>    7    23 ms    22 ms    24 
> ms  <http://twtelecom-gw.customer.alter.net>twtelecom-gw.customer.alter.net
>[152.179.50.186]
>    8    41 ms    40 ms    42 
> ms 
> <http://gso1-ar1-xe-2-0-0-0.us.twtelecom.net>gso1-ar1-xe-2-0-0-0.us.twtelecom.net
>[66.192.241.46]
>    9    42 ms    42 ms    43 
> ms 
> <http://74-202-159-238.static.twtelecom.net>74-202-159-238.static.twtelecom.net
>[74.202.159.238]
>   10     *        *        *     Request timed out.
>   11     *        *        *     Request timed out.
>   12     *        *        *     Request timed out.
>   13     *        *        *     Request timed out.
>   14     *        *        *     Request timed out.
>   15     *        *        *     Request timed out.
>   16     *        *        *     Request timed out.
>   17     *        *        *     Request timed out.
>   18     *        *        *     Request timed out.
>   19     *        *        *     Request timed out.
>   20     *        *        *     Request timed out.
>   21     *        *        *     Request timed out.
>   22     *        *        *     Request timed out.
>   23     *        *        *     Request timed out.
>   24     *        *        *     Request timed out.
>   25     *        *        *     Request timed out.
>   26     *        *        *     Request timed out.
>   27     *        *        *     Request timed out.
>   28     *        *        *     Request timed out.
>   29     *        *        *     Request timed out.
>   30     *        *        *     Request timed out.
>
>Trace complete.
>
>C:\>
>
>_______________________________________________
>Linux-users mailing list
><mailto:Linux-users at linux-sxs.org>Linux-users at linux-sxs.org
>http://mailman.celestial.com/mailman/listinfo/linux-users
>
>
>
>
>--
>Two things are infinite: the universe and human stupidity; and I'm 
>not sure about the the universe. -- Albert Einstein
>Visit my web page at: <http://david.bandel.us/>http://david.bandel.us/
>_______________________________________________
>Linux-users mailing list
>Linux-users at linux-sxs.org
>http://mailman.celestial.com/mailman/listinfo/linux-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/linux-users/attachments/20130615/14faa617/attachment.html 