• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Completed 3.2.0 Teaspeaks

Status
Not open for further replies.
U

unsernetz

Active member
sezing said:
thanks a lot. yes we have protocol txt now. so what we will do next ?
Click to expand...
Replace the chain, root_key_prv, root_key_pbl, root_prv_index with the Data from the Converter Tool. If you dont have a own Licence you can use the default from the tool
 
h1web

h1web

Well-known member
unsernetz said:
You dont need a NPL at all the Tool have the Keychain for the default TS License so you can use this and paste this keychain in the txt file. Then you can connect with a 3.2.0 Client and make unlimited Slots and Virtual Servers. Works good for me.
Click to expand...
I do get

Code: 
<20:25:24> Verbindung zum Server fehlgeschlagen
using the default keychains, not the NPL's.
 
X

xZarex

Member
h1web said:
I do get

Code: 
<20:25:24> Verbindung zum Server fehlgeschlagen
using the default keychains, not the NPL's.
Click to expand...
Ich nutze die selbe Methode, die funktioniert recht gut. Das einzige was ich festgestellt habe, ist dass ich manchmal bei den ersten 1-2 Verbindungsversuchen auch nur Fehlschläge habe. Jedoch bin ich mir nicht sicher ob das immer ist oder nur wenn man sehr schnell reconnected.
 
U

unsernetz

Active member
h1web said:
I do get

Code: 
<20:25:24> Verbindung zum Server fehlgeschlagen
using the default keychains, not the NPL's.
Click to expand...
Ich habe keine Probleme damit aber bei nem Freund funktioniert das ebenfalls nicht. Schau doch mal bitte in deinem TS Client Protokoll was du über Extra erreichst ob es noch eine genauere Beschreibung gibt warum die Verbindung fehlgeschlagen ist. Wenn du dort nichts findest schaue doch mal im Teaspeak Log. Gerne kannst du mir beides auch per PN zukommen lassen und ich schaue mir das mal an.
 
h1web

h1web

Well-known member
29.07.2018 19:14:43 ClientUI Info Connect to server: xxxxxx
29.07.2018 19:14:43 ClientUI Info Trying to resolve xxxxxx
29.07.2018 19:14:43 TSDNS Info A/AAAA DNS resolve for possible TSDNS successful, "xxxxxx" =(h: xxxxxx p:0)
29.07.2018 19:14:43 TSDNS Info A/AAAA DNS resolve for possible TSDNS successful, "xxxxxx" =(h: xxxxxx p:0)
29.07.2018 19:14:43 TSDNS Info A/AAAA DNS resolve successful, "xxxxx" =(h: xxxxxx p:0)
29.07.2018 19:14:43 TSDNS Info SRV DNS resolve unsuccessful, "_ts3._udp.xxxxx" Domain name not found
29.07.2018 19:14:43 TSDNS Info SRV DNS resolve unsuccessful, "_tsdns._tcp.xxxxx" Domain name not found
29.07.2018 19:14:44 TSDNS Info TSDNS queried unsuccessfully xxxxx:41144
29.07.2018 19:14:44 TSDNS Info No TSDNS found
29.07.2018 19:14:45 TSDNS Info TSDNS queried unsuccessfully xxxxx:41144
29.07.2018 19:14:45 TSDNS Info No TSDNS found
29.07.2018 19:14:45 ClientUI Info Lookup finished: ip=xxxxx port=9987 query=xxxxx error=0
29.07.2018 19:14:45 ClientUI Info Resolve successful: xxxxx:9987
29.07.2018 19:14:45 ClientUI Info Initiating connection: xxxxx:9987
29.07.2018 19:14:45 SyncImpl Error Error getting myteamspeak id: invalid_data
29.07.2018 19:14:45 ClientUI Info Connect status: Connecting
29.07.2018 19:14:45 PktHandler Devel Puzzle solve time: 1
29.07.2018 19:14:51 PktHandler Info Cleaning up connection because of 5 resends of COMMAND packet
29.07.2018 19:14:51 ClientUI Info Connect status: Disconnected
29.07.2018 19:14:51 ClientUI Info Failed to connect to server, want autoreconnect = 0
 
U

unsernetz

Active member
Mhh sehe jetzt nur das er da mehrmals versucht zu senden. Steht den im Log vom Teaspeak Server etwas von deinem Verbindungsversuch? Vllt kommt die Anfrage gar nicht erst richtig an weil etwas dazwischen blockiert
 
U

unsernetz

Active member
Was mir gerade bei nem Test aufgefallen ist das ich den Fehler ebenfalls hatte nach einem Neustart des Teaspeak Servers beim 2 Versuch ging es aber.
 
X

xZarex

Member
unsernetz said:
Was mir gerade bei nem Test aufgefallen ist das ich den Fehler ebenfalls hatte nach einem Neustart des Teaspeak Servers beim 2 Versuch ging es aber.
Click to expand...
Same here.

Code: 
29.07.2018 19:23:31    ClientUI    Info    Autoreconnecting   
29.07.2018 19:23:31    ClientUI    Info    Connect to server: *SERVERNICKNAME*   
29.07.2018 19:23:31    ClientUI    Info    Trying to resolve *SERVERNICKNAME*   
29.07.2018 19:23:31    TSDNS    Info    Trying to resolve server name: *SERVERNICKNAME*   
29.07.2018 19:23:31    TSDNS    Info    Server name successfully resolved   
29.07.2018 19:23:31    TSDNS    Info    Lookup: *IPADRESS OF SRV*:1337, parse result: IPv4 *IPADRESS OF SRV* 1337   
29.07.2018 19:23:31    TSDNS    Info    Server name resolved to IPs   
29.07.2018 19:23:31    ClientUI    Info    Lookup finished: ip=*IPADRESS OF SRV* port=1337 query=*SERVERNICKNAME* error=0   
29.07.2018 19:23:31    ClientUI    Info    Resolve successful: *IPADRESS OF SRV*:1337   
29.07.2018 19:23:31    ClientUI    Info    Initiating connection: *IPADRESS OF SRV*:1337   
29.07.2018 19:23:31    ClientUI    Info    Connect status: Connecting   
29.07.2018 19:23:31    PktHandler    Devel    Puzzle solve time: 1   
29.07.2018 19:23:37    PktHandler    Info    Cleaning up connection because of 5 resends of COMMAND packet   
29.07.2018 19:23:37    ClientUI    Info    Connect status: Disconnected   
29.07.2018 19:23:37    ClientUI    Info    Failed to connect to server, want autoreconnect = 1
 
h1web

h1web

Well-known member
Auch nach ~15 Reconnects kein Erfolg.
Bin quasi mit dem Beta 3.2.0 Client noch NIE auf dem experimental TeaSpeak Server gewesen.
 
D

DikkatDeli

New member
unsernetz said:
Replace the chain, root_key_prv, root_key_pbl, root_prv_index with the Data from the Converter Tool. If you dont have a own Licence you can use the default from the tool
Click to expand...

thanks alot. i found it. but i dont have own NPL license . How can i create a chain, root_key_prv, root_key_pbl, root_prv_index for 512 slots.
 
U

unsernetz

Active member
Because Teaspeak has no Slot and Server Limit u can use the Standard License from the Tool. But then the Tea*Speak Client says No Licence and that is dangerous when you use 512 Slots with no Licence. But when nobody report you then your safe i think
 
D

DikkatDeli

New member
unsernetz said:
Because Teaspeak has no Slot and Server Limit u can use the Standard License from the Tool. But then the Tea*Speak Client says No Licence and that is dangerous when you use 512 Slots with no Licence. But when nobody report you then your safe i think
Click to expand...

is Tea*Speak 3.2 client released ?
 
WolverinDEV

WolverinDEV

TeaSpeak Team
Staff member
Administrator
unsernetz said:
Because Teaspeak has no Slot and Server Limit u can use the Standard License from the Tool. But then the Tea*Speak Client says No Licence and that is dangerous when you use 512 Slots with no Licence. But when nobody report you then your safe i think
Click to expand...
Hmm well not 100% sure anymore. I just said that once, but I thought a little bit about that and I know that while the client process the blacklist it also sends the slots to Tea*Speak. So it could be may "dangerous" but I'm not 100% sure
 
U

unsernetz

Active member
WolverinDEV said:
. I just said that once, but I thought a little bit about that and I know that while the client process the blacklist it also sends the slots to Tea*Speak. So it could be may "dangerous" but I'm not 100% sure
Click to expand...
Because this i say its dangerous and only say i think its safe if nobody reports you. 100% safe is nothing. But on a Test IP i test it and there is no Blacklist so far with No Licence and 512 Slots. The Problem is only Tea*Speak knows why they ban a server and why not. If the Test IP got an Blacklist i will update this post
 
Status
Not open for further replies.