Packet loss problem

February 22, 2011 at 19:00:44
Specs: Windows 7
Sometimes when I tracert yahoo.com it runs perfectly, or this happens.

1 <1 ms <1 ms <1 ms
2 * * * Request timed out.
3 * 44 ms 37 ms gig11-0-2.rochnybtn-rtr01.nyroc.rr.com [24.93.0.
113]
4 24 ms 30 ms 82 ms xe-3-2-0-0.vstlny11-rtr000.nyroc.rr.com [24.92.2
24.122]
5 22 ms 22 ms 43 ms ae1-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.208
]
6 54 ms 44 ms 35 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 65 ms 62 ms 52 ms ae-2-d170.msr2.re1.yahoo.com [216.115.108.69]
11 60 ms 63 ms 46 ms te-8-1.bas-a1.re1.yahoo.com [66.196.112.205]
12 61 ms 62 ms 50 ms ir1.fp.vip.re1.yahoo.com [69.147.125.65]

It's extremely annoying and it makes online gaming impossible for me.

Any fixes? I've had this problem for around 5 years.

A couple more:


Tracing route to yahoo.com [98.137.149.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 21 ms 30 ms 10 ms 10.123.48.1
3 15 ms 19 ms 9 ms gig11-0-2.rochnybtn-rtr01.nyroc.rr.com [24.93.0.
113]
4 18 ms 33 ms 62 ms xe-3-2-0-0.vstlny11-rtr000.nyroc.rr.com [24.92.2
24.122]
5 21 ms 18 ms 24 ms ae1-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.208
]
6 46 ms 27 ms 28 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 30 ms 28 ms 28 ms ae-0-0.cr0.nyc20.tbone.rr.com [66.109.6.27]
8 109 ms 114 ms 96 ms ae-4-0.cr0.sjc30.tbone.rr.com [66.109.6.10]
9 95 ms 93 ms 129 ms ae-0-0.pr0.sjc20.tbone.rr.com [66.109.6.139]
10 108 ms 149 ms 112 ms 66.109.9.179
11 104 ms 110 ms 98 ms ae-0-d141.msr1.sp1.yahoo.com [216.115.107.51]
12 102 ms 101 ms 98 ms et-18-25.fab1-1-gdc.sp2.yahoo.com [67.195.128.67
]
13 118 ms 98 ms 94 ms te-8-3.bas2-1-prd.sp2.yahoo.com [67.195.130.106]

14 139 ms 98 ms 101 ms ir1.fp.vip.sp2.yahoo.com [98.137.149.56]

Trace complete.


Tracing route to yahoo.com [98.137.149.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 62 ms 41 ms * 10.123.48.1
3 16 ms 21 ms 12 ms gig11-0-2.rochnybtn-rtr01.nyroc.rr.com [24.93.0.
113]
4 25 ms 12 ms 14 ms xe-3-2-0-0.vstlny11-rtr000.nyroc.rr.com [24.92.2
24.122]
5 21 ms 30 ms 19 ms ae1-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.208
]
6 55 ms 52 ms 31 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 29 ms 44 ms 26 ms ae-0-0.cr0.nyc20.tbone.rr.com [66.109.6.27]
8 106 ms 108 ms 103 ms ae-4-0.cr0.sjc30.tbone.rr.com [66.109.6.10]
9 92 ms 98 ms 91 ms ae-0-0.pr0.sjc20.tbone.rr.com [66.109.6.139]
10 110 ms 95 ms 191 ms 66.109.9.179
11 144 ms 95 ms 94 ms ae-1-d141.msr1.sp1.yahoo.com [216.115.107.55]
12 103 ms 102 ms 104 ms et-18-25.fab1-1-gdc.sp2.yahoo.com [67.195.128.67
]
13 99 ms 98 ms 100 ms te-8-3.bas2-1-prd.sp2.yahoo.com [67.195.130.106]

14 95 ms 111 ms 107 ms ir1.fp.vip.sp2.yahoo.com [98.137.149.56]

Trace complete.

C:\Users\logibear2>tracert yahoo.com

Tracing route to yahoo.com [98.137.149.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 * * 28 ms 10.123.48.1
3 * * * Request timed out.
4 13 ms * 13 ms xe-3-2-0-0.vstlny11-rtr000.nyroc.rr.com [24.92.2
24.122]
5 31 ms 28 ms 29 ms ae1-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.208
]
6 40 ms 40 ms 29 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 40 ms 29 ms 42 ms ae-0-0.cr0.nyc20.tbone.rr.com [66.109.6.27]
8 100 ms 122 ms 129 ms ae-4-0.cr0.sjc30.tbone.rr.com [66.109.6.10]
9 * 94 ms * ae-0-0.pr0.sjc20.tbone.rr.com [66.109.6.139]
10 * 97 ms * 66.109.9.179
11 95 ms * 97 ms ae-0-d151.msr2.sp1.yahoo.com [216.115.107.75]
12 * * 111 ms et-18-25.fab1-1-gdc.sp2.yahoo.com [67.195.128.67
]
13 99 ms 96 ms 99 ms te-8-1.bas1-1-prd.sp2.yahoo.com [67.195.130.96]

14 * 98 ms 101 ms ir1.fp.vip.sp2.yahoo.com [98.137.149.56]

Trace complete.

Tracing route to yahoo.com [69.147.125.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms logibear2-PC.rochester.rr.com [192.168.2.1]
2 29 ms 38 ms 26 ms 10.123.48.1
3 41 ms 33 ms 28 ms gig11-0-2.rochnybtn-rtr01.nyroc.rr.com [24.93.0.
113]
4 14 ms 16 ms 22 ms xe-3-2-0-0.vstlny11-rtr000.nyroc.rr.com [24.92.2
24.122]
5 45 ms 52 ms 19 ms ae1-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.208
]
6 29 ms 39 ms 54 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 58 ms 61 ms 53 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
8 56 ms 61 ms 48 ms ae-1-0.pr0.dca20.tbone.rr.com [66.109.6.167]
9 55 ms 66 ms * 66.109.9.165
10 52 ms 48 ms 48 ms ae-1-d170.msr2.re1.yahoo.com [216.115.108.29]
11 52 ms 65 ms 64 ms te-9-4.bas-a2.re1.yahoo.com [66.196.112.203]
12 58 ms 55 ms 41 ms ir1.fp.vip.re1.yahoo.com [69.147.125.65]

Trace complete.

C:\Users\logibear2>tracert yahoo.com

Tracing route to yahoo.com [69.147.125.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms logibear2-PC.rochester.rr.com [192.168.2.1]
2 26 ms 26 ms 19 ms 10.123.48.1
3 31 ms 30 ms 33 ms gig11-0-2.rochnybtn-rtr01.nyroc.rr.com [24.93.0.
113]
4 65 ms * 64 ms xe-3-2-0-0.vstlny11-rtr000.nyroc.rr.com [24.92.2
24.122]
5 37 ms 27 ms 25 ms ae1-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.208
]
6 42 ms 59 ms 33 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 48 ms 85 ms 42 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
8 49 ms 77 ms 69 ms ae-1-0.pr0.dca20.tbone.rr.com [66.109.6.167]
9 49 ms 50 ms 45 ms 66.109.9.165
10 60 ms 46 ms 48 ms ae-1-d170.msr2.re1.yahoo.com [216.115.108.29]
11 60 ms 62 ms 56 ms te-9-4.bas-a2.re1.yahoo.com [66.196.112.203]
12 40 ms 49 ms 46 ms ir1.fp.vip.re1.yahoo.com [69.147.125.65]

Trace complete.

I've asked this before but never got a helpful answer.


See More: Packet loss problem

Report •


#1
February 23, 2011 at 00:53:39
The route you computer takes, to trace to yahoo.com isn't always the same!!!
Take a look at your tracert protocol, you've posted, where you get a time out at the 7th, 8th and 9th position.
Then compare all the 7th, 8th and 9th ip addresses listed there.
They differ. This happens, if there is a problem, a corrupt router, cable or huge traffic.
This routing system is a self learning system.
If a router is not accessable for an amount of time, the routers in it's environment will realize it, and the will use another router, to connect you to your destination.

Think about you are driving with your car and there was a crash on the road, you,re normally driving. In such case, you may have to use an alternative router, to get to your destination.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#2
February 23, 2011 at 17:22:06
So how do I fix that?

Report •

#3
February 23, 2011 at 18:16:23
You don't. This is beyond your control. Like I said before you need to share this with your isp and perhaps they can submit a complaint to get this fixed.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
February 24, 2011 at 00:10:53
This happens all day in the internet and isn't really a problem because, it takes some time, and another route will be chosen, to get to the requested destination.

Choose another destination, e.g. microsoft.com or www.microsoft.com and you'll see, that you can't trace the whole route, but you can surf the website of www.microsoft.com.

This happens, because some gateways and routers do not reply to the ICMP types, that are necessary to trace the route to a destination and therefore, you get timeouts.

Destinations like google.com will work completely.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •


Ask Question