This is outdated, and overly-complicated advice. Port forwarding is an obsolete solution, with several limitations: - the console doesn't know what ports are being forwarded, so it can't tell other consoles what ports it's on, or know with certainty what its NAT status is - the console can't decide for itself what ports to use, so if you want to have, say, an Xbox One and a 360 on the same network, you are SoL - You're setting up which ports get forwarded manually, so if these requirements change (say, in a dashboard update), you need to find out about them and make the changes yourself. There's a far better solution, and it's one OP got so close to before snatching defeat from the jaws of victory: [b]get UPNP working[/b]. UPNP IGD is a modern technology that solves all these problems: the console itself requests ports be forwarded, and the router tells the console what it's doing. Port forwarding through UPNP just works: switch on your console, and it will discover the router, and ask for its ports, without you needing to configure anything. If two consoles want the same port, the router tells the second one it can't have it, and the second one will pick a different port. Because the second console has been told what's going on, everything still works perfectly. You can even join the same multiplayer session and party chat on two consoles behind the same router. [b]So how do we set up this amazing technology?[/b] The answer is very simple: we get a router that supports UPNP, use that as our new main router, and remember to switch UPNP on. We tell our ISP's router that our new router is the DMZ machine, so the ISP's router forwards all ports to it. ...and that's it. No messing around with static IPs, no messing around with port mappings, no messing around with settings on the consoles. Switch them on, and they just work.