Which ports does the server use?
Service How to access Default Port Location to Change Voice TeamSpeak 2 client 8767 UDP Webinterface (see below) Webinterface http://{server_address}:{port} 14534 TCP server.ini (HTTPServer Port=12345) TCP query telnet {server_address} {port} 51234 TCP server.ini (TCPQueryPort=12345) To get your server working behind a router/firewall you only need to forward/open port 8767 UDP.

Some people can't connect to my server, some can. How to fix?

Symptoms: People who are using a home router (NAT) CANNOT connect to your server, but they CAN connect to other servers. People connected directly to the internet, CAN connect to your server. The machine that is running the server has MORE than one external IP address. The server is probably sending replies using a different ip address than the one the clients connect to. (Most likely they connected to an alias, not the primary IP address). Nat routers don't know what to do with this foreign incoming data (unknown IP address and port), and drop the packets. Solution: Open the file server.ini that is created in the same directory where the server executable is located. Look for the following line in section [Main Config]: BoundToIp1= Modify it like this: BoundToIp1=213.202.254.117 This will make the server listen and send only on the specified address. Even easier is to let the clients connect to the primary IP of the machine. You can bind the server to multiple IP addresses by adding additional BoundToIp options (i.e. BoundToIp2, BoundToIp3, etc.) to your server.ini.

Where can I find my superadmin and admin password?

To get the login data for the server administator, do the following: Start the TeamSpeak server. Open the file server.log that is created in the same directory where the server executable is located. Look for the following lines: ??-??-?? ??:??:??,WARNING,Info,SERVER, admin account info: username: admin password: abc123 ??-??-?? ??:??:??,WARNING,Info,SERVER, superadmin account info: username: superadmin password: 123abc For you the password will be DIFFERENT. Also notice that the superadmin account is only for web-adminning your server not to login via the client.

Can I use the TeamSpeak server on my webspace?

If you have free webspace, the answer is: most surely no! Under webspace in general we understand a space where you can upload webpages and somtimes scripts (html, php, cgi, ...). You get those spaces, together with an FTP access for the file upload, usually by renting an Internet connection. A webserver in the background is responsible to 'run' your page. The TeamSpeak server is however not a webpage but an application. To run applications you need much more rights and a shell access (Telnet, SSH, ...). You usually don't get this access for free and even some websapce offers you pay for do not necessarily allow you to run a server. If you're not sure if you have the requirements, ask your webspace hoster, NOT this FAQ!

How do I configure so that the server allows WAN access?

The TeamSpeak server does NOT require a special configuration. It listens per default on all installed IP interfaces. However if a router with NAT is beeing used, a port forwarding is required in the router configuration. Have a look at the according section below. There is a test script especially for TeamSpeak 2 servers. You can test the availability of any TeamSpeak server which should be available from the WAN with that script. You don't need to install anything, simply go to the the link below and follow the steps there: http://ts2test.planetteamspeak.com Please notice that this is an unsupported, unofficial 3rd party script, that is in no way affiliated with TeamSpeak Systems. Do NOT use the WAN IP or serverlist to connect to your LAN server. Your router will most surely not allow this. Within your own network, ONLY use the LAN IP. There is no difference even if you setup a port forwarding in your router, use the LAN IP when ever you or someone else is within the same LAN as the server is.

How do I unpack the Linux server?
You can unpack the Linux server by using the following command: tar -xjf filename.tar.bz2 The filename has to be substituted with the file's prefix.

How do I get a banner on my server?

To stop all the confusion about how to put a banner into the top-right corner of the client: You don't need any TCP query command for it, it's as easy as editing the server.ini. Append the following lines to your server.ini file: [ISP] GFX URL=http://available.for.all.clients/image.jpg Requirements: You need the TeamSpeak 2 server version 2.0.20.1 or later. You need to have superadmin rights. In case you rent a server, you will most surely not have superadmin rights. The image has to be in the JPEG-format. Try to keep the filesize as small as possible (< 50 KBytes). Too large banner files caused problems in the past. The maximal image height is 150 pixels. Please note that the TeamSpeak 2 client will automatically resize the banner to a height of 80 pixels. All clients must have access to the image file so you can't store it just simple on your harddisk. It is known that some image hosters cause problems. You might find more info in our Forums. The server has to be restarted to make a change to the server.ini effective. Simply restarting any virtual server is NOT enough! In case you want to link your banner with a website (on-click), do the following: Open the file server.ini that is created in the same directory where the server executable is located. Look for the following line in section [WebPost]: ISPLinkURL= Modify it like this: ISPLinkURL=http://www.TeamSpeak.com Do NOT add a second entry called ISPLinkURL= as this won't work. In case you have configured a new banner file but still the old file is beeing shown, please notice that every banner is stored in the file imagecache.ini, which should be located in the following folder: %AppData%/teamspeak2/ In the latest client version this cache file does not update automatically. You'll have to delete the old image files manually. A server-side workaround for this problem is to choose a different file name for new banner files.

How do I set the visibility of people in channels?

The TeamSpeak server offers two modes which have to be set in the web administration interface under "Server Settings" by an administrator: Clan Server, which means you can see every user connected to the server, good for servers that have a relativly low usercount. Public Server, which makes it impossible for connected clients to see who is in channels other than the one they are currently in, very usefull for huge servers, where all the "Member left" and "Member joined" sounds would disturb the users and packets submitting data only relevant for other channels would raise your traffic. Actually this designation is a bit missleading as PUBLIC does not mean "the server is open for all". PUBLIC / CLAN mode switches between the visability of all users on the server (independant in which channel they are) / only see people in the same channel and the join and leave sound notification. This settings are server specific, so it can not be set for a specific user group.

How can I recover my superadmin or admin password?
All passwords that were generated when you installed the TeamSpeak server can be found inside the server.log file. If you changed these passwords, there are tools available to recover the passwords. You can find them on our Forums.

Why is my server unable to detect my external IP?

The detection of the external IP is a "nice to have" feature offered by TeamSpeak. This service can not be guaranteed at all the time and there is nothing YOU can do about this. Anyway this has nothing to do with the main functionality of the server itself. The TeamSpeak server will run WITHOUT LIMITATIONS even when this feature is down. You can use a website like WhatIsMyIP.com to find out your external (WAN) IP.

How do I set the max. users to another value than 16?

To edit the max. users of your server you have to use your superadmin account. There's the following reason for it: A server hoster rents his servers and creates different virtual servers (servers which use the same TeamSpeak instance but different ports). Every server has its own SA, but shall be restricted to 16 slots. So a normal SA shouldn't be able to change the max-users of his server, while the SuperAdmin of the server (which is normally the TeamSpeak server hoster) should be able to. Login is done via webinterface. Make sure to use the correct login page (slogin.html). On outdated TeamSpeak servers you'll find a 'SuperAdmin'-checkbox. Afterwards click on 'Servers'. You'll get a list of all virtual servers, you are running. Click on the blue arrow next to the server, you want to edit to select it. Now click on 'Server settings', edit the 'ServerMaxUsers'-field and hit the save-button on the bottom.

How can I access my server via MS Telnet?
This is very simple: Open your Windows start menu Select "Run..." Enter "telnet.exe {server_address} {server_tcp_port}" Type "help" to get a list of all available commands You might want to use a more advanced program that is capable of SSH connections, too. If this is the case, try "PuTTY".

Can I install TeamSpeak as a Windows service?

Yes, you can. There's a native Windows service binary available for the latest TeamSpeak 2 version, which is very simple to install. Download the service binary from the following URL: http://www.teamspeak.com/index.php?page=downloads Copy the file into the same directory where the server executable is located. To install the TeamSpeak 2 server service, just execute the server_windows_service.exe with the -INSTALL parameter. The service can be removed from your system by executing the service binary with the -UNINSTALL parameter.

My TeamSpeak server does not allow the use of '()[]{}' in nicknames. How to fix?
Due to security reasons the server does per default not allow the use of certain chars in nicknames. This is controlled in the file 'server.ini' which is in the TeamSpeak 2 server folder by the following line: DisAllowedClientNameChars=()[]{} If you want to allow this chars on your server, simply delete them from this line and restart your server.

My server shows multiple IPs. Which one do people have to use?

When starting the TeamSpeak server you may have noticed that it displays two (or more) IP addresses. There are 2 different types of IP addresses. LAN (Local Area Network) IP addresses If somebody in your network (LAN) wants to connect to your server, he will have to use the LAN IP address. WAN (Wide Area Netwok) IP addresses If somebody from the Internet (WAN) wants to connect to your server, he will have to use the WAN IP address. Which type of IP address has to be used depends on the situation. How do I see if an IP address is a LAN IP or a WAN IP? LAN IP addresses are defined by an international standardisation board (RFC1918) to be of the following range: 10.0.0.0 to 10.255.255.255 172.16.0.0 to 172.31.255.255 192.168.0.0 to 192.168.255.255 An IP address from one of these ranges is always a LAN IP address and can only be used in a LAN. Hence all other IPs can be considered as WAN IP addresses.

Which options can be placed into the 'server.ini' file and what do they do?

The server.ini contains basic settings for the whole server instance, like the port for the webinterface, the TCP query port, the hoster banner and much more. Some of these settings can also be edited using the TeamSpeak servers webinterface. You can download a sample server.ini file here. The following options are available: [debug] section: MessageTypes - Internal setting (required for windows servers) MessageDepths - Internal setting (required for windows servers) [Main Config] section: ExternalIPDectection - Defines if the server should try to get his external IP using an external server HTTPServer Port - Port for the web administration interface HTTPServer Enabled - Enables / disables the web administration interface DateTimeFormat - Modifies the date and time output format of the TCP query interface and the web administration interface TCPQueryPort - Port for the TCP query interface AllowedClientNameChars - Characters allowed in client nicknames DisAllowedClientNameChars - Characters not allowed in client nicknames BoundToIpX - Needed to bind the server to IP addresses when running on a machine with multiple IPs [WebPost] section: AdminEmail - Email address of the server administrator, retrievable via TCP query and WebPost (* ISPLinkURL - Website address used for the hoster banner and ISP link on WebPost pages (* ISPName - Name of the company or organisation hosting the server (* ISPCountryNumber - Country the server is located in (* Enabled - Enables / disables the WebPost function (* PostURL - This defines to which WebPost the server will post it's information to (* ListPublic - Defines if the server will appear on the "Web Server List" in the TeamSpeak 2 client (* UserAgent - Internal setting (requiered for windows servers) [log] section - Enables / disables the servers enhanced logging capabilities (more...) [Spam] section: max_commands - Defines how many commands may be executed (* in_seconds - in X seconds without beeing considered spam. (* [ISP] section - Defines a hosterbanner which will be sent to all connecting clients (more...) *) Can also be set in the server's web adminstation interface.

Where are my servers's log files?
Both the server.ini and the logfile, called '~/server.log' are in the directory in which you installed/unpacked the server. The log file is beeing created the first time you start the server.

How can I enable the servers enhanced logging capabilities?

In newer versions the verbosity of the server logfile can be controlled in the server.ini. Open the file server.ini that is created in the same directory where the server executable is located. Look for a section named [log]. This section contains the following options: access_r - logs joins and quits of registered users access_u - logs joins and quits of unregistered users channel_registered - logs creation and deletion of registered channels channel_unregistered - logs creation and deletion of unregistered channels sa - logs joins and quits of server admins and granting and revoking of server admin rights chat - logs text messages sent to the server or a specific channel (private messages can NOT be logged) kick_server - logs kicks from the server kick_channel - logs kicks from a channel To enable a log option, set its value to 1, otherwise set it to 0.

When starting up the Linux server it posts "Runtime error 234". How to fix?
In most cases this errors occurs on SuSE Linux boxes, they haven't got glibc-locale installed. Install glibc-locale. After installing you will be fine.

When I try to start my Linux server I keep getting the message "Runtime error 0". How to fix?

In most cases, this error indicates a compatibility problem and can be fixed easily by using a program called "setarch". Detailed information about this utility can be found here: http://www.linuxmanpages.com/man8/setarch.8.php The following example will cause the TeamSpeak 2 server to see "i386" instead of the architecture shown by "uname -a" as machine type: setarch i386 ./teamspeak2-server_startscript start

I can not start the Linux server after upgrading my kernel. How to fix?

You may experience a segmentation fault when you're trying to start your server on Linux with kernel 2.6.x or later. That error can occur with some newer kernel versions. Some people have found workarounds but if you're able to do so, we'd strongly suggest reverting back to a known stable kernel that works flawlessly with TeamSpeak 2. You might also try starting your server using "setarch". Example: setarch i386 ./teamspeak2-server_startscript start