Forum Settings
       
Reply To Thread

Trying to set up teamspeak (port forwarding)Follow

#1 Oct 13 2005 at 12:02 PM Rating: Decent
***
1,516 posts
Ok, I am trying to set up a teamspeak server on my compy. It all works well, but I am behind a linksys router when I connect to the net. In the Teamspeak manual it says I need to use port forwarding to let other people connect to the server.

I called up linksys tech support and asked them to help me out, but they were pretty much clueless. Can anyone help me set up so that I can use Teamspeak? Or is there an alternative I can use, like a public server that I can get a private room in? This would be for no more than 6 people, but we don't want random people hopping into our chat group.

Thanks.
#2 Oct 13 2005 at 12:40 PM Rating: Decent
**
313 posts
Go into Applications and Gaming, I think it is, in your Linksys Router Configuration. Click on the DMZ tab, and input the IP of the PC you want to use for Teamspeak, click save. I don't have my router ATM, my friend is using it so she and her friend can both play FFXI in the same room at the moment, but that's how I always did it. :)
#3 Oct 18 2005 at 2:17 AM Rating: Decent
*
70 posts
I'm very familiar with this, as i just did it to my girlfriend's home network today. I'm assuming that your linksys router is a fairly current model (within 1-2 yrs old. If it's older, you may have to flash the router's bios.) ~Most~ linksys routers require that you first be physically connected to them via NIC card, cat-5cable/RJ-45 connectors ect., not via wireless.

With everything connected and running, open your web browser and punch in 192.168.1.1 That is the default IP Address that your router uses, and will remain that until someone sets the router to a different root address. At some point, you will find it necessary to both get your computer's network address, and verify your router's address.

To get this information, open Start menu, and click on "Run..." In the blank line, type "cmd" to open a command prompt, then type "ipconfig" and hit <enter>. The two lines you are looking for are 1: "IP Address", and 2: "Default Gateway". The address here is your computers address on your network, and usually looks something like "192.168.1.101" Default Gateway is your router's IP Address and, as stated above, is default "192.168.1.1" though it can be different. Memorize those last 3 digits of your IP address, and punch "Default Gateway" addy into your web browser.

Once you've entered that address into your browser, a logon window should pop up asking for username and password. Again, unless set to different values, both the username and password should be "admin", no caps, no nothing special.

Once logged on to the router, you'll see in the top center of the page a list of options. On my router here (Linksys BEFW11S4) i am given in order, "Setup, Wireless, Security, Applications & Gaming, Administration, and Status." Click on "Applications & Gaming" and you should see a list of options across the page right under the first set of options. You should see a list similar to "Port Range Forwarding, Port Triggering, UPnP Forwarding, and DMZ." As IceBlooMafoo stated, you can click on "DMZ," then set DMZ:"Enable", and DMZ Host IP Address: 192.168.1.xxx Remember those last three digits of your pc's netwrok address? Put those in for xxx. Now you can Click at the bottom of the page on "Save Settings" and you should be good to go. However, in doing this, you are "revealing" your individual computer's identity to the world, and it could possibly come back to bite you later unless you've got some decent software firewall / antivirus / pc protection suite to protect you.

An alternate way to do this (and safer for your pc as you are still under the virtual blanket of your router) is to use the "Port Range Forwarding" menu.

Now, I am assuming that you've already set up the Teamspeak RC2 server, and are just trying to get it out to the world. The default port used by the Teamspeak server is UDP port 8767. You can change this port number to whatever you like within the UDP range, though i wouldnt recommend it as you might accidentally choose a port that is used by another program. In a nutshell, just memorize whataver port number you are trying to run your server through.

In the "Port Range Forwarding" menu, pick an open line, and start filling them in from left to right.
Application:(anything works, safe bet to name it something that someone else would recognize.)
Start to:(enter your chosen port here)
End:(same number here)
---by doing this, you are only opening one specific port of your connection to the world, while keeping everything else hidden---
Protocol:(pulldown menu listing TCP, UDP, and BOTH. Choose "UDP".)
IP Address:(192.168.1.xxx Set those last three digits to whatever your network ip address is.)
Enable:(a checkbox. Click it to get that purrti colored x in that box.)

in example, mine looks like this:
Application: Teamspeak
Start to: 8767
End: 8767
Protocol: UDP
IP Address: 192.168.1.103
Enable: (purrti colored x is present)

All that's left is click the "Save Changes" button at the bottom.
#4 Oct 18 2005 at 4:28 AM Rating: Decent
*
70 posts
Assuming that you've finished the DMZ/Port Range Forwarding mess, your server should now be open to the world, or at least to whomever you've created a registered username and password to your server. Now i will go over how to (or at least how I) make sure it all works.

---Please note, that you may have problems doing this depending on what kind of security software you have running on your pc. I'm not familiar with most of these programs. A pretty simple example is for the Sygate Personal Firewall (personal fav freebie.) When you open the server for the first time, a window should pop up asking if you want to allow said program access to [internet (i forgot what words it uses.) In that window, click the little box to allow permanent access, then click yes.---

Get ahold of a second pc or enlist/bribe a guinea pig -erm... friend to give you some of thier time. If it isnt already there, download and install Teamspeak RC2 Client on pc#2. Open the client, click Connect>>Connect. In the Local Addressbook tab, you can hand enter each line of information, then click connect at the bottom. Doing it this way, there is a pretty high chance that something was enetered wrong, and you can waste attempt after attempt trying to figure out what is wrong.

The other way to do this is, in my opinion, more efficient and has less margin for error. Next to the Local Addressbook tab, click on the Web Server List tab. If you havent done this before, the Server List Filter should pop up. If it doesnt,click on Change Filter at the bottom of the page.

Leave all options in the Server List Filter window set to "Show All" except for, in the bottom left, click on "Show servers containing" bullet and put whatever you named your server in the text box. Click OK.

All servers online with whatever you put in that box as part of thier server name will pop up in the list window. Find your server in the list (should only be a few in there, if there's even more than one listing), highlight it, and click "Copy to Local Addressbook" at the bottom right of the window.

Back on the Local Addressbook tab, click on your server's name, and put in your nickname. If you're allowing anonymous users, enter the server password, if any, and any other relevent information, and click connect. If you are registering each user yourself on the server's administration page, click on the "Registered" bullet in the client window, enter your login name and user password, along with any of the other relevent information and click Connect.

If all information is correct, you'll hear "Link Engaged" chime from the client, and boom!, you're on. If something is wrong, you'll hear an "Error" chime, and you'll see a little half-witted guess at why the client thinks it couldnt connect to the server.

Here is where using the server list can be a godsend to your watch. If the server shows up in the list, but you are unable to connect, then you know that there is a problem with the client side login information. Well that, or the information was entered wrong into the server administration page. If your server does not show up in the window, you can assume the problem is server-side.

Looking now at the PC which has your server on it, right click on the server icon in the taskbar. Now mouse over "Your IP's". You should see two addresses in here. One is your network address (192.168.1.xxx), the second should be your ISP's (Internet Service Provider) provided address (something other than 192.168.1.xxx). If you only see the network ip, recheck all of the information you entered into the router... basically start form the very top of my ramblings here, and hopefully you wont read this part again. If you see both numbers, you now know that your network settings are good, you have a software problem.

With both addresses showing, your server is visible on the net, but something is blocking the streams. To check this, reboot your pc, go to lunch, open your task manager once windows gets around to fully loading and close all non-essential programs including your security suite. Now load up the server, right click on the icon, and again mouse over "Your IP's", make sure you have both numbers. Back on the client, try to login. if you still cant connect, reboot the client PC and clear all non-essential programs from task manager, then load client and try again.

If you've made it this far, all i can suggest is email tech support, or *shiver* looking towards Roger Wilco.

-Good Luck (^_^)
Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 32 All times are in CST
Anonymous Guests (32)