Tutorial Connect with TS³-Clients [3.2.0+] to TeaSpeak servers

[mkll11one]

A new problem with client 3.2.2

What slots was the server?

 

[wotjokers]

100 slots, on version 3.2.1, the connection is no problem

 

[zocker]

100 slots, on version 3.2.1, the connection is no problem

? No Problem ? i cant join

 

[Awlok]

In 3.2.2 (beta) gives this error, when you try enter in some teamspeak crack.

 

[ThomasTailor93]

When you change your slots to 32 you can join.
TeamSpeak added a Slot check

So its not possible anymore even with TeaSpeak to crack slots.

Is it possible for TeaSpeak to fake / spoof slots? But let more then 32 Clients on Server.

 

[Gonçalo Santos]

How can I allow that old versions could connect on my server?

 

[mkll11one]

100 slots, on version 3.2.1, the connection is no problem

it's a problem.. TeamSpeak has added a slot check. try with 32 slots.

 

[ThomasTailor93]

it's a problem.. TeamSpeak has added a slot check. try with 32 slots.

Slot check got added on 3.2.2 [BETA]
With 3.2.1 he can connect without any problem.

 

[Shnepsey]

When I replace my protocol_key with the one that's posted here, I can't run my teaspeak server, it keeps crashing.
And without it, I can run the server but can't connect with my teamspeak client (3.2.1)....

 

[DJDosKiller]

When I replace my protocol_key with the one that's posted here, I can't run my teaspeak server, it keeps crashing.
And without it, I can run the server but can't connect with my teamspeak client (3.2.1)....

Delete all spaces inside protocol_key.txt

 

[ewenjo]

When I replace my protocol_key with the one that's posted here, I can't run my teaspeak server, it keeps crashing.
And without it, I can run the server but can't connect with my teamspeak client (3.2.1)....

1. Stop the server (if running now)
2. Delete the protocol_key.txt
3. Start the server and let it generate a new protocol_key.txt
4. Stop the server & delete the newly genereated protocol_key.txt
5. wget https://gist.githubusercontent.com/...2bb047f9717d0f78bd11acee867e/protocol_key.txt
6. Then start the server again

Credits: DrN00bish

 

[Shnepsey]

1. Stop the server (if running now)
2. Delete the protocol_key.txt
3. Start the server and let it generate a new protocol_key.txt
4. Stop the server & delete the newly genereated protocol_key.txt
5. wget https://gist.githubusercontent.com/...2bb047f9717d0f78bd11acee867e/protocol_key.txt
6. Then start the server again

Credits: DrN00bish

Thank you!
that worked!

 

[filip3712]

1. Stop the server (if running now)
2. Delete the protocol_key.txt
3. Start the server and let it generate a new protocol_key.txt
4. Stop the server & delete the newly genereated protocol_key.txt
5. wget https://gist.githubusercontent.com/...2bb047f9717d0f78bd11acee867e/protocol_key.txt
6. Then start the server again

Credits: DrN00bish

After 12 hours, it stopped working

Connection lost because server license can not be validated

 

[Herbalist]

Thanks for this tutorial helped me a lot !!!

 

[paulvilla]

Bug connections in servers.
This is 1.2.15-beta-12

 

[mkll11one]

Bug connections in servers

What server-version are you using? Do you have updated to: 1.2.15-beta-12

 

[paulvilla]

What server-version are you using? Do you have updated to: 1.2.15-beta-12

Yes

 

[dange]

Guys i did it but i have same problem:
<15:52:35> Trying to connect to server on x.x.x.x
<15:52:35> Disconnected from server (server version is too old for command)
What i have to do?

 

[mkll11one]

Guys i did it but i have same problem:
<15:52:35> Trying to connect to server on x.x.x.x
<15:52:35> Disconnected from server (server version is too old for command)
What i have to do?

You need to edit config.yml and set: experimental_31: 1

 

[CoC-Eu]

Connection lost because server license can not be validated