OS and Software > Broadband Tweaks > [Tweak Test] Need help with Tweak

reply to catchme

Re: [Tweak Test] Need help with Tweak

i pinged bungie.net and after 4 "Request timed out", it had 4 packets sent and 0 received, with 100% loss...(this is with my firewall off)
so i tried various other gaming sites...
miniclip.com - 4 sent and 3 received
flyordie.com - 4 sent and 4 received
callofduty.com - 4 sent and 4 received (another xbox game)
assassinscreed.com - 4 sent 4 received (another xbox game)

i pinged bungie.net several times with the same result, if I'm getting 100% loss wouldn't that mean I can't play at all due to serious latency? I am playing it about every other day now, and the latency IS better, but still very unstable.

as for the Tracert...

Tracing route to bungie.net [65.59.234.97]
over a maximum of 30 hops:

1 - 1 ms 1 ms 1 ms dslrouter [192.168.200.1]
2 - 18 ms 19 ms 18 ms EV-ESR1-72-49-112-1.fuse.net [72.49.112.1]
3 - 20 ms 20 ms 20 ms 10ge2-2.ws-osr2.zoomtown.com [216.68.7.205]
4 - 20 ms 20 ms 20 ms 10ge1-4.sw2.core.fuse.net [216.68.7.204]
5 - 23 ms 22 ms 23 ms CINCINNATI.bar1.Cincinnati1.Level3.net [4.59.40.6]
6 - 20 ms 20 ms 19 ms xe-10-3-0.bar1.Cincinnati1.Level3.net [4.59.40.5
]
7 - 60 ms 28 ms 35 ms ae-10-10.ebr2.Chicago1.Level3.net [4.69.136.214]

8 - 28 ms 35 ms 35 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.132.41]

9 - 27 ms 26 ms 26 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
10 - 55 ms 52 ms 54 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61]
11 - 87 ms 91 ms 87 ms ae-2.ebr2.Seattle1.Level3.net [4.69.132.53]
12 - 77 ms 77 ms 77 ms ae-21-52.car1.Seattle1.Level3.net [4.68.105.34]

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.

doesn't look so good..

You have to be careful when reading pings and tracerts. Just because you get a "timed out" does not not say that there is packet loss.

Many routers and sites are set to not to respond to pings. Bungie.net is rejecting pings. That's why you have timed outs starting at hop 13. Up to hop 13 the tracert looks good.

The pings to the other game sites are OK. You dropped one packet to miniclip.com. When you run a ping test ping the site at least 20 times. Add -n 20 to the ping command.

You may just be a victim of routing by your ISP. I cannot see anything that sticks out as being an issue.
--
"You can observe a lot by watching". Yogi Berra

ok, well like i said it is better, it certainly hasn't been as bad as it was.

my ISP did say to get a router, do you think that would effect my latency? if so, do you recommend any? Lynksys is good I've heard.

Thanks for all your help! I really appreciate your patience working with me, I've learned some new things.

A router will not improve your packet loss and latency. What it will do is add another layer of protection between you and the evils of the Internet. Also, if you add another another PC or laptop it will be the conduit for your network.

I have had Linksys (now Cisco) routers and they worked just dandy. Other folks may have a different cut on it.

I hope your connection improves some more; good luck.
--
"You can observe a lot by watching". Yogi Berra