12.21
For those who weren’t aware, the TeamSpeak 3 beta has started – infact there has been so much interest the TeamSpeak site ended up using a placeholder page with download links (and just the forum) because there was so much interest (according to their twitter feed, 70 million visitors).
I’ve already struggled and grappled with the server, it never helps matters that I often have to deal with the memory of setting up the Enemy Territory: QUAKE Wars server – which needed both your local IP (NIC IP) and your external IP (from your ISP). But I have done it now, and feel quit pleased about that. So I’ll provide a quick run through of setting it up at the basic level for those who might still be having trouble (including wading through the forums).
This guide will be for those trying to set up a quick and dirty server, this assumes you will be using your desktop PC or one with some form of remote desktop connection. So I apologise for those with remote machines that may require telnet to use, though from what I gather there are plenty of guides (including a video guide) helping you set this up.
Step 1: Download & Installation
You can download both the server and client from this page. Once done install the client, and unpack the server into a location you can access.
Step 2: First Run
There are two very important things to take note of when you first start up your server, it will create a token in the first log file to give your server administrator access; this is one use only. Though you can generate more as the SA to hand out to other users. Secondly it will give you a username and password to access if you decide to use the telnet or ServerQuery; note it down (it appears in the console window on first run)… it doesn’t show up a second time.
I would seriously advise that you create a shortcut to your server (perhaps on your desktop), and tell it to create an ini file (configuration file) with existing settings like so (this will be on your shortcut – “right click -> properties -> Target”:
<install_directory>\ts3server_win64.exe createinifile=1
This will generate an ini file in your server’s install directory (wherever your installed it). This means when your server is run with this shortcut it will generate one of these ini files for use – it should look something like this:
machine_id= default_voice_port=9987 voice_ip=0.0.0.0 licensepath= filetransfer_port=30033 filetransfer_ip=0.0.0.0 query_port=10011 query_ip=0.0.0.0 dbplugin=ts3db_sqlite3 dbpluginparameter= dbsqlpath=sql/ dbsqlcreatepath=create_sqlite/ logpath=logs logquerycommands=0
You should alter all IPs to your Network Interface Card’s IP – this may also pose a problem regarding those with dynamic IPs on the local network, something I do not have experience with. You also have options to use your own custom database server, although I have opted to just keep it simple and use the one provided.
Once you have adjusted the configuration file, you need to get the shortcut to tell the server to use it, so as above you can remove the “createinifile=1″ and then place “inifile=ts3server.ini”.
You can always test the connection with your TS3 Client, try connecting to “localhost” (127.0.0.1) or your IP as entered above; if the latter fails then you have likely done something wrong. You do not attempt to bind the TS3 server to your external internet IP, it will likely fail this and an error will appear in the log files for that session.
Step 3: Port Forwarding
This can often be the bane of all server set up processes, external users will not be able to access your server unless you do all the port forwarding on any routers/hubs – and you will likely have to configure your firewall on your computer to allow the ports inbound, ports are as follows:
VoIP: 9987 (UDP) ServerQuery: 10011 (TCP) File Upload: 30033 (TCP)
If this succeeds, some routers (although this isn’t fool proof), should allow you to connect to your external IP address – but the most fail safe way of testing this is to get someone who is actually external to try connecting to you. Remember, your router (hardware) firewall and your computer’s (software) firewall will need to be configured properly.
Best of luck setting up your server, you can post any troubles you may be having here and I will attempt to answer them; but don’t forget there can be quite a lot of information over in the TeamSpeak Forums!
Other Information
No Comment.
Add Your Comment