Teamspeak Server Troubles
There are thousands of things that can go wrong with every application, but some just aren’t your fault. You’ve checked your settings, you’ve made sure your headphones are plugged in, but every time you try to log on to your favorite teamspeak server it cuts you off. Here we look at some common errors and let you know when it’s not your problem, when it is, and what to do about both.
“No reply from server”
This one certainly sounds like they’re in the wrong - why isn’t the server replying to you? You have to remember that while these error messages are true, they don’t always mean what you think: “no reply from server” could mean that the server isn’t there at all, or it’s running an SMTP database, or it’s underneath four meters of water and can’t really deal with your audio-exchange request right now.
The most common cause of this problem is the simple typo which leaves your client looking in the wrong place for the right server. Another is that the teamspeak server you’re looking for isn’t there anymore. Smaller servers, especially clan voicechat servers, may flicker on and off depending on whether they can pay for them that month.
“Got a bad response from server”
How dare the server give you a bad response! But this isn’t the server being rude, or rather, not being any ruder than a bouncer normally is when you try to get into a club wearing the wrong clothes. This response means that you’re using one version of teamspeak, the server is using another, and never the twain shall meet. If you’ve just installed the software you’re likely using RC2, meaning that this address must be the antiquated RC1 version. Solution? Go somewhere that isn’t using stone-age voicechat technology.
“Codec not supported”
Another case of concise but unclear wording obscuring the meaning. It could be interpreted as the server’s inability to support your audio codec, one among many options, but the fact is it’ll be because your codecs are out of date. You’re trying to connect to a modern communications net by bashing your stone-ax and lionskin loincloth against them and the server is having none of it. Leave, update your codecs and drivers, and come back.
“Error Getting List”
You’re looking for a new place to play, but when you click on the web server list you don’t get a list. You get an error. An “error getting list”, so to speak.
This one genuinely isn’t your fault. Your poor little desktop program can’t find the list because there’s no list to find - something has gone wrong at Teamspeak central and you’ll just have to wait until they can fix it. It normally doesn’t take long, though in the meantime you may be forced to extreme measures like “talking to people in real life.”
Random Reboots
When using Teamspeak your desktop reboots itself at random. To say that this is mildly frustrating is like saying a thermonuclear explosion in a volcano is a bit hot - especially since it has a tendency to leave your Frigate unmanned and unpowered with enemy raiders coming in (or whatever).
This, also, really isn’t your fault. Microsoft were good to their word of “no more bluescreens of death” promise with Windows XP, but in a doublespeak manner of which the finest political spin doctor would be proud. When Windows feels it might end up in a BSOD it automatically reboots the system - rather than “generating an error message” or “telling the user what’s actually going on.”
To fix this go into Settings in your Control Panel and click “System/Advanced/System and Recovery/Settings” and in “System Failure” uncheck the “Automatically Restart” checkbox.
