Community Forums Today's Posts     Member List     Archive    
Results 1 to 15 of 15

Hybrid View

  1. #1
    Join Date
    Dec 2003
    4858′0″N 107′0″E

    FAQ - TS 2.x Server

    This HowTo deals with the Installation/Configuration of a Teamspeak-Server under Linux.

    Thanks to Raymond for help to translate this howto!



    -- 1.0 - Prepare System
    -- 1.1 - Download/Install files
    -- 1.2 - Start Teamspeak
    -- 1.3 - WebInterface
    -- 1.4 - The server.ini
    -- 1.5 - The server.log
    -- 1.6 - The server.dbs
    -- 2.0 - Router Configuration
    -- 3.0 - Construct a Backup
    -- 4.0 - Install a Banner

    -- FAQ: (frequently asked questions) Official FAQ

    1.0 Prepare System
    Open a console or log in via SSH.

    Then, become Root with:

    First, you will need to build a new user, so you can later execute TeamSpeak as this user:

    useradd ts
    Now that you have built the new user "ts", you will need to construct a Home-Directory for the user with:

    mkdir /home/ts
    Now, assign a Home-Directory to the User "ts", in which he will possess all of the necessary rights for the execution of TeamSpeak:

    chown -R ts /home/ts
    The user now only requires a password to be able to log in via SSH:

    passwd ts
    Enter the password for ts.

    Switch to the user "ts" with:

    su ts
    Now, switch to the Home-Directory with the user:

    cd /home/ts

    1.1 Download/Install files
    Download TeamSpeak to your Computer:
    (Gentoo-Users can just enter "emerge teamspeak2-server-bin" in the
    console and then go on with point 1.2, if they want)


    (current links on the official homepage: The better that your internet connection is, the faster the file will be downloaded.
    After the download, unpack the archive with:

    tar -jxvf ts2_server_rc2_20201.tar.bz2
    (Note: Tab = automatic completion)

    The time that this process will take is dependant on the speed of your computer.

    1.2 Start Teamspeak
    Go into the directory that has just been unpacked with:

    cd tss2_rc2
    In this directory there is a startscript that you can use to start the service:

    ./teamspeak2-server_startscript start
    If the following appears, the server has been sucessfully started:

    TeamSpeak Server Daemon started with PID ****
    You can verify this with the following command:

    ./teamspeak2-server_startscript status
    More Commands:

    ./teamspeak2-server_startscript stop - Stops the server

    ./teamspeak2-server_startscript restart - Restarts the Server

    ./teamspeak2-server_startscript passwords - Gives you the Super-admin and Admin password

    You will need to use that last command for out next step:

    ./teamspeak2-server_startscript passwords
    The command, in the console, will give you the admin passwords. These passwords are randomly generated during the install process! They do not need to be changed.

    1.3 The WebInterface
    Now, you can log into the WebInterface in a browser with:




    The Interface is self-explanatory so I will not go into detail on how to use it.

    1.4 The server.ini

    Back to the shell/console:
    In the TeamSpeak-Directory you will find the server.ini file which can be opened with:

    mcedit server.ini
    If mcedit does not work, you will need to install the mc-editor.
    Threfore, here are the links:

    Mandrake 10.0:
    RedHat 9:
    SuSE 9.1:
    Debian: Just enter "apt-get install mc".
    Gentoo: Just enter "emerge mc".

    You can install the package with: "rpm -ivh PACKAGENAME" (Under Debian or Gentoo this step is not necessary anymore)

    You can find more links on


    [Main Config]
    BoundToIp1 - Values: through - standard value: empty - If the server possesses several IP-addresses, Teamspeak be assigned to an specific IP.
    ExternalIPDetection - Values: 0 or 1 - standard value: 1 - This function should stay at 1, so that the TeamSpeak-server will get the IP referring to the server by on its own.
    HTTPServer Port - Values: 1 through 65535 - standard value: 14534 - This is the port to the WebInterface of TeamSpeak.
    HTTPServer Enabled - Values: 0 or 1 - standard value: 1 - This function decides, if the WebInterface should be switched on or off.
    DateTimeFormat - Values: they can be any changed if you like - standard value: dd-mm-yyyy hh:nn:ss - Date and Time for Teamspeak.
    TCPQueryPort - Values: 1 through 65535 - standard value: 51234 - Determines the port for access to the server via Telnet.
    AllowedClientNameChars - Values: A-Z + special symbol - standard values: empty - The permitted letters/symbols in the
    nickname of the connecting client. (the next setting is more useful)
    DisAllowedClientNameChars - Values: A-Z + special symbol -
    standard values: ()[]{}
    - The letters/symbols which are not allowed in the nickname of the connecting client.

    MessageTypes - Values: ? - standard value: LMTALL - It's best if you don't change this setting.
    MessageDepths - Values: ? - standard value: LMDALL - It's best if you don't change this setting.

    These settings can be administrated comfortably in the WebInterface. (Global Settings).

    access_r - Values: 0 or 1 standard value: 0 - Logs the action registered (If a user registers or joins the server)
    access_u - Values: 0 or 1 standard value: 0 - Logs the action registered (If a person registers or joins the server)
    channel_registered - Values: 0 or 1 standard value: 0 - Logs the action registered channel (If a channel is registered or erased)
    channel_unregistered - Values: 0 or 1 standard value: 0 - Logs the action unregistered channel (If a unregistered channel is constructed)
    sa - Values: 0 or 1 standard value: 0 Logs the action ServerAdmin (If a server-admin joins the server or somebody gets server-admin or taken away from)
    chat - Values: 0 or 1 standard value: 0 - Logs the action Chat (If user/admin/registered-person talk via chat)
    kick_server - Values: 0 or 1 standard value: 0 - Logs the action ServerKick (If somebody is kicked from the server)
    kick_channel - Values: 0 or 1 standard value: 0 - Logs the action ChannelKick (If somebody is kicked from a channel)

    These settings can be administrated comfortably in the WebInterface (Global Settings).

    1.5 The server.log
    You will find the following in the server.log:

    Where the results of the log settings in the server.ini are saved.
    Changes in the configuration are saved. (Starting of the Server/Starting of a virtual server, etc.. )
    Possible occured mistakes are saved. (Useful for troubleshooting on your own or here in the forums!)

    1.6 The server.dbs
    In the server.dbs, all informations about the virtual servers are saved. (Channels, servernames, etc..)

    2.0 Router Configuration
    If you use a router in a LAN, you must carry out cofiguration-settings on the router, before other users can connect to your TeamSpeak-Server from outside of the LAN.
    You must connect with your internal IP (192.168.x.x), if you installed the server on your private network.

    It is very difficult to explain this as simple as possible, because there are countless different router-models. You also must think about this for yourself a little.
    Normally all routers have their own "homepage", where different settings can be manipulated.

    So we open the browser and enter (IP dependent on your network):


    If a window with a password-query appears, the username is usually:

    and the password:

    (Once again, this is dependant on make/model of the router. Consult your Owner's Manual.)

    If you are sure that you have entered the username and the password correctly, and the access is still denied => Read the manual of the Router.

    If the window doesn't appear check your computers network setting and use the IP address specified as the "Gateway".

    If the window still doesn't appear => read the manual of the Router.

    I assume that we are now on the start page of the "Router's Homepage". Please, do not change any setting, if you don't know what it means.
    As already mentioned, there are different models of routers , so you must search for "port-forwarding", "port-release", "virtual-servers", "ports" or similar things on the homepage by yourself.

    There should be at least 2 text-fields:
    Where the required port must be entered.
    Where your local IP-address (192.168.x.x) must be entered.

    TeamSpeak uses the following ports:

    8767 would be the UDP-standard-port. (This is the only port necessary to connect to the server from outside (Internet). If a new virtual server with the port 8768 is started that port must also be configured.)

    14534 would be the TCP-WebInterfaceport. (For Administration)

    51234 would be the TCP-Telnetport. (Professional)

    After the configuration of the ports that you want available to the internet, push "save", "commit" or similar buttons (otherwise the settings won't be saved!).

    3.0 Construct a Backup
    It is sometimes a good idea to make a backup (safety device) of the TeamSpeak-Server. Just in case of a takeover, hack, or any other kind of stupidity. It could be that you have simply lost everything. In this section we want to prevent that.

    There are many ways to construct a backup of files using scripts which require more linux knowledge. As a Beginner you can damage the system with these scripts if they are improperly implemented. So we will do it the simple way.

    The server.dbs (which contains the information for all servers, channels etc.) and the server.ini (which contains all information about the settings of the TeamSpeak-server) are what is important. Since we are lazy and don't want to copy the single files to another PC/Server, we will pack the two files into a .tar.gz-archive. To do this, go in your TeamSpeak-Directory and enter the following:

    tar -cvzf backup.tar.gz server.dbs server.ini
    Now, both files are in the archive.

    There are different possibilities to get the archive from the server.
    Let's take one of the easiest:
    The program is actually self-explanatory. As with a SSH-client, you just log in. From there you can just download the file on the local PC like you do in windows-explorer.

    And that's that!

    When we want to work with the backup'd files again we copy the archive, with WinSCP, back from the PC to the Server (into the TeamSpeak-Directory) and enter the following:

    tar -zxvf backup.tar.gz

    4.0 Install a Banner
    With the final release of TeamSpeak 2, it is possible to install a banner in TeamSpeak. This is in the area in the client where the channel information is displayed. At the moment it is, unfotunately, only possible to configure a banner for the whole server and not for the individual virtual ones. Another problem: If the client changes the size of his window, the banner is changed in the same proportions.

    IMPORTANT: The Banner must be in .jpg format, or it won't be displayed!

    We must log in with the SSH-Client as usual, go into the TeamSpeak-Directory and write:

    mcedit server.ini
    (or other editors for example: nano, pico, vi...) to open the configuration file of TeamSpeak.

    There we find the entry:

    which you will need to change in the following way:

    With this setting the banner will be linked with the indicated URL. The user will be redirected to, when they clicks on the banner. If you don't want that, then just leave this setting blank.

    At the bottom in the server.ini we enter the following:

    GFX URL=
    As you can see there is the absolute path to the banner now. When you have finished using the mceditor press "F10" to exit. (You will be prompted to save. Don't forget to save!)

    Now you must restart the TeamSpeak-Server, so that your settings are seen:

    ./teamspeak2-server_startscript restart
    (The banner will be saved in the imagecache.ini at the client. Unfortunately, the banner will not be updated, if you change the banner at a later time. The user will most likely still have the banner until he formats his computer. Only by deleting the imagecache.ini (the file
    is hidden - C:\documents and settings\yourname\applicationfiles\teamspeak2\) will the banner be updated again.
    Last edited by Michael; 22-02-2005 at 22:24.

  2. #2
    Join Date
    Dec 2003
    4858′0″N 107′0″E
    No feedback?

  3. #3
    Join Date
    Nov 2004
    Portland, OR
    OK I got Permission denied from your instructions...

    [ts@secure1 tss2_rc2]$ ./teamspeak2-server_startscript start
    /bin/bash: /root/.bashrc: Permission denied
    starting the teamspeak2 server
    TeamSpeak Server Daemon started with PID 30127
    [ts@secure1 tss2_rc2]$
    [ts@secure1 tss2_rc2]$ ./teamspeak2-server_startscript status
    /bin/bash: /root/.bashrc: Permission denied
    the server seems to be running
    [ts@secure1 tss2_rc2]$ ./teamspeak2-server_startscript password
    /bin/bash: /root/.bashrc: Permission denied
    Usage: ./teamspeak2-server_startscript {start|stop|restart|status|passwords}
    [ts@secure1 tss2_rc2]$ ./teamspeak2-server_startscript passwords
    /bin/bash: /root/.bashrc: Permission denied
    Following passwords were generated on 06-01-05 09:17:03
    superadmin = "X"
    admin = "X"

    Also how to set the program to start on server reboot?



  4. #4
    Join Date
    Oct 2003
    Another way to get MC, should work for all *nixes

    gunzip mc-4.6.0.tar.gz 
    tar -xf mc-4.6.0.tar 
    mv mc-4.6.0 /usr/src
    cd /usr/src/mc-4.6.0/
    make install
    Your mileage may vary, it works for me.

    If mcedit doesn't work, nano and/or pico shold do the trick as well.

  5. #5
    Join Date
    May 2005
    Huntsville, Ala.
    Quote Originally Posted by Michael
    No feedback?
    This worked fine for me.. thanks for putting it together.

  6. #6
    Join Date
    Jun 2005

    How can i install a mysql teamspeak server ?
    i've imported all create* files to ts database, but the server is still not running

  7. #7
    Join Date
    Jun 2002
    Is there any documentation on how the TCP protocol on port 51234 ?

    I want to develop some apps and it would be nice to see what commands can be sent and what data is expected back.

  8. #8
    Join Date
    Dec 2003
    4858′0″N 107′0″E
    Is there any documentation on how the TCP protocol on port 51234 ?
    Click Start/Run, enter "cmd" and hit enter. Next type "telnet <IP address> <port>" and hit enter. Next type "help" and you're in business.


Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. FAQ - TS 2.x CLIENT
    By eyeQ.MacTV in forum [TeamSpeak 2] Client Support
    Replies: 7
    Last Post: 06-06-2005, 13:27
  2. TS Server dies, ERROR,All,TTSUDPSender.Execute
    By Bones_taw in forum [TeamSpeak 2] Server Support
    Replies: 4
    Last Post: 16-12-2003, 05:23
  3. Can not log in to server ??
    By Ten4 in forum [TeamSpeak 2] Server Support
    Replies: 3
    Last Post: 07-12-2003, 08:03
  4. I cant clik administration after TS restart
    By Schirmer in forum [TeamSpeak 2] Server Support
    Replies: 9
    Last Post: 13-06-2003, 04:20

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts