Losing packets in Teamspeak

kupitmen

Reputable
Aug 25, 2014
5
0
4,520
Hello, so the problem is that, for some reason, I get a huge packet loss in my friends Teamspeak server (about 60%). He is using multiplay.co.uk services. I'm from Lithuania so I get a bit higher ping than they do, but it's not the problem. If I try to join any other TS server, I get 0% packet loss. It isn't my router, neither the modem. Here are some pictures:
Traceroute to google.com:
vh2QdoS.png

Traceroute to Multiplay.co.uk:
DjcMqek.png

As you can see at the 8 hop, I get timed out, sometimes the Traceroute shows the IP, sometimes it doesn't. Any help is greatly appreciated :)
 
Solution


Changing your DNS server can help in the case of geo-location based cloud services because the DNS will give you a different IP address for the same name. In this case, of a specific IP address, changing your DNS server has absolutely nothing to do with your routing.
Your traceroute show no issues. Lets say hop 8 was totally broken...no power to the router...how would traffic ever get to hop 9 or hop10 which shows no issues and no loss.

All this means is the device is configured to not respond to traceroute. In general trace and ping are low priority data so if it is busy doing something important like passing actual traffic it may delay the response or randomly no respond.

A tracert that is bad show problems starting at some hop and then continuing to cause issues all the way to the end
 
The trace shows no problems. You would have to run this or one of the things like pathping until you get lucky and see something. Otherwise it is something with the application or server if it never shows up in the tracert

Realistically lets say you found that telia has a bad fiber going to level 3. Even if you were 100% sure that was the problem who would you even think to call.
 


Changing your DNS server can help in the case of geo-location based cloud services because the DNS will give you a different IP address for the same name. In this case, of a specific IP address, changing your DNS server has absolutely nothing to do with your routing.
 
Solution