Xbox One and 360 on same router - NAT type strict on 1 open on the other

I have a U-Verse modem/router combo, a 2wire 3801HGV. I then have one of the ethernet ports going into a Netgear Gigabit Switch GS108 which I am connected to, my brother is connected directly to the router.

The problem is that whenever his NAT is open, mine is strict. And when mine is open, his is strict. I've tried a number of things such as assigning his xbox to DMZ mode in our router so all ports are open for him. His firewall is disabled on the router
and is assigned to a public IP. I set up a user defined application with the following ports for my xbox:

tcp 53

tcp 80

tcp 3074

udp 53

udp 88

udp 500

udp 3074

udp 3544

udp 4500

I cannot disable the firewall to my xbox and assign it a public IP because the public IP is already assigned to him, my router wont let me disable my firewall unless I have a public IP but it's already taken.

Is there anything else I can do to have us both have open NAT types without having to get a better router?

:)

 

NAT Type is Open on Xbox One, But Strict on 360

My NAT type on my 360 has suddenly changed from open to strict. Nothing has changed with my network, I haven't gotten a new router or modem, and my Xbox One still says that my NAT type is open. I've tried some different things to fix it, but I don't understand
why my NAT type went from open on both consoles for a long period of time to strict on the 360 for no apparent reason.

 

Help with a strict NAT type

Hey guys just fixed the strict nat type problem. I have an optimum modem with one cable slot on back for my router. My router was making my nat strict. I put one of those cable spliters into my modem plugged my modem and hardwired xbox cable into the other
slot on the splitter and nat was then open.

 

Are you able to enable UPnP on your router? (Universal Plug and Play)

That could correct the issue.

Let us know. In the meantime I'm going to see if someone better than me with networks can take a look at this.

 

When you opened the ports, did you use Port Forwarding or Port Range Triggering?

If you used Port Forwarding then only one console will get that at a time, the others connected will have their NAT changed due to another using it, but if you set the ports using Port Range Triggering, than any device using the ports opened should, theoretically,
be able to.

As a side note, there are a lot of routers out there, specially older ones, who cannot handle multiple NAT uses very well, as i'm not familiar with your brand, i do not know if that could be the case.

Change what i said first and see if that does anything, and let me know, and i'll see if i can figure out something.

 

One thing to check is, depending on the network hardware, some devices are not able to support multiple consoles with Open NAT. Since one console is able to be open while the other goes to strict, this seems to be the case with your particular network configuration.
I attempted to look up your network hardware in the Network Hardware forums (forums.xbox.com/.../default.aspx), but was unable to find your devices
that you listed.

 

Modem router combo , bad .....separate modem , separate router , GOOD!!.....just been through this and solved it today.....netgear wrn2000 (45 bucks) solved it......

 

[quote user="Camp Nowhere"]

... The problem is that whenever his NAT is open, mine is strict. And when mine is open, his is strict.

[/quote]

So far so problematic.

[quote user="Camp Nowhere"]

I've tried a number of things such as assigning his xbox to DMZ mode in our router so all ports are open for him. His firewall is disabled on the router and is assigned to a public IP. I set up a user defined application with the following ports for my
xbox:

[/quote]

That won't work. If you put a console in the DMZ, it's basically telling the router "Let that DMZ console have ALL the incoming traffic first!", resulting in a strict NAT for your console.

If you then set up port forwarding rules to your console, it depends on how the router firmware was programmed. The router could then say "Give ALL the incoming traffic to the DMZ Xbox, but my human master went and created manual rules, that I will *always*
honor before the DMZ!", which will result in the DMZ console having a strict NAT, and your console having an open NAT.

Or the router could think "Okay, that's nice that my human master made these port forwarding rules, but there is a console in the DMZ, that is needing just these ports at the moment, and I'll priorize the DMZ over the port forwarding rules", resulting in
the same strict NAT for you as before.

[quote user="Camp Nowhere"]

...I cannot disable the firewall to my xbox and assign it a public IP because the public IP is already assigned to him, my router wont let me disable my firewall unless I have a public IP but it's already taken.

[/quote]

That's what the DMZ does. So, this is "by design". It takes ONE device and acts as if it is directly accessible to the internet. And only ONE device can be in the DMZ at any time (for most consumer routers).

[quote user="Camp Nowhere"]

Is there anything else I can do to have us both have open NAT types without having to get a better router?

[/quote]

If you already limit yourself to the "without having to get a better router", you can only hope that your current router gets a better firmware update that supports multiple Xbox consoles at the same time.

If there is no better firmware update, the answer is "No." :-(

You won't be getting around a new modem/router it seems.

 

I had this on an old router I had with multiple Xbox 360's. In the end I bought a gaming router and it solved the problem with multiple Xbox One's and Xbox 360's connected. I opted for Netgear WNDR37AV since it got decent Amazon reviews and mentioned the
NAT in some of the reviews. Works like a charm.

 

So after a lot of irritating trial and error I finally got it working.

What I ended up doing was removing the public ip from the xbox 360. I got a router and assigned the public ip to my router instead then disable the firewall to it.

On my router I set up port triggering for the ports that I listed in my previous post. Once I did that my NAT immediately switched to open. I wanted to make sure both systems did in fact have open NAT types so I started both my xbox one and the 360 and
connected them both to xbox live. The xbox one tells you from the network settings what your NAT is, the 360 as far as I can tell doesn't directly show you like the one, but when you retest the connection on the 360 it will tell you once it's connected that
you have a strict NAT.

I started my xbox one up first and it said OPEN right away, I then connected with the 360 and I didn't get the strict NAT warning I did before. I checked the one again just to make sure and both systems had an open NAT. I haven't had any issues with chat
and getting disconnected from games anymore.

One question though, why wouldn't port forwarding have worked? I initially tried that but for whatever reason I still had a strict NAT.

 

[quote user="Camp Nowhere"]

One question though, why wouldn't port forwarding have worked? I initially tried that but for whatever reason I still had a strict NAT.

[/quote]

That's because you can only manually port forward one port to one device only.

With Port triggering, the router actively watches which device requests the port, and dynamically forwards it to that device: "Hey, the Xbox 360 sent data on port 3074, so I'll forward the ports to the 360." (A bit later) "Wow, now the Xbox One sent data
to a port on my watch list, I'll re-route the incoming data there now".

Port triggering however ONLY works if the device FIRST sent out data on a specific port (the trigger port).

With Port Forwarding, you manually tell the router to route incoming traffic on (a) specific port(s) to one specific device. If you try to route a port to a second device, most routers will tell you that this port is already assigned to a device already
and can't be forwarded anymore.

The problem the router has is, that the router needs to decide to which device an incoming data packet should be sent.

Unfortunately, if the Xbox in your network did NOT initiate the conversation first, the router will not know to which device in your network (Xbox 360, Xbox One, your PC, your sister's laptop, etc...) the data packet should be sent.

The same would be true if it were possible to port forward to two devices on the same port. If a data packet arrives, should it be sent to Xbox One or 360?

With Port Triggering, the traffic gets sent to that console that requested and triggered the port most recently.

 

I am glad it worked out for you, buddy.