packet loss
9 posts
• Page 1 of 1
packet loss
I have been getting packet loss on ECGN since Tuesday evening. If I ping the ECGN # 1 several times roughly 1/3 of the time I get packet loss. This makes BF42 really frustrating to have all the connection problem pauses. I have called my ISP the past two days but we are playing phone tag.
Is there anything I can do I on my end to improve the situation? What causes packet loss? I have ADSL 1.5/384 with a Siscoe 678 router.
Thanks,
Jim
Is there anything I can do I on my end to improve the situation? What causes packet loss? I have ADSL 1.5/384 with a Siscoe 678 router.
Thanks,
Jim
Originally posted by Tommy Boy
How do you measure packet loss? Any good program recommendations?
I would like to know a good program too. I did about 10-15 ping 205.177.13.8 and ping sends 4 packets each test. I am losing 1-2 packets too often. In game it looks like deva vu. I am running along and suddely a warp back two steps or so. I imagine to those around me it looks like I freeze for a second every so often. It gets me killed.
Jim
- Fat Bastard
You can use ping -t 205.177.13.8 in the command line it will run til you stop it. (use ctrl C to stop it)
Pinging 205.177.13.8 with 32 bytes of data:
Reply from 205.177.13.8: bytes=32 time=17ms TTL=116
Reply from 205.177.13.8: bytes=32 time=19ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Reply from 205.177.13.8: bytes=32 time=23ms TTL=116
Reply from 205.177.13.8: bytes=32 time=27ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Reply from 205.177.13.8: bytes=32 time=25ms TTL=116
Reply from 205.177.13.8: bytes=32 time=15ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Reply from 205.177.13.8: bytes=32 time=17ms TTL=116
Reply from 205.177.13.8: bytes=32 time=18ms TTL=116
Reply from 205.177.13.8: bytes=32 time=14ms TTL=116
Reply from 205.177.13.8: bytes=32 time=24ms TTL=116
Reply from 205.177.13.8: bytes=32 time=34ms TTL=116
Reply from 205.177.13.8: bytes=32 time=17ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Reply from 205.177.13.8: bytes=32 time=25ms TTL=116
Reply from 205.177.13.8: bytes=32 time=25ms TTL=116
Reply from 205.177.13.8: bytes=32 time=20ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Ping statistics for 205.177.13.8:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 34ms, Average = 20ms
Once your done that
C:\DOCUME~1\DAD>tracert 205.177.13.8
Tracing route to ecgn20.ecgnetwork.com [205.177.13.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 29 ms 16 ms 45 ms ??.???.?.?
3 8 ms 41 ms 10 ms er-1-FE-00.cumb.md.charter.com [24.159.164.1]
4 15 ms 41 ms 17 ms 12.119.69.109
5 19 ms 41 ms 45 ms gbr6-p55.wswdc.ip.att.net [12.123.194.165]
6 68 ms 15 ms 15 ms tbr2-p013701.wswdc.ip.att.net [12.122.11.189]
7 17 ms 64 ms 17 ms ggr2-p390.wswdc.ip.att.net [12.123.9.85]
8 32 ms 13 ms 12 ms att-gw.dc.cw.net [192.205.32.46]
9 13 ms 16 ms 18 ms cpr2-pos-0-0.VirginiaEquinix.cw.net [206.24.238.
218]
10 18 ms 15 ms 52 ms bpr1-so-4-0-0.VirginiaEquinix.cw.net [206.24.227
.62]
11 18 ms 70 ms 33 ms beyond-the-network.VirginiaEquinix.cw.net [208.1
73.50.182]
12 32 ms 53 ms 15 ms ge6-1.colo01.ash01.pccwbtn.net [63.216.0.61]
13 25 ms 15 ms 49 ms ecgn20.ecgnetwork.com [205.177.13.8]
Trace complete.
Do both of those tests and post the results Jim makes it easier to narrow the problem down.
Pinging 205.177.13.8 with 32 bytes of data:
Reply from 205.177.13.8: bytes=32 time=17ms TTL=116
Reply from 205.177.13.8: bytes=32 time=19ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Reply from 205.177.13.8: bytes=32 time=23ms TTL=116
Reply from 205.177.13.8: bytes=32 time=27ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Reply from 205.177.13.8: bytes=32 time=25ms TTL=116
Reply from 205.177.13.8: bytes=32 time=15ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Reply from 205.177.13.8: bytes=32 time=17ms TTL=116
Reply from 205.177.13.8: bytes=32 time=18ms TTL=116
Reply from 205.177.13.8: bytes=32 time=14ms TTL=116
Reply from 205.177.13.8: bytes=32 time=24ms TTL=116
Reply from 205.177.13.8: bytes=32 time=34ms TTL=116
Reply from 205.177.13.8: bytes=32 time=17ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Reply from 205.177.13.8: bytes=32 time=25ms TTL=116
Reply from 205.177.13.8: bytes=32 time=25ms TTL=116
Reply from 205.177.13.8: bytes=32 time=20ms TTL=116
Reply from 205.177.13.8: bytes=32 time=16ms TTL=116
Ping statistics for 205.177.13.8:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 34ms, Average = 20ms
Once your done that
C:\DOCUME~1\DAD>tracert 205.177.13.8
Tracing route to ecgn20.ecgnetwork.com [205.177.13.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 29 ms 16 ms 45 ms ??.???.?.?
3 8 ms 41 ms 10 ms er-1-FE-00.cumb.md.charter.com [24.159.164.1]
4 15 ms 41 ms 17 ms 12.119.69.109
5 19 ms 41 ms 45 ms gbr6-p55.wswdc.ip.att.net [12.123.194.165]
6 68 ms 15 ms 15 ms tbr2-p013701.wswdc.ip.att.net [12.122.11.189]
7 17 ms 64 ms 17 ms ggr2-p390.wswdc.ip.att.net [12.123.9.85]
8 32 ms 13 ms 12 ms att-gw.dc.cw.net [192.205.32.46]
9 13 ms 16 ms 18 ms cpr2-pos-0-0.VirginiaEquinix.cw.net [206.24.238.
218]
10 18 ms 15 ms 52 ms bpr1-so-4-0-0.VirginiaEquinix.cw.net [206.24.227
.62]
11 18 ms 70 ms 33 ms beyond-the-network.VirginiaEquinix.cw.net [208.1
73.50.182]
12 32 ms 53 ms 15 ms ge6-1.colo01.ash01.pccwbtn.net [63.216.0.61]
13 25 ms 15 ms 49 ms ecgn20.ecgnetwork.com [205.177.13.8]
Trace complete.
Do both of those tests and post the results Jim makes it easier to narrow the problem down.
- RCinator
This'll get you 20 counts - plenty enough for a single test.
ping -n 20 http://www.ecgnetwork.com
Alternatively, if you want to email your isp, send it to a file like:
ping -n 20 http://www.ecgnetwork.com > C:\ping_ecgn.txt
Then you can just mail the file to your isp's tech.
ping -n 20 http://www.ecgnetwork.com
Alternatively, if you want to email your isp, send it to a file like:
ping -n 20 http://www.ecgnetwork.com > C:\ping_ecgn.txt
Then you can just mail the file to your isp's tech.
or just try this
http://www.ecgnetwork.com/ping.php
http://www.ecgnetwork.com/ping.php
I have not failed...I have just found 10,000 ways that don't work.
T.A.Edison
T.A.Edison
- JimmyTango
-
- Posts: 1774
- Joined: Tue Nov 05, 2002 5:17 pm
- Location: Land of the Shemales.
Or, use ASE, the only game browser to use, that will give you pocket loss % when looking at servers.
- Bullhead
Or, download one of two programs, both great...
1. VisualRoute @ http://www.visualware.com/personal/download/index.html#visualroute . They allow a 14 free trial, should be all you'll need. It'll give VERY good info.
2. simpler version of VR, free for use, called winMTR @ http://winmtr.sourceforge.net/ .
Jim...I sent you a PM.
1. VisualRoute @ http://www.visualware.com/personal/download/index.html#visualroute . They allow a 14 free trial, should be all you'll need. It'll give VERY good info.
2. simpler version of VR, free for use, called winMTR @ http://winmtr.sourceforge.net/ .
Jim...I sent you a PM.
- the_slog
Re: packet loss
Originally posted by Jim0322
Is there anything I can do I on my end to improve the situation? What causes packet loss? I have ADSL 1.5/384 with a Siscoe 678 router.
Thanks,
Jim
Packet Loss is usually not something that occurs between you and you ISP (although it can happen.) Much more often its a problem with some random router somewhere in the internet.
9 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 27 guests