What is it with port 9987?

[DJFire_CFR]

Ive read through tons and tons of posts about port 9987...

And I am having this issue also...

Info:

Windows 7 64-bit
TS3 Server 64-bit 3.0.3
TS3 Client 64-bit 3.0.5

Ports: 10011, 30033, 9987

Now, ports 10011 and 30033 work just fine with no issues what-so-ever...

but port 9987 no matter what I do, where I put it, how I put it will not open what-so-ever... I have tried it on my main PC, my other PC, and my laptop. (all 3 different LAN ips, and ive tried them all)

I have them set as followed:



Now granted I can connect using the client on my own PC using "localhost" as the server address... (But thats a given) But can not connect using the WAN IP..

And Yes, I have tried setting up as DMZ, but that did nothing and changed nothing. I know all about routers and ports and yadda yadda yadda, As I have been running an internet radio station for the past 6 years and I have setup many DJs. As 2 ports are required to be open for certain things.

So going through all this stuff.. No matter what changes I make or try to do, port 9987 will not open for anything.

Is there ANY other way to change that port (9987) to something else that might be easier to get open using the Windows version of the TS Server?

I dont recall having this issue with TS2 server this much.... =\

(I did try doing this on Linux server that I have, but I was the only one that could connect, no one else could. So thats why I decided to try it on Windows instead... but just worse problems)

[SilentStorm]

You can use the Query Interface to change the Port of the VirtualServer while the instance is running if you already put considerable time setting up that server.

telnet localhost 11011
login serveradmin PASSWORD
use port=9987
serveredit virtualserver_port=44444
serverprocessstop
quit

and after that just start the server again.

Second Method:
or you can just delete the ts3server.sqlitedb in the Server directory and start the Server with the default_voice_port=44444 Parameter.

The latter will cause the Server to create the first Virtualserver on Port 44444 and any subsequent servers will use the next free port above that number, while the first option will just change the port of the existing server and any subsequent servers will be created on the next free port starting with 9987 again.



You could also do the first method and start the server with the default_voice_port parameter as mentioned in Method 2 to combine both methods and force the server to create any subsequent servers starting from the port you specified in the parameter.

[DJFire_CFR]

Well, I just don't understand it... Whats a good port to use ? seems no matter what one I set for it, it wont open... 10011 and 30033 open just fine... the voice port will not open at all... I don't get it....maybe I'll try it on linux again on my actual server, instead of windows.

--- Merged ---

So yeah, I guess im just going to give up and use something else... TS2 I never had any issues with on Windows (Or Linux) TS3 server has changed so much since back then, its almost as if you need to be an advanced programmer to do anything with it...

I tried doing it all over on a linux server... got it all uploaded, setup, etc.. even have a license in there... and its not even reading the license.. and its still only letting "me" connect.. no one else can connect... All they get is : "Error: Failed to connect to server" but it doesnt tell you "why" it failed to connect... So I cant even try to do anything because I dont know what its failing.

How come im able to connect but no one else can? (This is on a Dedicated server using Linux, not on my own network) Bu tim still able to connect, but no one else can.. So after about 6 hours of frustration, I think im just going to find something else.. its to much of a headache anymore.

--- Merged ---

Okay great, So I finnnnnnnnally figured out what the issue was, and now people can connect... However, its not "finding" the license key file that I have uploaded (before I started everything)... So now my issue is its just not seeing the license file... So I'll see if I can find that in the forums here.

--- Merged ---

Great, I found out the issue with the license key, and why it was not working correctly... So I think I have gotten everything fixed and working now... I hope anyways...

So my first issue was an IP Issue on my server.. As there is a "Main IP" for my server... and my site has its own IP.. Now what I found out was after trying to use my sites IP and/or domain name, It was not allowing others to connect (No I dont have shared hosting, I have my own dedicated server, im the only one on it) So instead of using my domain name or site IP, I had to use the actual 'server" IP itself.. (all that frustration because of 1 number... /sigh)


Now for the license issue. I used a gmail account to register for the license... and after reading a post I found on here... Which said about gmail. I "viewed" the file instead of downloading it, and "copy n pasted" the info into the licensekey.dat file.. restarted the "Teamspeak" server, and it finally read it... So (from what I read in another post, they are correct) The license key should be sent in a zip file instead of just a plain .dat file as "most" email systems are corrupting the file, and causes it to become .. eh.. "broken" so to speak.

So if anyone else has any "issues" with the license key using gmail, hotmail, aol, or such email systems like those... "View the file" don't download it... create a licensekey.dat file and paste it in there, and then upload it to your server.

Teamspeak is a great Voice program... But should be "toned" down a bit for those that are not "programming gods". Granted there is ALOT of people on here that know TS inside and out, but "newerish" people do not, and run into tons and tons of issues like this..

But I guess the ole saying goes "you get what you pay for" and when its free, its all on you!

[SilentStorm]

Glad to hear everything worked out for you.

You can force the Teamspeak Server to only use one of the however many IP Addresses you got by using commandline options. See the server_quickstart.txt inside the docs folder for a list and explanation of available parameters.