GameTracker > Forum > General Help > Unable to connect teamspeak 3 and gametracker
Vultr.com - Instant Cloud Server Deployment
GAMETRACKER FORUMS
Forum Home > General Help > Unable to connect teamspeak 3 and gametracker
pahkillerPM
#1
Unable to connect teamspeak 3 and gametracker
Aug 13, 2012 5:02 AM
Joined: Dec 21, 2007
Posts: 12
Its been a while since this worked like more than 12 to 18 months ago
I am with hypernia and am assured that it is not blacklisted or blocked.

I have tried 3 times today but no success am I missing something?
help would be appreciated
burnPM
#2
Aug 13, 2012 10:24 AM
Joined: Sep 27, 2006
Posts: 10924
Hello,

Have you looked over http://www.gametracker.com/games/ts3/forum.php?thread=42258 again to make sure you have the permissions set up?
I am retired from GameTracker after 11 years and will not be responsive for support requests.

pahkillerPM
#3
Aug 13, 2012 6:12 PM
Joined: Dec 21, 2007
Posts: 12
burn wrote:
Hello,

Have you looked over http://www.gametracker.com/games/ts3/forum.php?thread=42258 again to make sure you have the permissions set up?


Hi yes I have permissions setup I believe I was told by my Teamspeak provider I may have queried too many times and got banned which makes no sense to me at all
would this be a possibility?
I have enabled telnet om my pc win7 but cant get past this am I entering it wrong
..... ex. telnet IPADDRESS QUERYPORT example 203.14.173.45:10093
I enter it like that and get nothing
Last edited by: pahkiller Aug 13, 2012 6:20 PM
burnPM
#4
Aug 13, 2012 7:10 PM
Joined: Sep 27, 2006
Posts: 10924
Hello,

I would recommend just skip down to the instructions for editing the permissions and double check. You can always try whitelisting the GameTracker IPs to see if your server accidentally banned the IPs.

You need to actually substitute your information, eg

telnet 203.14.173.45 10093

Or through the windows telnet client, as indicated:

open 203.14.173.45 10093

However, I am assuming 10093 is the join port and not the query port, which it should be, as I am not able to connect to it.
I am retired from GameTracker after 11 years and will not be responsive for support requests.

pahkillerPM
#5
Aug 13, 2012 10:13 PM
Joined: Dec 21, 2007
Posts: 12
burn wrote:
Hello,

I would recommend just skip down to the instructions for editing the permissions and double check. You can always try whitelisting the GameTracker IPs to see if your server accidentally banned the IPs.

You need to actually substitute your information, eg

telnet 203.14.173.45 10093

Or through the windows telnet client, as indicated:

open 203.14.173.45 10093

However, I am assuming 10093 is the join port and not the query port, which it should be, as I am not able to connect to it.

ok the ip is 203.14.173.58 the port 10093
burnPM
#6
Aug 13, 2012 10:21 PM
Joined: Sep 27, 2006
Posts: 10924
Hello,

I cannot telnet that server on that query port. Please contact your provider to open that query port in the firewall for you.
I am retired from GameTracker after 11 years and will not be responsive for support requests.

pahkillerPM
#7
Aug 14, 2012 4:06 AM
Joined: Dec 21, 2007
Posts: 12
burn wrote:
Hello,

I cannot telnet that server on that query port. Please contact your provider to open that query port in the firewall for you.


They said it is'
burnPM
#8
Aug 14, 2012 10:40 AM
Joined: Sep 27, 2006
Posts: 10924
pahkiller wrote:
burn wrote:
Hello,

I cannot telnet that server on that query port. Please contact your provider to open that query port in the firewall for you.


They said it is'


Hello,

No TS3 server can be scanned on 10093. Both you and them can easily confirm that. However, if you missed in one of my earlier replies, please see below:

burn wrote:
However, I am assuming 10093 is the join port and not the query port


Please enter the QUERY PORT as the QUERY PORT and the JOIN PORT as the JOIN PORT. I would recommend linking your server provider to this thread for you. Hopefully they will be able to add the server with the correct information and/or update the permissions for you.
I am retired from GameTracker after 11 years and will not be responsive for support requests.