Runing a server behind a router?

[Jerry Jenko]

Well, I came that far that my server was working on NAT but then somehow something got messed up with ports and ppl can't send in their voice because of ports, how could I set which ports to use?

[Dummer Sack]

Default port of TS is 8767 UDP. Look in the manual or the FAQ for the other ports (You only need to forward 8767 UDP for normal operation).
If you want more info do a search for "Port Forwarding" in the forum.

[guldi]

you can see your current TS server port in the webadmin (if you by accident changed it). If you can't connecto to the webadmin, this port is in the server.ini

[Jerry Jenko]

Originally posted by Dummer Sack
Default port of TS is 8767 UDP. Look in the manual or the FAQ for the other ports (You only need to forward 8767 UDP for normal operation).
If you want more info do a search for "Port Forwarding" in the forum.

Well, I forwarded that 8767 and the 14000 something for the console and suddenly yesterday clients could not send their voice in :(

[Dummer Sack]

Make sure that your LAN IP did not change.

If you did set it to "optain IP address automatically" in the network settings, it is possible that it is changing. Then you have to update the port forwarding at the router.

I recommend to configure your TS server manually to a fixed IP.

[Jerry Jenko]

Originally posted by Jerry Jenko


Well, I forwarded that 8767 and the 14000 something for the console and suddenly yesterday clients could not send their voice in :(

well, I'm quite sure that wouldn't be it, the problem it is that it binds clients to ports like 2700 and 1605. Can I set to which ports he can bind them to?

[Dummer Sack]

No. The client is using a random source port between 1024 and 65563 (but it will not bind to that port/listen on it).

But even if the source port would be static you can not be certain the incoming connections come from that port because the user may use NAT. And in this case the source port is always more or less random anyway.
If you use a firewall do not filter by source port. Filter by destination port.

[Jerry Jenko]

Originally posted by Dummer Sack
No. The client is using a random source port between 1024 and 65563 (but it will not bind to that port/listen on it).

But even if the source port would be static you can not be certain the incoming connections come from that port because the user may use NAT. And in this case the source port is always more or less random anyway.
If you use a firewall do not filter by source port. Filter by destination port.

And where could I set that?

[Dummer Sack]

Originally posted by Jerry Jenko
And where could I set that?
Man be more precise. I have no glass ball or telepathic abilities. What do you want to set where?

If you mean how to configure your firewall then I have to pass. You did not even mention what Firewall you use. As I already said I have no telepathic abilities.

[Jerry Jenko]

:P

Ok, well I have a router and its a stupid one so I can't forward like 28000 ports like in Linksys, well, my issue is that clients connected can hear me but others can't hear others.

[jonnyz0109]

What router do you have? I just finished setting up my server, I am using a D-Link 604 Router/Firewall, and with the help of this and other current threads, along with some FAQs, I was able to figure it all out and get things working! Maybe if you tell me what router you have I will be able to help you with its settings.

[guldi]

@Jerry Jenko

if you "only" have a router with no firewall, then you only need to forward the incoming connections to the TS server port (default 8767). You DO NOT need to forward all the ports the clients could use (NAT is handling this ports). It's good to know the basics aout NAT as you're no playing with it. I recommand doing some research in the web or in this forum. It's much easier if you understand how the things work.


However if you have a firewall running, blocking outgoing connections, then you will need to open ALL the UDP ports mentioned in the FAQ for the client.

[Dummer Sack]

Ah, a D-Link.

EDIT: Ups, I misread the posters name. So If you don't have a D-Link then this just gives you a general picture what to do Jerry Jenko.

Just search Open Ports Setup in your router config (You should find it under NAT Setup).
There create an new Open Ports rule.
As Local Computer you enter the LAN IP of your TS server. As Protocol you choose UDP. As Start and End Port you choose 8767 (If you have changed the ServerUDPPort in the web interface use the one you specified there).
If you want the web interface externally available add another port with protocol TCP and Start and End Port 14534.

The source port of the incoming packtes is irrelevant in the port forwarding.

Before you fiddle with your network config bejond the port forwarding make sure all clients work correct.
Make them all test the local test mode.
Then all join a public server like voice.teamspeak.org and make sure all is working correct there.

If you still have problems make sure that your router firmware is the most up to date one. Check at D-Links website for updates. Also search a router forum where they know your router and check if there are known problems with specific firmware versions.

If you have activated the integrated packet filter you have to allow the following traffic:
Incoming: Source IP: any, Source Port: any, Destination IP: any, Destination Port: 8767
Outgoing: Source IP: any, Source Port: 8767, Destination IP: any, Destination Port: any

[Jerry Jenko]

^ well I did that, I have Digitus Link, something German firmware 1.96c, well I allready have opened those ports, console works fine, I can give the login if maybe someone would need it, well my server was runing great, but once it just went bad.

[Dummer Sack]

I don't know Digitus Link.

So I cannot help you further. But if it did work then somthing in your setup must have changed. Try to find out what has changed.

I don't know what else to do.