Ports are open on firewall, IP addresses for GT are whitelisted, Able to ping port for TS3 server. But GT still doesn't pick up on the server status.

ip: join.gcinema.net:9987 Query:10011

TS3
Welcome to the TeamSpeak 3 ServerQuery interface, type "help" for a list of comm
ands and "help <command>" for information on a specific command.
use port=9987
error id=1033 msg=server\sis\snot\srunning
use port=9987
error id=1033 msg=server\sis\snot\srunning

burn wrote:
TS3
Welcome to the TeamSpeak 3 ServerQuery interface, type "help" for a list of comm
ands and "help <command>" for information on a specific command.
use port=9987
error id=1033 msg=server\sis\snot\srunning
use port=9987
error id=1033 msg=server\sis\snot\srunning

I have been connected to the ts server since I posted...

and why are you trying to run serverquery on a connect port?

If you don't know how testing query permissions works via telnet I suggest reading the guide at the bottom of this post: http://www.gametracker.com/games/ts3/forum.php?thread=42258

burn wrote:
If you don't know how testing query permissions works via telnet I suggest reading the guide at the bottom of this post: http://www.gametracker.com/games/ts3/forum.php?thread=42258


I have validated that the whitelist is matching what is needed. Guest Server Query permissions have been validated.

Configuration wise (including firewall), has not changed. This happened out of the blue.

madman32395 wrote:
Configuration wise (including firewall), has not changed. This happened out of the blue.

I am having the same issue!
Any advice?

doggsofwar wrote:
madman32395 wrote:
Configuration wise (including firewall), has not changed. This happened out of the blue.

I am having the same issue!
Any advice?

Ok I fixed it... I am using FireDaemon Pro to run as a service. For some reason there were two TS servers running. Once I closed them down via Task Manager and restarted the service I was able to query again.

also make sure the query whitelist is up to date.

Thanks,

Mike.

doggsofwar wrote:
doggsofwar wrote:
madman32395 wrote:
Configuration wise (including firewall), has not changed. This happened out of the blue.

I am having the same issue!
Any advice?

Ok I fixed it... I am using FireDaemon Pro to run as a service. For some reason there were two TS servers running. Once I closed them down via Task Manager and restarted the service I was able to query again.

also make sure the query whitelist is up to date.

Thanks,

Mike.

That was weird. So with your fix, I decided to stroll through and see what processes were running... apparently TS soft crashed and relaunched but did not close its previous instance. So there were two teamspeak instances for one server. While it operated normally, it would not allow query and such; but allowed join.