Teamspeak banner is kind of essential if you are running your own Teamspeak server for your guild or team. It is one of those things that makes that extra touch or personalize the server. Let’s have a look on how to add Teamspeak banner to your server.
Teamspeak Banner requirements
There are a few requirements to your banner. The Teamspeak banner size is 921 x 236 pixels. It can be a different size, but your Teamspeak client will either crop it or change aspect ratio. Depends on what you chose in the settings for the banner. So to make it easier for your self, just make a banner 921 x 236 pixels.
The second requirement regarding your banner is that it needs to be on the internet. So you will need an URL. You can not upload a banner to the server. Most important, of course, need to be server admin of the Teamspeak server you want to add the banner too.
Teamspeak Banner, step by step
I will assume you are server admin and already entered the privilege key and logged in to the server.
Teamspeak Banner Step 1
Right-click (or double finger tap) the server as shown in the picture. From the popup menu select “Edit Virtual Server”.
Teamspeak Banner Step 2
In the Manage Virtual Server window, you will need to click the blue “More” button at the bottom left corner. Then the rest of the options will appear.
Teamspeak Banner Step 3
In the “Banner Gfx URL” is where you put in the URL for your Teamspeak banners. Or you can actually only link one banner at the time. But you can change the URL anytime you want to.
In the field below (in the URL field) you can enter an URL you can send your users to if they click on the banner.
When done click Apply and it is ready with your brand new banner to customize your server.
Some last notes
If you are not an artist or don’t feel comfortable to make your own banner from scratch, just google for Teamspeak banner template, banner generator or custom banner maker. There are tons of them out there.
If you need to resize, there are also online image resizer to be found. But most computers should have an app to do that for you.
Teamspeak vs Ventrilo was the question for several years in the past. The answer? The thing is that is not just Teamspeak and Ventrilo on the market anymore. Mumble was one of the first to come along, as open source, for free for anyone who could host a server. And now several years later many more are fighting for your voice over IP.
Ventrilo was believed to die a few years ago. Since 2014 no one heard anything from them. No new versions of the VoIP software. No more updates. Then in 2017, as a shock, a brand new version of Ventrilo came. Version 4 came on the market, as Discord was becoming increasingly popular. Stirring up the battle about Teamspeak vs Ventrilo.
Teamspeak has its history too. The first public version of Teamspeak came out in 2001. That is at the moment 17 years ago, many gamers are younger than that. Ventrilo came out the year after, in 2002. And younger VoIP applications have died. Mohawk Voice came out in 2009, only for Windows (at least on the server side) and pretty much died 5-6 years later.Some users even went on Skype?!?!
Teamspeak vs Ventrilo
Ventrilo version 3 allowed users to download and install their own server. Without any license, you could run an 8 slot Ventrilo server. Probably enough for most friendly online battles. Teamspeak, on the other hand, allowed a server without a license to run with 32 slots. Could probably be enough for many clans out there. Sadly there doesn’t seem to be any Ventrilo server available for download now. At least not on their own webpage. Did they gave up on Teamspeak vs Ventrilo.
Ease to use. Both Teamspeak and Ventrilo are relatively easy to use. Teamspeak offers an overlay on top of your game. So you can see who is online, who is talking and so on. No such features are known for Ventrilo.
I can not find a single point where Ventrilo will be better than Teamspeak. If you know of any, let me know in the comment field and I will update the article.
Other competitors who died
It is not only Teamspeak vs Ventrilo out there. Several other software died in the battle for VoIP Domination.
Roger Wilco came out in 1999 and only lasted a few years. They claimed to have 5 million users just before they died in 2003. That is when their last version came out.
Mohawk Voice was one of the last competitors who released a software. They came out first in 2010 and lasted until 2015. Their website is down and no one ever saw version 1.2 of Mohawk Voice.
Xfire came out in 2003 for the first time. They officially discontinued their VoIP software in 2015. One of their more popular features was the ability to record your gameplay for uploading to YouTube and other Video sites. Fun fact, Viacom bought Xfire in 2006 for $102 million.
Competitors still alive
Other companies and VoIP competitors survived the Teamspeak vs Ventrilo fight. Here are the most known software.
Mumble released for the first time in 2005. Last stable release in 2017. Their website is still up and both their client and server software available for download across several platforms.
Skype came out in 2003. Bought by eBay in 2005 and bought again by Microsoft in 2011. Still alive and kicking. But as the gamers say, only noobs use Skype as VoIP. Offers nothing to gamers other than voice and video chat and some sharing functions.
Discord was released in 2015 and is one of the latest competitors and the VoIP software that has stolen most users from all the others VoIP software. Discord uses a centralized server farm, unable to self-host. They have also monetized the software with customization options where you pay a monthly subscription to have animated avatars and stuff like that.
SSH slow login can be a result of recent network changes. If your SSH connection was ok before, and now takes a lot longer. The problem is either with your network or the terminal you try to using SSH protocol from. You can also try to login to the terminal from the localhost. Both can be tedious to fault find.
SSH slow login
Here is what happened to me, and how I fixed it. One day all my servers at home suddenly took 10-15 seconds or longer to connect to with SSH. My external servers behaved normally. So I knew it wasn’t my laptop. Also, all my servers, both at home and externally, is running Debian. Various versions of Debian, but only Debian.
My local internet provider has these really crappy fiber cable modems. Extremely limited settings and general bad quality with its built-in wifi too. I eventually got a decent Asus wifi router but had to move my servers at home to a different subnet. That resulted in ssh login takes very long time. It was not a slow ssh connection, just login to ssh was slow.
I configured the network interface changes, but that did not change anything (except the internet connection). I checked the OpenSSH log. That didn’t give anything away either. Then I noticed the nameserver address in the resolv.conf file. It was set to the old subnet. Here is how my resolv.conf file looks:
After I changed the nameserver over to the new subnet for the Asus router it works like before. Lightning quick login to ssh. Just like before I installed the new router. Because of some stupid limitations in the fiber cable modem, I really had to create a new subnet for the home servers.
Wrong nameserver setting is not the only reason for ssh slow login. There can be other reasons for ssh slow login too. It can also be a good idea to check the configuration for the host in the hosts file.
Some have fixed the issue by setting UseDNS setting to no in the ssh config (sshd_config). Like this:
sudo vim /etc/sshd_config
That will just disable the DNS for the secure shell server. I think just setting the correct nameserver address will be a better solution. Especially if a slow ssh login is a problem when connecting from an ssh client.
Other have solved slow ssh connection issues by disabling the GSSApi authentication. GSSAPI is a framework for authentication. You could try that too if none of the above worked out for your server. You disable the GSSAPI authentication in the sshd_config file.
sudo vim /etc/sshd_config
If none of the tips above helps. Try adding the -v argument when trying to connect to your ssh server. It will print out everything that is going on, and you can see where it hangs. If it is the nameserver settings that is wrong, it will look like the picture below.
After doing these changes a restart is recommended.
If you enjoyed my ssh slow login article you can check out my SSH login message change here. Or how to use the SCP command. An excellent method to transfer files with an encrypted connection on port 22.
Roundcube autoresponder is handy to know for sending out-of-office messages when you are unable to reply to your emails. For self-hosted mail servers, Roundcube is a popular webmail client. It is very easy to set up a Roundcube autoresponder.
If you don’t have your own mail server but want one. Check out iRedMail. That is kind of installing and setting up a mail server all by itself. The default webmail client is Roundcube.
Here is how to set up your out-of-office autoresponder, step by step.
1. Log in to your Roundcube. Usually done going to your mail server. In example mail.yourdomain.com
2. Log in with your username and password. Your username is usually your email address.
3. Go to your Roundcube email settings, like the arrow in the picture below.
4. In the settings column, almost at the bottom, click the Filters. Next, you want to click managesieve in the Filter Sets column. Then in the Filters column, click the + sign to open a new filter rule.
5. Now you filter ruler window should be open. The first thing you need to do is select a name. The name is not important to anyone but you. Just so you recognize what this specific filter rule does. Vrww5gn4 is not a particularly good name. Vacation or out of office would be a better name for this rule.
6. Then you need to select for what incoming emails the rule should apply to. You want to select all messages.
7. Next is execute the following actions. Make sure “Reply with message” is selected. “Message body” is the autoresponder mail itself. That is where you write your message. Message subject is the subject of the mail. Vacation or out of office is good subjects to have here. Reply sender address is the email address you want the recipients to send any replies to. How often send messages(in days), 1 should be enough. Means it send out 1 message to each person who tries to email you.
8. Your Roundcube autoresponder is now finished and click save.
Go on vacation
When you return to office or from vacation or whatever, you don’t need to delete the autoresponder. At the bottom, next to the save button, there is a Filter disabled checkbox. Just check that, and click save. And you can just edit the message body next time you need an out of office Roundcube autoresponder.
Now your email is set up to send automatic messages. So go have your vacation. Enjoy!
Teamspeak is one of the best but not only, voice or communication software for gamers. There are lots of alternatives to Teamspeak. Not that I want you to change away from Teamspeak. I love it, and it the software I use most. I just want you to know about the alternatives to Teamspeak as there might be others that you want to use for other than gaming.
Alternatives to Teamspeak
These alternatives to Teamspeak does are not listen in any particular order.
First alternative – Discord
Discord itself claims you can ditch both Skype and Teamspeak with this software. Claiming it is the only communication tool gamers need. Let’s look at what Discord is. First of all, Discord is totally free and available to most operating systems.
Like its competitors the communication is encrypted. Another good thing is that Discord hides your IP. So no chance of getting DDoS by your enemies in-game. There is also a mobile app, so you can always be in touch with your friend. I have this app just to be able to get in-touch with my son. As he rarely responds to SMS, messenger or any other social media.
Server hosting is taken care by Discord. You manager your server your self via the web interface or the app. Not like Teamspeak where you have to host it your self or rent a Teamspeak server. It is worth to check out. Teamspeak has lost quite a few users to Discord. And is probably Teamspeaks strongest contestant at the moment.
Second alternative – Mumble
Mumble is another great communication tool for gamers and other people who want to communicate over the internet.
Mumble is also encrypted and uses public/private key authentication by default. You can locate your fellow gamers across servers. Easy to set up and has an in-game overlay so you can see how is talking. A challenge with gaming clans with several hundred members.
As with several of the other software, Mumble is free (and open source) and available for most operating systems. No licensing (Teamspeak do you hear that?). Has a great user permission system and several community made web interfaces.
Third alternative – Ventrilo
For several years there were some rumors that Ventrilo was not being developed any longer. On several websites, it says they stopped on v3.0.8 for Windows and V3.0.13 for Mac. I was a Ventrilo user in the old days and went to their website to check this. There I found Version 4.0.0 for both Windows and Mac.
Their interface is a bit simpler than some of the others, but don’t let that fool you. It is still a powerful communication tool. However, their servers are not free. You need to rent from an approved host.
Fourth alternative – Ring
I was told Ring was another alternative to Teamspeak. To me, it looks a bit more like an alternative to Skype. Yes, I know some people use Skype to communicate when gaming. They should stop doing that :p
Ring is can do voice, teleconference, media sharing and messaging. Yea, that seems like Skype to me. If you are looking for a communication tool for gaming, you should probably check out the first three alternatives.
That’s my short list of alternatives to Teamspeak.
If you want to host your own Teamspeak server at home, these are the ports you need to set up port forwarding rules for. If you in the example have your server on 192.168.1.155, that is the IP you need to forward the default Teamspeak ports to. You can, of course, change the default Teamspeak ports. And if you obtain a Teamspeak server license you can add more than one voice server. Then you get additional ports to forward.
Please take notice of the port type (UDP/TCP), as you will need to specify that in your router when setting up port forwarding rules. In some routers, you can select both types in addition to either TCP/UDP. It shouldn’t be necessary to select both types. But if you are unsure you can, of course, try it.
Another option if you have problems forwarding the default ports, is to set the Teamspeak server IP as DMZ. Setting your server as DMZ in your router should be the last resort if anything else fails. As DMZ opens all ports that are not port forwarded to the DMZ IP. And therefore vulnerable to all kind of attacks.
For Teamspeak clients to be able to access your Teamspeak server hosted on your home network. There are services like dyn.com, that most routers support, to give domain names to servers with dynamic IP addresses. If you got a static IP address, it is not a problem. With a static IP address, you can link a normal domain, or sub-domain, to your home server. Other options are to rent a VPS. Digital Ocean rents out VPS starting at $5 a month.