Setting up a game server behind a router

[SpaceyWilly]

I figured out which port the game uses, now what do I do to free it up? I've tried adding the game "Enemy Territory" to the applications menu in the router (a dlink dl-650) configuration program, but I wasnt really sure of the details

For example,
a) should the port go under trigger port or public port?

b) what type of trigger is it, TCP or UDP or both?

c) if the game port is the trigger port, what do I put as the public port?

d) what IP address should I tell people to connect to? The IP of my modem (66.182....) or the IP of the computer on the network(192.168....)?

So far, I have been able to access the server from another computer on the network by pointing the game to the computer's IP address (192.168.0.103), but it does not show up on the list of servers.

Any suggestions will be appreciated.

[Krusty]

1. you need to have people connect to your public IP address if they are not on the local network, not the 192.168.*.*

2. Generally, the trigger port is the same as the public port. For example, if warcraft3 uses tcp port 6112 to host games, you need the people who want to join the game request to connect through port 6112. In order for them to actually make it to your computer, warcraft is looking for requests for port 6112 as well.

My router is slightly different than yours, so the rest of this may differ:

My computer has 2 different settings for opening ports. It has 'virtual server' and trigger ports. In virtual server, you set the public port and private port to be the same (for simplicity. this way, its like there is no router). In the trigger port stuff, you can pick one of those virtual server ports to cause other ports to open up. Lets say you only have 10 spaces to enter virtual server ports on your router but you need to use 50 different ports to run your server (we'll say you need ports 20-70). You could set a virtual server port for, say, port 20. Then in the trigger ports, you set the trigger port to port 20 and set it to trigger ports 21-70.

TCP and UDP are two different protocols. If you do not know which one to use, you could either set 2 different virtual server settings: one for TCP and one for UDP or you can test to see which one makes it work. Most of the instances I have come across use TCP.