Guide TeamSpeak 3 Client Not Responding? See this thread!

[Nephilim]

Not a problem! I'm glad this helped you out!



That's correct. The entire server is experiencing issues. The problem outlined in this thread only affects Windows users. Since you're on a Mac, you're in the clear! :]

Well actually, I still can't connect to the server on my mac. When I connect to ts.mcgamer.net, I get to see this but I can't do anything at all.



And after approximately 20 seconds I get this message.

 

[JoelJCE]

Well actually, I still can't connect to the server on my mac. When I connect to ts.mcgamer.net, I get to see this but I can't do anything at all.



And after approximately 20 seconds I get this message.

Nephilim_04,

The issue is with the TeamSpeak server. The behaviour you (and many others) are experiencing is what happens when you attempt to connect to a server that is under a DDoS attack.

In the case of the original problem on this thread, a user's logs indicated that they connected successfully but their TeamSpeak client crashed. In your case, your client doesn't crash, but rather you're unable to establish a connection to begin with.

People who DDoS servers and other players often co-ordinate their attacks to disrupt certain events. As you've already pointed out, the Community Focus Group was scheduled for today; this is likely what they are trying to disrupt.

 

[Nephilim]

Nephilim_04,

The issue is with the TeamSpeak server. The behaviour you (and many others) are experiencing is what happens when you attempt to connect to a server which is under a DDoS attack.

In the case of the problem described in the original post on this thread, a user's logs indicate that they connected successfully but their TeamSpeak client crashes. In your case, your client does not crash, but rather you are unable to establish a connection to begin with.

People who DDoS servers and other players often co-ordinate their attacks to disrupt certain events. As you've already pointed out, the Community Focus Group was scheduled for today; this is likely what they are trying to disrupt.

Okay, I understand the situation now, thanks for the clarification!

PS: My apologies if I was a bit pushing about this topic, that would be since I am not 100% familiar yet with how Teamspeak works.

 

[JoelJCE]

PS: My apologies if I was a bit pushing about this topic, that would be since I am not 100% familiar yet with how Teamspeak works.

Not a problem at all! For everyone who currently uses TeamSpeak, we were all in the same situation when we started using it as well! :]

 

[HuntyB88]

I hope this helps a big group of people because Teamspeak can be very tricky at times.

 

[Alvalo]

Mine says

please help

 

[JoelJCE]

Mine saysView attachment 26226
please help

Hello Alvalo,

MCGamer uses something called an SRV record to point to the TeamSpeak server. You don't need to entirely understand this, but in a simplistic description it allows them to point the hostname "ts.mcgamer.net" to the actual TeamSpeak server IP (which is written as numbers). Resolving a hostname is the process of converting the hostname to the IP; changing the text form into numeric form.

So with all that in mind, what does this message say? Well, it says that it's unable to resolve the hostname; or as we learned earlier, your computer is unable to change the text form of the address (ts.mcgamer.net) into numeric form so that your computer can actually connect.

I'm going to ask you to follow these steps. Some steps may seem unnecessary, but they all contribute to diagnosing your problem:

1. Exit TeamSpeak completely. Reopen it and attempt to connect again.

2. Restart your computer and attempt to connect again.

3. Connect to the server with the direct IP: 69.160.45.3:20003 (this is the resolved numeric IP; both addresses point to the same server)

4. If issues persist, reply to this thread and I'll look into the problem further when I get on my desktop.

Kind Regards,
JoelJCE

 

[Alvalo]

Hello Alvalo,

MCGamer uses something called an SRV record to point to the TeamSpeak server. You don't need to entirely understand this, but in a simplistic description it allows them to point the hostname "ts.mcgamer.net" to the actual TeamSpeak server IP (which is written as numbers). Resolving a hostname is the process of converting the hostname to the IP; changing the text form into numeric form.

So with all that in mind, what does this message say? Well, it says that it's unable to resolve the hostname; or as we learned earlier, your computer is unable to change the text form of the address (ts.mcgamer.net) into numeric form so that your computer can actually connect.

I'm going to ask you to follow these steps. Some steps may seem unnecessary, but they all contribute to diagnosing your problem:

1. Exit TeamSpeak completely. Reopen it and attempt to connect again.

2. Restart your computer and attempt to connect again.

3. Connect to the server with the direct IP: 69.160.45.3:20003 (this is the resolved numeric IP; both addresses point to the same server)

4. If issues persist, reply to this thread and I'll look into the problem further when I get on my desktop.

Kind Regards,
JoelJCE

Thank you, it worked.

 

[JoelJCE]

UPDATE: The TeamSpeak Team has released a beta version of 3.0.15 which corrects the issues with BBCodes. Another alternative to the methods listed in this thread is to set yourself on the beta channel and update to 3.0.15. However, I will not provide a guide on how to do this; the process of updating to a beta client is a little more advanced and accurate support cannot always be provided if you're using a beta client (as some features do not work correctly).

For more information on the latest beta version and how to update your client, view this thread.

When the TeamSpeak Team releases the stable version of 3.0.15, I will request that a Staff member locks and unstickies this thread (as the problem will be corrected at the point). But until the new release this problem is still an ongoing issue.

 

[Twee]

Nice guide!

 

[Felipe]

great help thanks!

 

[JoelJCE]

UPDATE:
The TeamSpeak Team has released Client version 3.0.15 (the version that resolves the BBCode exploit) to the stable channel. The update must be triggered manually at this time, until a new Server version is released that will prompt this update.

To install version 3.0.15, go to Help -> Check for Update and you will begin the installation process.

At this time, I will request that a Moderator both locks and unstickies this thread (as this particular issue has been corrected, there is no foreseeable issues regarding this problem in the future). Should you need any TeamSpeak assistance, please do not hesistate to private message me or tag me in an open thread!