TheWiseGuy
Dog And Butterfly
Premium,MVM
join:2002-07-04
Yonkers, NY
| reply to Chaz70
Re: OOL connected but very slow to not working internet
The hops that time out completely are set not to respond to a tracert (a packet with a ttl of zero) and therefore will not respond in a trace. That really is not indicative of a problem.
The first trace showed no problems. The second trace did show 2 packets lost. Whether the problem was at the hops that did not respond or prior to those hops would require more traces. This can be done as UnnDunn  suggested by setting up a line monitor or with one of the utilities I suggested.
Still looking at the traces you posted neither would be consistent with the Internet not working. Since your problem is the Internet stops working, and a problem has been confirmed in the Direct Forum, I think that at this point the traces will not help as much as initially. Since they confirmed a problem in the Direct Forum I would think the problem is somewhat local to your area.
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
Chaz70
join:2002-09-24
Middlesex, NJ | Thanks TheWiseGuy. One of the techs that came to the house said he was going to ask his boss to have the line monitored, but of course I never heard anything from them again after that. |
|
Chaz70
join:2002-09-24
Middlesex, NJ
| reply to TheWiseGuy
TheWiseGuy:
The hops that time out completely are set not to respond to a tracert (a packet with a ttl of zero) and therefore will not respond in a trace. That really is not indicative of a problem.
I dont think thats true in this case. It COULD be but I dont believe it here.
Here is the same traces from my work ISP.
Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.201
2 21 ms 14 ms 4 ms ewr-edge-07.inet.qwest.net [63.229.57.181]
3 8 ms 5 ms 34 ms ewr-core-02.inet.qwest.net [205.171.17.53]
4 27 ms 20 ms 25 ms jfk-core-01.inet.qwest.net [67.14.5.90]
5 46 ms 49 ms 45 ms jfk-brdr-03.inet.qwest.net [205.171.30.2]
6 101 ms * 12 ms 63.146.27.42
7 * * * Request timed out.
8 151 ms 197 ms 230 ms if-2-0-0-457.core3.AEQ-Ashburn.as6453.net [209.58.27.129]
9 260 ms 261 ms 227 ms ix-14-2.core3.AEQ-Ashburn.as6453.net [63.243.149.110]
10 47 ms 73 ms 130 ms ae-6.pat1.dce.yahoo.com [216.115.102.172]
11 230 ms 218 ms 217 ms ae1-p150.msr2.re1.yahoo.com [216.115.108.21]
12 73 ms 94 ms 119 ms te-9-4.bas-a1.re1.yahoo.com [66.196.112.207]
13 117 ms 168 ms 241 ms f1.www.vip.re1.yahoo.com [69.147.76.15]
Trace complete.
Tracing route to vnsc-pri.sys.gtei.net [4.2.2.1]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.201
2 28 ms 41 ms 78 ms ewr-edge-07.inet.qwest.net [63.229.57.181]
3 192 ms 108 ms 95 ms ewr-core-02.inet.qwest.net [205.171.17.53]
4 26 ms 12 ms 11 ms ewr-brdr-03.inet.qwest.net [205.171.17.158]
5 18 ms 16 ms 6 ms ge-6-18.car4.sanjose1.level3.net [4.68.111.109]
6 13 ms 15 ms 11 ms ae-32-52.ebr2.newark1.level3.net [4.68.99.62]
7 7 ms 18 ms 18 ms ae-1-100.ebr1.newark1.level3.net [4.69.132.21]
8 46 ms 48 ms 48 ms ae-2-2.ebr1.newyork1.level3.net [4.69.132.97]
9 8 ms 18 ms 34 ms ae-61-61.csw1.newyork1.level3.net [4.69.134.66]
10 72 ms 70 ms 155 ms ge-2-0.core1.newyork1.level3.net [4.68.97.8]
11 16 ms 17 ms 13 ms vnsc-pri.sys.gtei.net [4.2.2.1]
Trace complete. |
|
TheWiseGuy
Dog And Butterfly
Premium,MVM
join:2002-07-04
Yonkers, NY
| The traces take different paths. OOL has routers that for everyone time out because they are set not to respond to a ttl=0. These normally are somewhere between hops 3-7. Here is my typical trace.
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
Chaz70
join:2002-09-24
Middlesex, NJ | Yeah. At work here some times I get a request timed out at a hop or 2 but trace it again and it shows. I think it is local network being busy.
Direct support said the hops showed a possible problem in my local area.... |
|
TheWiseGuy
Dog And Butterfly
Premium,MVM
join:2002-07-04
Yonkers, NY
| A tracert from work to a site will pass through very different pieces of equipment then a tracert from home to the same site. That is why it helps to figure out where the problem is occurring. Each piece of equipment can be configured differently. When you get 3 asterisks(time outs) consistently from a hop but the hops after it tend to respond, it almost always means the equipment forwarding the packet is configured not to respond to a trace.
A good read on traces, how they work and what they mean can be found at the link below.
»homepage.ntlworld.com/robin.d.h.···aceroute
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
