View Full Version : Packet loss
ChainsawUK
29/11/2007, 20:52
Ping statistics for 66.36.241.110:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 124ms, Maximum = 127ms, Average = 125ms
2 nights in a row this has been happening now and its impossible to play on game servers wtf is going on?
Its fine through the day ....it just seems to happen around 7pm onwards.
Is it just that server? Is everything else normal?
I've ran a ping from another ISP and there is a lot more packet loss - therefore the issue is unlikely to be on our network, and at their end.
Pinging 66.36.241.110 with 32 bytes of data:
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Request timed out.
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Request timed out.
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=90ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=91ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Request timed out.
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Request timed out.
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=98ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=89ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=87ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Reply from 66.36.241.110: bytes=32 time=88ms TTL=116
Ping statistics for 66.36.241.110:
Packets: Sent = 144, Received = 121, Lost = 23
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 98ms, Average = 88ms
Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms x.x.x.x
2 12 ms 14 ms 12 ms 87-x.x.x
3 12 ms 12 ms 12 ms 195.50.112.237
4 12 ms 16 ms 18 ms ae-32-52.ebr2.London1.Level3.net [4.68.116.62]
5 87 ms 90 ms 89 ms ae-4.ebr1.NewYork1.Level3.net [4.69.132.109]
6 82 ms 90 ms 89 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
7 90 ms 89 ms 90 ms ae-64-64.ebr4.NewYork1.Level3.net [4.69.134.113]
8 90 ms 89 ms 90 ms ae-3.ebr4.Washington1.Level3.net [4.69.132.93]
9 96 ms 89 ms 90 ms ae-74-74.csw2.Washington1.Level3.net [4.69.134.182]
10 86 ms 86 ms 87 ms ae-22-79.car2.Washington1.Level3.net [4.68.17.68]
11 88 ms 87 ms 87 ms ge6-2.core1.dca2.hopone.net [66.36.224.190]
12 * * * Request timed out.
13 88 ms 89 ms 88 ms sls-cb9p7.dca2.superb.net [66.36.241.110]
d3rang3d
29/11/2007, 21:02
I would guess as your playing on a US based server, connection there is fine until you jump across the pond, maybe 7pm ish is when all the American kids get online to play. Whats it like playing on a UK based server?
---------------------
NeoTrace Trace Version 3.25 Results
Target: 66.36.241.110
Date: 29/11/2007 (Thursday), 20:59:08
Nodes: 14
Node Data
Node Net Reg IP Address Location Node Name
14 1 1 66.36.241.110 WASHINGTON D.C. sls-cb9p7.dca2.superb.net
Packet Data
Node High Low Avg Tot Lost
14 139 139 139 1 0
Network Data
Network id#: 1
OrgName: HopOne Internet Corporation
OrgID: HOPO
Address: 3311 South 120th Place
City: Tukwila
StateProv: WA
PostalCode: 98168-5125
Country: US
ChainsawUK
29/11/2007, 21:18
C:\Documents and Settings\Kev>pathping 217.163.10.158
Tracing route to 217.163.10.158 over a maximum of 30 hops
0 chainsaw-a24c41 [192.168.1.5]
1 mygateway.ar7 [192.168.1.1]
2 elm.dsl.enta.net [87.127.229.34]
3 vlan4003.telehouse-east2.dsl.enta.net [87.127.229.33]
4 gi1-8.telehouse-east2.core.enta.net [62.249.192.125]
5 te4-4.telehouse-east.core.enta.net [87.127.236.97]
6 te5-1.telecity-hex.core.enta.net [87.127.236.102]
7 ldn-tch-i2-link.telia.net [213.248.84.109]
8 ldn-b2-link.telia.net [80.91.250.213]
9 ldn-bb2-link.telia.net [80.91.252.13]
10 ldn-b4-link.telia.net [80.91.254.22]
11 ge-6-22.car2.London1.Level3.net [4.68.111.181]
12 ge-11-2.ipcolo2.London1.Level3.net [4.68.116.170]
13 217.163.10.158
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 chainsaw-a24c41 [192.168.1.5]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% mygateway.ar7 [192.168.1.1]
0/ 100 = 0% |
2 27ms 0/ 100 = 0% 0/ 100 = 0% elm.dsl.enta.net [87.127.229.34]
0/ 100 = 0% |
3 28ms 0/ 100 = 0% 0/ 100 = 0% vlan4003.telehouse-east2.dsl.enta.
net [87.127.229.33]
0/ 100 = 0% |
4 35ms 0/ 100 = 0% 0/ 100 = 0% gi1-8.telehouse-east2.core.enta.ne
t [62.249.192.125]
0/ 100 = 0% |
5 39ms 0/ 100 = 0% 0/ 100 = 0% te4-4.telehouse-east.core.enta.net
[87.127.236.97]
0/ 100 = 0% |
6 32ms 0/ 100 = 0% 0/ 100 = 0% te5-1.telecity-hex.core.enta.net [
87.127.236.102]
0/ 100 = 0% |
7 32ms 1/ 100 = 1% 1/ 100 = 1% ldn-tch-i2-link.telia.net [213.248
.84.109]
0/ 100 = 0% |
8 34ms 0/ 100 = 0% 0/ 100 = 0% ldn-b2-link.telia.net [80.91.250.2
13]
0/ 100 = 0% |
9 35ms 0/ 100 = 0% 0/ 100 = 0% ldn-bb2-link.telia.net [80.91.252.
13]
0/ 100 = 0% |
10 39ms 0/ 100 = 0% 0/ 100 = 0% ldn-b4-link.telia.net [80.91.254.2
2]
0/ 100 = 0% |
11 44ms 1/ 100 = 1% 1/ 100 = 1% ge-6-22.car2.London1.Level3.net [4
.68.111.181]
0/ 100 = 0% |
12 34ms 0/ 100 = 0% 0/ 100 = 0% ge-11-2.ipcolo2.London1.Level3.net
[4.68.116.170]
0/ 100 = 0% |
13 34ms 0/ 100 = 0% 0/ 100 = 0% 217.163.10.158
Trace complete.
I will get some Pinging done now.
HERE IS my results
Ahh not a good idea im downloading. Give me a tick stop me downloads
Reply from 212.58.224.131: bytes=32 time=16ms TTL=120
Reply from 212.58.224.131: bytes=32 time=16ms TTL=120
Reply from 212.58.224.131: bytes=32 time=16ms TTL=120
Reply from 212.58.224.131: bytes=32 time=16ms TTL=120
Thats to BBC
Time to open downloads again
d3rang3d
29/11/2007, 21:29
That looks alot better, I traced it too...
NeoTrace Trace Version 3.25 Results
Target: 217.163.10.158
Date: 29/11/2007 (Thursday), 21:27:19
Nodes: 13
Node Data
Node Net Reg IP Address Location Node Name
13 1 - 217.163.10.158 Southwark
Packet Data
Node High Low Avg Tot Lost
13 15 15 15 1 0
Somberlain
29/11/2007, 21:37
Getting crazy packet loss playing on the US DAoC servers over the past 2-3days..never ever an issue before. Right now it's pretty much unplayable, frustrating as heck and the reason I came here looking for answers :/
Ping statistics for 206.112.64.6:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 164ms, Maximum = 184ms, Average = 166ms
d3rang3d
29/11/2007, 21:46
Probably problems over the pond then, not to do with ADSL24 here, not much you can do till they fix problems over there. I've been playing on UK and euro servers pretty much every day with no problems.
It's fine for me..
C:\Documents and Settings\Josh>ping 66.36.241.110
Pinging 66.36.241.110 with 32 bytes of data:
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Ping statistics for 66.36.241.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 97ms, Average = 96ms
C:\Documents and Settings\Josh>tracert 66.36.241.110
Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110]
over a maximum of 30 hops:
1 4 ms 3 ms <1 ms mygateway.ar7 [192.168.1.1]
2 19 ms 19 ms 18 ms chestnut.dsl.enta.net [84.45.242.68]
3 21 ms 18 ms 19 ms vlan4001.global-switch.dsl.enta.net [84.45.242.65]
4 18 ms 18 ms 18 ms gi3-8.telehouse-east.dsl.enta.net [84.45.242.50]
5 18 ms 18 ms 18 ms te5-2.telehouse-east.core.enta.net [62.249.192.121]
6 19 ms 19 ms 21 ms te5-1.telecity-hex.core.enta.net [87.127.236.102]
7 18 ms 20 ms 18 ms ldn-tch-i2-link.telia.net [213.248.84.109]
8 19 ms 19 ms 18 ms ldn-b2-link.telia.net [80.91.250.213]
9 22 ms 19 ms 20 ms ldn-bb2-link.telia.net [80.91.252.13]
10 19 ms 18 ms 20 ms ldn-b1-pos5-0.telia.net [213.248.74.14]
11 18 ms 20 ms 18 ms globalcrossing-ic-119628-ldn-b1.telia.net [213.248.104.78]
12 95 ms 94 ms 93 ms ge2-2.core2.dca2.hopone.net [66.36.224.170]
13 104 ms 105 ms * vl3.msfc1.distb2.dca2.hopone.net [66.36.224.245]
14 95 ms 94 ms 93 ms sls-cb9p7.dca2.superb.net [66.36.241.110]
Trace complete.
Somberlain
29/11/2007, 21:58
Yeah, not experiencing any loss to UK servers.
http://www.dslreports.com/routerwatch/ash-bb1-link.telia.net
^might have something to do with it in my case, dunno.
It's fine for me..
try a "ping -t 66.36.241.110" and you will probably see some requests timing out over a longer period :)
try a "ping -t 66.36.241.110" and you will probably see some requests timing out over a longer period :)
Erm... 0% packet loss, 147 packets as well... :p
C:\Documents and Settings\Josh>ping -t 66.36.241.110
Pinging 66.36.241.110 with 32 bytes of data:
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=125ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=105ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=98ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=104ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=98ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=98ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=96ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=95ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=97ms TTL=111
Reply from 66.36.241.110: bytes=32 time=93ms TTL=111
Reply from 66.36.241.110: bytes=32 time=94ms TTL=111
Ping statistics for 66.36.241.110:
Packets: Sent = 147, Received = 147, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 125ms, Average = 94ms
There have been various problems on hopone.net network over the past few days as has been mentioned elsewhere.
Obviously, only affects ISPs who use this route ---> linky (http://adsl24.co.uk/forum/showthread.php?t=3920)
Cheers
corris
Bassetts
30/11/2007, 11:59
Just a lil helper.
I find Winmtr (http://winmtr.sourceforge.net/) much more helpful when troubleshooting traffic loss across a route, as it displays packet loss across each hop on the route, so makes it nice and easy to see where the loss starts happening.
Example of output to 66.36.241.110
http://img151.imageshack.us/img151/7788/winmtrin9.gif
Hope you find this usefull
ChainsawUK
30/11/2007, 20:55
This is from UK servers not american and its happening again for the 3rd night in a row from 7pm onwards.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| mygateway.ar7 - 0 | 101 | 101 | 0 | 1 | 16 | 0 |
| elm.dsl.enta.net - 0 | 101 | 101 | 15 | 25 | 94 | 16 |
| vlan4003.telehouse-east2.dsl.enta.net - 1 | 101 | 100 | 15 | 25 | 78 | 31 |
| gi1-8.telehouse-east2.core.enta.net - 0 | 100 | 100 | 15 | 38 | 250 | 78 |
| te4-4.telehouse-east.core.enta.net - 0 | 100 | 100 | 15 | 41 | 235 | 47 |
| te5-1.telecity-hex.core.enta.net - 0 | 100 | 100 | 15 | 35 | 219 | 15 |
| ldn-tch-i2-link.telia.net - 0 | 100 | 100 | 15 | 32 | 188 | 16 |
| ldn-b2-link.telia.net - 1 | 100 | 99 | 31 | 37 | 94 | 31 |
| ldn-bb2-link.telia.net - 0 | 100 | 100 | 16 | 40 | 94 | 47 |
| ldn-b4-link.telia.net - 0 | 100 | 100 | 15 | 42 | 109 | 46 |
| ge-6-22.car2.London1.Level3.net - 0 | 100 | 100 | 16 | 49 | 203 | 94 |
| ge-10-0.ipcolo2.London1.Level3.net - 1 | 100 | 99 | 31 | 40 | 78 | 47 |
| 217.163.28.173 - 1 | 100 | 99 | 31 | 42 | 125 | 31 |
|________________________________________________| ______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
No one else is seeing this and there have been no calls/tickets to support so definitely an isolated issue. Any more information you can provide would be great.
I don't know if this is related but I've had numerous problems playing Halo 3 over the last few nights, losing connection with the games. However when I check my routers log there is no mention of 'loss of sync' or anything, but I can see the light on my router (Netgear DG834G) flashes orange when it happens. Could it be packet loss causing this? It's driving me mad....:(
If the light is flashing orange then the line has lost sync. This is normally a line issue, or something causing noise on the line. Tried the router in the BT test socket (and upgraded router firmware?)
If the light is flashing orange then the line has lost sync. This is normally a line issue, or something causing noise on the line. Tried the router in the BT test socket (and upgraded router firmware?)
The logs of my router don't mention any 'loss of syncronization' though, surely they would if it had? The firmware is the latest version (I checked last night), and I don't appear to have a test socket on my bt box.
Yeah, the log should show that but i've seen it not do so in the past. Flashing amber "i" light certainly indicates loss of connection to the exchange.
If there is no test socket, whats your normal socket/filter/extension setup?
I only have the one socket, which has an adsl filter on it, and then my phone and router connected. No other phones or sockets. This has been going on for quite a while now, and a I'm starting to lose the plot! Briefly this is the history:
1. Was with F2S on 8mb connection and losing sync once or twice a day, usually late evening.
2. Moved to ADSL24, and started getting 100-200 loss of syncs a day! Not losing the connection with ADSL24 though, my session logs on my account page confirmed this.
3. Spoke to tech support who reckoned it was an equipment problem, probably my router.
4. My old router was a 4 year old original DG834. Bought a new DG834G and had no problems for a couple of weeks.
5. Last week or so have been having one or two drops a day while playing online, usually late evening.
Please, for my sanity, help me sort this out!!
If it's my line then what can I do, do we need to get a BT engineer to look at it?
Here's the connection statistics for my router if that's any help...
Connection Speed 6528 kbps 448 kbps
Line Attenuation 46 db 12.5 db
Noise Margin 3 db 24 db
Edit: here's a speedtest too, I never really get speeds above 2.5mb which is disappoingting especially as I usually got 4.5-5.5mb with f2s.
http://www.speedtest.net/result/207776718.png (http://www.speedtest.net)
Loss of SYNC's are irrelevent of your ISP so these will happen whoever you are with at the time.
The noise margin is too low, it needs to be above 6 to stay reliable. If you have no test socket, ensure that all sockets (master/extension) only have wires 2 and 5 connected, and that all sockets are filters, and any unneccessary equipment unplugged.
Your speedtest at the moment will not be a true accurate as it's always lower at weekend due to more people being online. Testing at a weekday would show better
How do I improve the noise margin then? I have the old style grey twin wire coming into my house and the set up looks like this......
http://www.rthomas.adsl24.co.uk/tel1.jpg
http://www.rthomas.adsl24.co.uk/tel2.jpg
http://www.rthomas.adsl24.co.uk/tel3.jpg
http://www.rthomas.adsl24.co.uk/tel4.jpg
Now I've got this.............what the hell?
http://www.rthomas.adsl24.co.uk/statistics.jpg
Your setup is the best it cn be there - no extensions at all.
That high figure on the noise margin means it's gone below 0 - e.g. negative. Not a good sign, as the connection will be slow/intermittent and probably reconnect soon.
The problem with the Netgear routers is that they hold on for dea life, instead of re-syncing when it should do, to get the line back up to the normal 6dB noise margin. This is a good feature to some extent, but in cases when it goes into minus figures, surely it has to re-sync, - yet it doesn't.
The higher your Connection speed on the router - the lower the noise margin will be.
I'd suggest a new filter, and if that doesn't help, log a ticket with support for BT involvement.
That's the third filter I've tried, it was new with the router. I'll log a ticket with support tomorrow, thanks for your help.
[QUOTE=Pumpkin;43853]Now I've got this.............what the hell?
http://www.rthomas.adsl24.co.uk/statistics.jpg[/QUOT
I would suggest trying to reboot your ADSL/Router because your 6.8Mbps downstream speed was too fast for a 46db attenuation; probably that explained your modem's Stat was reporting -ve SNR margin. Like James said that your modem should have auto re-sync for such a crappy SNR but it did not. The "objective" of my suggested "reboot" is trying to forced BT Line card to LOWER your downstream speed to something more sensible, i.e. 6 or higher downstream SNR instead.
Spoke to ADSL24 support today who were very helpful. I told them the problems I'd been having and my noise margin being very low and they passed it to BT.
BT initially changed the port or something, which didn't have any effect, so I rang back support who got BT on the case again. This time they swapped and reset my card at the exchange and now my noise margin is 6db and my speedtest has rose from 2500kb to 4500kb!! The big test will be when I play online and hopefully won't get any more drops, but so far things are looking promising!
http://www.speedtest.net/result/209087874.png (http://www.speedtest.net)
My noise margin has dropped to around 2db again, I haven't tried playing online and seeing if my connection drops yet though.
Couple of questions though, firstly would I be better off changing to a 2mb fixed connection? Or would I have more success changing to a LLU provider for my broadband?
I'm not really interested in super fast speeds or anything, I just want a stable line.....:(
Well moving to LLU won't fix the line. Only the fact that LLU does not have IP profiles. The line will still be in the same state, as such.
Lowering to 2Mb fixed would give you more noise margin hence higher stability.
Hmm, I might do that then. I'll see how my connection is for the next week or so and if I'm still dropping out I'll switch I think.
I switched Interleaving from Auto to On and now my noise margin seems to be stable at about 10db. Is that good or bad??:confused:
smartybones
06/12/2007, 16:55
i belive that may just be coincidence....
the noise margin is a physical paramiter of the telephone line..... interleaving is a form of error correction of the transmition on the telephone line....
Yep, noise margin down to 0db again....:(
vBulletin® v3.8.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.