Hi,

We would like our TS3 server to be visible for GameTracker to query. But currently there seems to be something blocking this.

I know there is a guide here on how to open teamspeak for GT query. However, I don't have telnet access to the server, and I have absolutely no idea of what the telnet commands do.

We asked Art Of War Central, who hosts our gameservers and teamspeak, to open up for this with reference to the guide, but they refuse to do so, claiming that if they did, it would impose a risk to the server.

They ask for a specific IP to open up for queries, but I understand from the GameTracker FAQ that queries are done from a number of IPs, and that is therefore not the right way to do it.

It surprises me though, that GT would recommend doing stuff to the server that makes it vulnerable. Assumingly AOWC are professionals who knows what they are talking about.

What do other people do? Should I just accept that TS3 can not be opened for GameTracker queries while still being safe?

Thanks,
Spip

Can you ask them to supply a link to a teamspeak.com page that indicates there is a vulnerability in this? I have just done a search of the forums and only found a vulnerability in TS (so before TS3) but nothing else.

You are the first person who has run into this issue (who has posted about it at least) and even major providers like GameServers.com do not block telnet and haven't run into issues.

Hi Burn,

Thanks for looking into this. I asked AOWC for a reference, and this is the answer:

"No no no.
I didn''t say that there was a risk opening teamspeak to gametracker.
What, you think teamspeak has a setting called BE_TOTALLY_OPEN_TO_GAMETRACKER? It''s not that specific.
If we open it for gametracker, we open it for EVERYTHING. EVERYONE."

Hi again,

I have an update on this. I had some time and energy to do a few experiments, and I found some surprising stuff:

It turns out that the TS3 server is already open for telnet commands. I tried to use your guide for using telnet to send commands to the server to investigate what is wrong. BTW: The "use port=joinport" does not work for our server. "use 1" worked better (the server instance).

It turned out to be a matter of the client rights not set correctly on the server for the guest group. I have admin access, so I just granted channellist and serverinfo rights to the guest group (and removed some other rights that we dont want our guests to have). And now it works.

Thanks!