Stuck on Moderate NAT. Tried everything. (at least I think)

Hi, I just bought an Xbox One a few days ago and also had internet put in here at my new house.

I have BT Infinity 2 - 72 Down / 17 Up and a BT Home Hub 5 router/modem (not entirely sure which one but there's only 1)

So basically, I've tried everything to my knowledge but can't get off Moderate NAT.

I've tried - Port fowarding, DMZ, turning off firewall (temporarily), and UPnP all in different combinations. I also have a static IP on my XB1.

I can't seem to get off Moderate, I haven't even had a glimpse of an Open NAT. Could anyone help me out? Sorry if I laid out my post poorly it's my first post and I did my best

:)

 

My NAT Type Is Behind A Port-Restricted Nat

My Nat Type Is Stuck On Moderate And Cannot Change It.

I Have Tried Everything And It Still Stays On Moderate.

It's Impossible To Change It To Open.

 

connection quality on xbl, titanfall?

it's moderate.

i have the xbo as the DMZ host. got rid of everything in port forwarding to avoid conflicts, but was still stuck with moderate NAT type. so eventually i just gave up.

 

Are you sure that you port forwarded correctly? The Xbox One needs the ports 53, 80, 88, 500, 3074, 3544, and 4500 to be port forwarded. Port forward all of these ports and then reset your Xbox One to see if your NAT opens.

 

I had a similar problem.

Trying those items in combinations probably won't work. That's what I've found, anyway.

The DMZ, by itself, should work.

So should port forwarding, if you forwarded all of the ports listed by bluejellybean0.

UPnP doesn't work properly on all hardware, I'd try that last.

Also, do a multi-player test after making changes, when it's done, hold down both triggers and both shoulder buttons. After a minute or two, this will tell you exactly what kind of NAT you have. You're trying for a Cone NAT.

 

Like the one above me said. UPnP doesn't work on Xbox One.

The only thing that worked for me is the DMZ method.

 

@ blueJELLYbean0 - Double checked and I 100% have forwarded the correct ports.

@ R00K008 - Done the cone NAT thing and it opened my NAT on the dashboard but not CoD: Ghosts.

@ the king ayman - Tried DMZ already and it didn't work either.

Appreciate all the help by the way. Is that everything I can possibly try? Am I stuck with a moderate NAT forever haha?

 

If you're good on the dashboard but not on Ghosts, try opening ports

3075 (UDP) and

3076 (UDP).

I believe those are required for Ghosts.

 

@ R00K008 I tried that still no luck

 

If you try to work with a DMZ and get the message "you are not behind a cone nat" then everything is fine as this is telling you "NAT open". If you still have only moderate NAT on CoD even if you have got an open NAT it may also be a temporarily game problem.
Please understand that the displayed NAT on CoD and the One are two different statuses and that CoD may cause problems because it's its own special kind of network. So first check what's up with NAT on your Xbox. Suggestion is definitively the use of DMZ.

Please have also in mind that you can only use DMZ or portforwarding. Not both at the same time, this will cause issues.

If you still are on a moderate NAT on your Xbox (not on CoD!) even though you use DMZ, then it may also be an issue with your provider. So you should also consider to ask there if they maybe block any ports or protocols or if you are on ip sharing.

 

Okay, so I think I've the issue (at least temporarily). I think the reason why the cone NAT thing wasn't working is because Ghosts was always in my disc drive. So I took it out and then done that and it seemed to work. Thanks everyone for the help, I really
appreciate it

 

The BT homehub 5 is trash. I had one then binned it.

Its UPnP is not fully compatible with xbox one(or ps4 so dont blame xbox).

It particularly struggles with activision games that use demonware port mapping.

COD ghosts and probably Destiny. I say this because destiny beta used demonware to open port 1200 on my tp link router.

So if you ever plan on getting destiny you may have problems with that as well unless you forward the required port which in the beta was port 1200.