Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 7 of 7
  1. #1
    Join Date
    December 2014
    Posts
    15

    Bad connection quality

    A user has a bad connection quality on a specified server, as it show Teamspeak 3 client, and a poor quality of voice. But without any packet loss to the server (server IP address in the WinMTR trace is 100% correct, it's possible to connect to this IP and port directly).
    On other TS server he has a good connection quality.

    What could be a problem?

    Does Teamspeak 3 client show connection quality from a current user, or average value from all users on a server?

    Name:  124-KOPIYfaad0.png
Views: 1819
Size:  51.3 KB

  2. #2
    Join Date
    November 2006
    Location
    Kent - UK
    Posts
    67
    Thats to do with your host, your connection to your VPS is poor.

    Double check If other users have the same packet loss (click the middle mouse button on someones name)

  3. #3
    Join Date
    December 2014
    Posts
    15
    Several other users experience the same issue. But other parts feels fine, without any problems.
    Should not traceroute show a packet loss in this case?

  4. #4
    Join Date
    November 2006
    Location
    Kent - UK
    Posts
    67
    tracert might show it, but it's the quality of the connection, is it a VPS? Dedicated Server? or a home PC?

  5. #5
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,368
    MTR is usually ICMP. TeamSpeak is UDP. Routing might favor ICMP.

  6. #6
    Join Date
    December 2014
    Posts
    15
    It's a dedicated server. As I said, not all users have a bad connection quality. For instance, I have a good connection. The bad "connection quality" is non-permanent (but WinMTR trace is made in that period). Sometimes a connection for these users is ok.

    If ICMP traceroute does not show a packet loss, then how to locate a problem?

  7. #7
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,368
    Echo (also called ping) is an ICMP feature. Windows itself and MTR use ICMP echo. However, there is UDP tracert software. It sends UDP packets and hopes that routers complain about low TTL. That complaint is again ICMP packet. Might cause firewall issues, that's why the ICMP one is usually favored.
    Despite these issues, Linux uses UDP. You might try that on the server.

    You should check the direction and type of packet loss (displayed in TeamSpeak). Often, packetloss is the result of poor firewall settings, but that wouldn't be periodical.
    I wouldn't worry much but change the server's hoster. Did that a few times and now stick to the same datacenter for years.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Connection Lost & reconnect changes quality
    By Jomant in forum Android
    Replies: 2
    Last Post: June 24th, 2014, 06:25 AM
  2. Replies: 3
    Last Post: February 20th, 2014, 04:03 AM
  3. Replies: 1
    Last Post: January 29th, 2013, 08:43 AM
  4. Replies: 1
    Last Post: March 15th, 2010, 10:00 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •