Teamspeak issues

[#1]

Hello all
Ok, heres the thing. I rent a TS server, have done for a while.
Until resently its performed very well, no issues.
Around about 2-3 weeks ago i had a vid on my webspace that was to popular and it forced by web access to be suspended or something, my traffic allowance for 24hs was 770MB over the allowed limit.
I got all this fixed up, contact PN, etc.
However, since around that time, my pings on games, and particularly TS have gone higher and the one server i realy need, the one i rent, i cant get on at all, it keeps timing out.
I'm not sure what it is but the TS provider says its my com or my ISP. They asked me to do a pin g and trace using CMD and send them the results, they still said it was me or the ISP after.
So, heres my results, i dont really follow what they mean, the first one i kind of get and the ping is fine i think. Can anyone help?

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
Pinging TS26.DARKSTARLLC.COM [78.129.193.3] with 32 bytes of data:
Reply from 78.129.193.3: bytes=32 time=55ms TTL=55
Reply from 78.129.193.3: bytes=32 time=80ms TTL=55
Reply from 78.129.193.3: bytes=32 time=53ms TTL=55
Reply from 78.129.193.3: bytes=32 time=65ms TTL=55
Ping statistics for 78.129.193.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 80ms, Average = 63ms

Tracing route to TS26.DARKSTARLLC.COM [78.129.193.3]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 52 ms 70 ms 54 ms lo0-homesurf.pcl-ag01.plus.net [195.166.128.28]
3 60 ms 52 ms 66 ms gi1-5-806.pcl-gw2.plus.net [84.92.5.69]
4 71 ms 209 ms 198 ms te2-1.pcl-gw01.plus.net [212.159.1.113]
5 63 ms 66 ms 54 ms te2-2.pte-gw1.plus.net [212.159.0.186]
6 62 ms 58 ms 70 ms ge0-1.lonap.lon.rapidswitch.com [193.203.5.86]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 53 ms 67 ms 52 ms 78.129.193.3
Trace complete.

[#2]

The server traces ok for me[png attached], just Rapidswitch is blocking ICMP's on its routers.
Have you taken a wireshark capture in TS yet? It could be a fault with PN's traffic management.

[#3]

I'd suggest running a short Wireshark capture whilst you're using Teamspeak and raise a ticket with it attached. Include a short description about the problem and the IP of the server in question too.

[#4]

I'll try that.
Also, after having a think... I am hardwired to my router. My girlfriend runs a laptop off a wirless connection off the same router. If she was busy on the wirless connection while i was doing my usual (TS open, xfire open, 2 eve clients open) would that increase network traffic enough to timeout my connection to some of the TS servers?

[#5]

I'll go for a tentative "no", unless she's torrenting at line-speed or otherwise saturating the line.
Teamspeak is pretty resilient to adverse network connection as it uses UDP.  This means you might get "patchy" chat but certainly not a complete inability to connect.
It might be worthwhile seeing if your IP has been auto-banned from the server.  Teamspeak can occasionally detect an "Excess Flood" situation from the client in times when there is a laggy connection to the server.  It usually applies an auto-ban of ~5mins but I have seen situations where it has applied a timed auto-ban which is never removed.
You should also be able to "reboot" the server from the Darkstar control panel (it's been a year or so since I've used Darkstar, preferring to host my own TS on a colo server now)
B.

[#6]

ah thanks for the tip, i'll keep checking it out and see how things go
thanks
merr

[#7]

Wiresharks done, ticket is in
just awaiting the results. kind of nifty that wireshark program, dont have a clue what its doing, but still nifty

[#8]

Can someone give whoever "Internal" is a nudge to check ticket 26712278
Internal is meant to check port additions, what ever that means

[#9]

Dave should have had a chance to have a look at your ticket by the end of his day (he finishes around half seven).

[#10]

Many thanks