Users unable to connect [Not a port forwarding / blocking issue]

[cbroughton]

People are unable to connect to my TeamSpeak 3 server running on port 9987. This machine has a static public IP assigned to it, and the TeamSpeak 3 server is being started manually.

Up until yesterday they were able to connect just fine, but now only I am able to connect (using either a local IP, localhost, or an IP through a VPN or ipKVM adapter.)

I have made contact with my server's ISP, and have checked IPTablesWIN and the following rules are in action:

(1.2.3.4 being synonymous of the server's IP)

PROTO  SOURCE         DEST           DIR  ACTION
UDP    1.2.3.4:9987   *:*            OUT  ALLOW
UDP    *:*            1.2.3.4:9987   IN   ALLOW

TCP    1.2.3.4:10011  *:*            OUT  ALLOW
TCP    *:*            1.2.3.4:10011  IN   ALLOW

TCP    1.2.3.4:30033  *:*            OUT  ALLOW
TCP    *:*            1.2.3.4:30033  IN   ALLOW

I have also tried marking this machine as an internet gateway (a rule for ALLOW *:* *:* TCP/UDP) and still no go. They were able to connect a day ago with no problems, and now they cannot.

Relevant TeamSpeak 3 Server Information:

 - Version: . . . . . 3.0.0-rc1 (Build: Unknown)
 - Operating System:. Microsoft Windows XP [Version 5.1.2600]
 - Soundcard Version: Not Applicable
 - DirectX Version: . Not Applicable
 - Error Message: . . Not Applicable

[cbroughton]

I've noticed that the TS3DNS seems to be the only bit of TeamSpeak 3 that has a proper centralized configuration file, whereas the main TeamSpeak 3 binary does not have any such ini configuration file, registry entry, or anything of the sort.

What if I wanted to specify a different path or filename for the sqlite database?
What if I wanted to slave-configure MySQL servers, or use MySQL at all?
What if (god forbid) I wanted to change the port my TeamSpeak 3 server runs on?

Am I supposed to rely on the sqlite database's configuration, and have TeamSpeak 3 server then load both sqlite.dll and mysql.dll to use a MySQL database? This seems like a waste of file handlers and system resources to me.

Relevant TeamSpeak 3 Server Information:

 - Version: . . . . . 3.0.0-rc1 (Build: Unknown)
 - Operating System:. Microsoft Windows XP [Version 5.1.2600]
 - Soundcard Version: Not Applicable
 - DirectX Version: . Not Applicable
 - Error Message: . . Not Applicable

[florian_fr40]

Hello

TeamSpeak 3 binary does not have any such ini configuration file, registry entry, or anything of the sort.

Please read the documentation : TeamSpeak 3 Server Quick Start.txt

[Tomas]

I've noticed that the TS3DNS seems to be the only bit of TeamSpeak 3 that has a proper centralized configuration file, whereas the main TeamSpeak 3 binary does not have any such ini configuration file, registry entry, or anything of the sort.

for rest of your post all is well known and documented. Also posted on this forum.
With registry option give me a break !! Thats not platform independent nor easy to go with!

As for centralized config file, you are right there ts3server binary doesn't have single file. But then again I just verified that teamspeak3 server actually close the opened ini files after startup. So no waste of resources there.

ts3 "shared libs" are not a big deal anyway