I dont know if im allowed to post links so go to r4p3 (If you dont know this site ask Google) and search for Tea*Speak 3 License viewer and converterWhich tool? I'd like to know how to get it and paste it as you said
I dont know if im allowed to post links so go to r4p3 (If you dont know this site ask Google) and search for Tea*Speak 3 License viewer and converterWhich tool? I'd like to know how to get it and paste it as you 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 toolthanks a lot. yes we have protocol txt now. so what we will do next ?
I do getYou 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.
<20:25:24> Verbindung zum Server fehlgeschlagen
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.I do get
using the default keychains, not the NPL's.Code:<20:25:24> Verbindung zum Server fehlgeschlagen
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.I do get
using the default keychains, not the NPL's.Code:<20:25:24> Verbindung zum Server fehlgeschlagen
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
Same here.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.
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
Ging der 2 Verbindungsversuch dann?Same here.
Der 3. ging dann, ich habe einfach mal ein Thema dafür eröffnet, das hat hier ja eigl. nichts zu suchenGing der 2 Verbindungsversuch dann?
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
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
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% sureBecause 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
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. 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