Problems with TS Server - Linksys Router?

[Migasf]

Hello.

I have a problem creating a TS Server for my clan. First I thought that my router was blocking the 8767 port, but then I open that one, and the same error was given to my clanmates:

[20:07:31] Connecting to ***.***.***.***:8767
[20:07:34] No reply from server
Maybe the server is offline
or maybe teamspeak is not running on it

And another thing: I'm not sure was IP address I should give them. What I usually do is go to www.myip.com, copy-paste the address, add «:8767» to it and give them to my teammates. (Sorry for being a TS-Server newb :). )

A friend of mine, who uses Linux, told me to use the address 127.1.1.0 to access my own server, which I did. Am I doing right?

If you need any further details, please tell me.

Thank you,
Migasf

P.S.: Sorry my English errors, but I'm from Portugal ;)

[Bluetooth]

127.0.0.1 is the "loopback" ip. It will not work from outside. 8767 UDP or TCP is opened? Make surew it's open on the incoming section int he firewall, not outgoing. I believe u need to open UDP (or both if you did should work). The IP address you give them is the one you get at: www.whatismyipaddress.com.

How many machines are on the lan? You may need to forward everything that comes into 8767 from outside (internet) to point to your server (ie. 10.x.x.x or 192.168.x.x) in the router.

I hope it's clear and easily understood.

[pim]

It's UDP 8767, no need to open more than stirctly necessary

127.0.0.1 is indeed the loopback interface, as localhost is the local host-name. You can use both to do whatever you want as long as you are on the same machine

However, behind your router your machines have an internal, or LAN ip-address. On these machines open a dos/cmd box and type "ipconfig /all" and you will find those addresses. These ip's you need to use in the Linksys to portforward UDP 8767 to the machine running TS server. Make sure all firewall on the machines are switched off

Also, take the TS-server machine off DHCP and give it a fixed LAN address (in network properties) in the same range/subnet. This to make sure TS-server remains reachable when either the dhcp leases renew and/or you restart your computers

Hope this helps

[Migasf]

My problem has been fixed, thank you very much ;)

[pim]

Care to tell us what the solution is?

[Migasf]

I don't really know what the problem was, because I did all the changes you said and only tested when I was finished. I'm sorry. Oh, and another thing: to enter the server, my mates had (and still have) to use the 2nd IP address shown when I right-click the TS Server system tray icon («You Ip's»), instead of the IP address I get when I go to www.whatismyipaddress.com.

;)

Migasf

[Bluetooth]

So is it safe to say the IP address was incorrect? Did you have a private IP as the 1st one? I am a little confused.

[Migasf]

Bluetooth,

The IP I got from www.whatismyipaddress.com was indeed incorrect. When I was talking about the '1st' and '2nd' IPs, I was talking about those who appear in the TS-Server system tray icon menu. The first one was the IP address of my PC inside the intranet (ex: 192.168.1.101 ). The second was my real IP address (ex: 213.22.64.47 at this moment), the one my teammates use to connect.

Hope this helps. :D

Migasf