Port Triggering (not forwarding) configuration.

Hi, what is the exact make/model of router you are using?

[quote user="Siddo"]

...I have 3 xboxs all with different IP addresses. To configure port triggering ...

[/quote]

I would advise against port triggering, as this would only help if only ONE of each consoles is online at the same time. As soon as two or more consoles try to go online, port triggering will fail.

Instead you should use UPnP, if possible. If your router does not properly support UPnP with your consoles, you need to try if there is a firmware update available for your router, or buy a new router.

For more information you could also read the NAT post linked in my signature which also has a list of compatible routers that support multiple Xbox consoles.

Hi the Modem is a betgear DM111G. The router is a netgear WNDR4000 (N750). Very unlikely that more than one xbox will ever go online at the same time so port triggering seems my only option. The router does support uPnP but seems it seems very shaky in working. That is how it configured at the moment and an example of how shaky is if I go straight into COD black ops, multiplayer, login to live when prompted, get to the lobby it say NAT strength is moderated. Start all over again and login to live first and I get the same. Start all over again and run a xbox live test connection first and I get NAT open. V weird. Will check in the router config to see if any ports get registered in uPnP in any of these circumstances.

Cheers

First of all ensure you are using the very latest version of firmware.

If you do want to use triggering turn off UPnP and set up triggering, looking at the manual it shows the option to do TCP or UDP or both so I'm not sure why you can't set that up?

So leave the "Service User" as Any and then trigger these ports accordingly:- support.xbox.com/.../xbox-kb.aspx using TCP, UDP or both as relevant

Yup, latest firmware all round. For triggering you need to set the triggering port and this can only have a type of TCP or UDP and not both. The service type of the incoming connection can be TCP and UDP. So where it says a port is both for configuring port-forwarding for the xbox, does that mean both for the incoming connection (which is fine) and if so what type is the outgoing connection. If it is TCP or UDP and not both then I can configure port triggering. If not then I am screwed. There is also (don't hurt me) a PS3 in the mix which is an even bigger pain in the butt. Much poorer uPnP support and very shaky everything for online use. I have made the PS3 my DMZ server as I only have the one and gets it out of the way.

Well you can see what I can't :) I can only quote from the manual:-

"Select the service type, either TCP or UDP or both (TCP/UDP). If you are not sure, select TCP/UDP."

Even if you can't set-up both (TCP/UDP) you could still do two separate entries to cover both? So for example a TCP trigger for 3074 and a UDP trigger for 3074

Hi, Thats what the manual says. However, for the service type it does not give the option of BOTH. I will contact netgear about this.

Cheers

Ok, even so you should be able to create a UDP entry and a TCP entry

Nah, Once a port has one set of config it will not allow a second

Really???? So for port 3074 it won't allow you to port triggering on:-

3074 UDP

3074 TCP

If not then that is certainly a bug to take up with Netgear