PDA

View Full Version : Help with setting up server


mistery1989
18-10-2004, 11:54
I need some help with setting up my own teamspeak server.

I've got my TS Server online, but nobody can connect. The IP's I got are:

192.168.1.101
213.84.147.26

I can connect on 192.168.1.101 but not on 213.84.147.26. Other people cant connect at all. Now I noticed that something most be changed in my router settings. So I have looked there, but what do I have to change ?

Ive made a screenshot off my router: http://mistery.s2swebhosting.nl/router.jpg

Please, is there someone that can help me..
Ive set DMZ (Demilitarized Zone) to 1 allready.

guldi
18-10-2004, 12:13
1) Do NOT use the WAN IP within your LAN (only use the LAN IP)
2) do a search for port forwarding in this forum. In your router I guess you have to check the virtual server section. If possible, do not use the DMZ feature, a simple port forwarding for one port (the TS server port, def. 8767 UDP !!!) is enough.

mistery1989
18-10-2004, 12:43
1) Do NOT use the WAN IP within your LAN (only use the LAN IP)
2) do a search for port forwarding in this forum. In your router I guess you have to check the virtual server section. If possible, do not use the DMZ feature, a simple port forwarding for one port (the TS server port, def. 8767 UDP !!!) is enough.

euhm.. about UDP.. tell me what to change plz ;)

http://www.mistery.s2swebhosting.nl/router2.jpg \

This is the Virtual Server section.

guldi
18-10-2004, 13:40
I assume you've read what info is given on this page (concerning DHCP,..) ?
I'd propose to test the following:

- Protocoll: if possible choose UDP (else leave it on both)
- Port Range: set it to the value you've choosen for your TS server port (default it is set to 8767 => 8767 ~ 8767). You can change this port in the webadmin.
- Redirect IP: here comes the LAN IP of the PC hosting the TS server. In your case this would be 192.168.1.101 (as you've posted earlier)

The TCPQuery Port and the webadmin port you should not forward (unless this is required) !

Finally make sure no port or IP filter is blocking the TS server port.

elitebravo
12-11-2004, 11:28
1) Do NOT use the WAN IP within your LAN (only use the LAN IP)
2) do a search for port forwarding in this forum. In your router I guess you have to check the virtual server section. If possible, do not use the DMZ feature, a simple port forwarding for one port (the TS server port, def. 8767 UDP !!!) is enough. OK then is the udp 8767 in commine and outcomming

guldi
12-11-2004, 11:46
seen from the server the port 8767 UDP is incomming. You can NOT mod. the outgoing port(s) of the server. They're choosen I guess at random (you can test this with a port scanner).

Brain
12-11-2004, 12:45
Outgoing ports or "What is the ephemeral port range?"
We all know that connections on the internet are generally two-way. As such, any IP packet sent contains the source (=sender) IP address+port and the destination (=receiver) address and port.
This is necessary because the receiver has to know where to send his response back.

The destination address and port are quite clear. If you for example want to view Brain's webpage and enter http://www.brainspace.info into your browser, the browser will use DNS to see what IP address www.brainspace.info belongs to and since you want to see a website the destination port 80 is obvious as well because all computers in the world know that websites are on port 80 by default.

The source address is quite clear as well - it's the IP address of your computer. But where does the source port come from? Web browsers (and client programs in general) don't have a world-wide unique port where web servers send the websites to.

This is where the ephemeral port range comes into play.
This word monster simply describes a pool of dynamically allocatable local ports. On Windows the ephemeral port range is 1024 to 4999, as it is on BSD. However that range isn't fixed, you can easily (or not so easily) define another range, for example 60000 to 65535 or whatever you see fit.
The Operating System manages this pool of port numbers. Programs can request to be assigned ports from this pool and the Operating System makes sure that not two simultaneously running programs get the same port number. It also watches the allocated ports and hands over all incoming data to the appropriate applications.


Example:
Let's assume you've just booted your Windows. You open your browser and type "http://www.brainspace.info" into the address bar. The browser now looks up the IP Address of www.brainspace.info, and generates an IP packet that looks like this:
Source address: AAA.BBB.CCC.DDD (your IP)
Source port: 1024 (browser says: "hey Windows, give me a port!" and since no other program has made a connection to the internet you get the first port from the ephemeral range)
Destination address: 213.239.199.177
Destination port: 80
Content: HTML-Representation of "hey Webserver, give me your start page"

Now Windows makes a note that incoming data on Port 1024 belongs to the browser until that connection to the web server is closed.