Hello
last few weeks having a lot of problems with teamspeak, sound break up on both received voice and people complaining of break up from my end. Had this particular teamspeak for over a year on the same ip / port without problem and is used regularly by a bunch of friends.
I'm in nottingham
A friend whos on Virgin in Bristol is having identical issues, other people that share the Teamspeak on BT and various ADSL dont have the same issue.
Are Virgin now applying traffic shaping against Teamspeak ports, this particular teamspeak is on port 8823 & is there anything i can do about this , its very frustrating and kind of ruins the experience.
I do seem to get a number of timeouts and packet loss, as mentioned above friends not on Virgin are not getting the same issue which leads me to believe its not a problem at gameservers end.
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
ping ts52.gameservers.com
Pinging ts52.gameservers.com [66.55.131.14] with 32 bytes of data:
Reply from 66.55.131.14: bytes=32 time=113ms TTL=49
Ping statistics for 66.55.131.14:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 113ms, Average = 113ms
Control-C
^C
ping -t ts52.gameservers.com
Pinging ts52.gameservers.com [66.55.131.14] with 32 bytes of data:
Request timed out.
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=126ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=102ms TTL=49
Request timed out.
Reply from 66.55.131.14: bytes=32 time=106ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=101ms TTL=49
Reply from 66.55.131.14: bytes=32 time=95ms TTL=49
Reply from 66.55.131.14: bytes=32 time=107ms TTL=49
Reply from 66.55.131.14: bytes=32 time=103ms TTL=49
Reply from 66.55.131.14: bytes=32 time=94ms TTL=49
Reply from 66.55.131.14: bytes=32 time=94ms TTL=49
Ping statistics for 66.55.131.14:
Packets: Sent = 17, Received = 15, Lost = 2 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 94ms, Maximum = 126ms, Average = 99ms
Control-C
^C
tracert ts52.gameservers.com
Tracing route to ts52.gameservers.com [66.55.131.14]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 22 ms 7 ms 38 ms 10.225.56.1
3 12 ms 8 ms 47 ms nott-t2cam1-b-v153.network.virginmedia.net [80.4
.47.25]
4 18 ms 27 ms 7 ms nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
5 38 ms 30 ms 15 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
6 14 ms 11 ms 12 ms pop-bb-a-so-100-0.network.virginmedia.net [213.1
05.172.14]
7 19 ms 54 ms 19 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
8 19 ms 32 ms 51 ms xe-1-3-0.cr1.ams2.nl.nlayer.net [195.69.145.219]
9 28 ms 20 ms 21 ms xe-1-1-0.cr1.lhr1.uk.nlayer.net [69.22.142.33]
10 98 ms 93 ms 124 ms xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]
11 100 ms 93 ms 112 ms tge2-4.ar1.ewr1.us.nlayer.net [69.31.95.182]
12 123 ms 104 ms 92 ms as20473.tge2-2-105.ar1.ewr1.us.nlayer.net [69.31
.95.198]
13 96 ms 106 ms 94 ms p-tge1-4-cr2.ewr2.Choopa.net [64.237.32.46]
14 95 ms 105 ms 118 ms 66.55.131.14.choopa.net [66.55.131.14]
Trace complete.
tracert ts52.gameservers.com
Tracing route to ts52.gameservers.com [66.55.131.14]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 32 ms 9 ms 6 ms 10.225.56.1
3 15 ms 24 ms 10 ms nott-t2cam1-b-v153.network.virginmedia.net [80.4
.47.25]
4 8 ms 7 ms 20 ms nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
5 12 ms 42 ms 14 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
6 12 ms 23 ms 13 ms pop-bb-a-so-100-0.network.virginmedia.net [213.1
05.172.14]
7 20 ms 22 ms 24 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
8 24 ms 28 ms 30 ms xe-1-3-0.cr1.ams2.nl.nlayer.net [195.69.145.219]
9 23 ms 22 ms 22 ms xe-1-1-0.cr1.lhr1.uk.nlayer.net [69.22.142.33]
10 92 ms 101 ms 112 ms xe-2-2-0.cr1.nyc3.us.nlayer.net [69.22.142.9]
11 93 ms 94 ms 95 ms tge2-4.ar1.ewr1.us.nlayer.net [69.31.95.182]
12 144 ms 92 ms 93 ms as20473.tge2-2-105.ar1.ewr1.us.nlayer.net [69.31
.95.198]
13 122 ms 94 ms 104 ms p-tge1-4-cr2.ewr2.Choopa.net [64.237.32.46]
14 119 ms 98 ms 96 ms 66.55.131.14.choopa.net [66.55.131.14]
Trace complete.
Code:
ping -t www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=16ms TTL=117
Reply from 212.58.253.67: bytes=32 time=19ms TTL=117
Reply from 212.58.253.67: bytes=32 time=24ms TTL=117
Reply from 212.58.253.67: bytes=32 time=15ms TTL=117
Reply from 212.58.253.67: bytes=32 time=16ms TTL=117
Reply from 212.58.253.67: bytes=32 time=24ms TTL=117
Reply from 212.58.253.67: bytes=32 time=15ms TTL=117
Reply from 212.58.253.67: bytes=32 time=42ms TTL=117
Reply from 212.58.253.67: bytes=32 time=20ms TTL=117
Reply from 212.58.253.67: bytes=32 time=15ms TTL=117
Reply from 212.58.253.67: bytes=32 time=15ms TTL=117
Reply from 212.58.253.67: bytes=32 time=23ms TTL=117
Ping statistics for 212.58.253.67:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 42ms, Average = 20ms
Control-C
WinXp 32
8800GT, Core2 Quad Q6600, 4 gig DDR3
Netgear WGT624 connected via cat5 / ethernet
Tried various router resets, connecting directly to modem, resetting mac address etc
Gaming and surfing seems reasonably normal , teamspeak poor even if only app running, dont believe its an application issue ..
have not tried contacting support yet, are the frontline able to deal with this kind of request and whats the best way to get the additional info to them ?