Teamspeak/vds problems.

[lancir]

Okay so i've been trying to add a teamspeak server onto our vps/vds and i am having problems.

I recently added the rules for the ports into the OS's Firewall but canyouseeme.org still cant see the port...is there any other steps i should do.

Also i cant get my teamspeak to bind to the port i want (6990) it keeps binding to port 0

[Edge100x]

Have you tested with the firewall turned off?

Where are you setting the port?

[lancir]

I am setting the port in the "Windows firewall and advanced security" and the firewall is currently off and i still cant see those ports...but it can see ports 21 and 27015

[.=QUACK=.Major.Pain]

We run TS3 on a windows VDS, and never had to do anything to allow ports.

[lancir]

can you plse tell me how? idk what going on

[.=QUACK=.Major.Pain]

We had another member set it up over a year ago, but I think he installed the files, and then you have to register with TS website to get a key to activate it and you have to place that key in a file. At least I think that was how.

This is from memory, but I might be way off.

[lancir]

Ohh no all the register is is he got you a most likely a non profit license...still need help

[Hot Carl]

Are you setting the port in your ts3server.ini? It should automatically set it to the default port but if you aren't it might be worth a shot.

Also have you looked in the Teamspeak logs to make sure the server is running? Sometimes they don't run even though you think they run, that is why I hate running TS on Windows.

Carl

[.=QUACK=.Major.Pain]

Also check your processes and see if it is running.
It may be running, but it's configured incorrectly and you just can't connect.

[Hot Carl]

Also check your processes and see if it is running.
It may be running, but it's configured incorrectly and you just can't connect.

Well he really can't configure it unless he is using the .ini like I spoke of, however if he is using the .ini and is having all the problems he isn't using the proper format in the .ini file.

On Windows it either works or doesn't, the beauty of the logs in Windows is it will tell him why. Under Linux it sits there like a bump on a log and uses a process as if it is doing something.

Carl