Strict NAT in Destiny

My XBox One is saying that my NAT is open, then when I log into Destiny it mentiones i have a strict NAT. I have tried to port forward and all that and even UPnP, but the xbox is saying that the NAT is Open, just destiny is saying its not...i do not know
what to do.

Activision games like Ghosts and destiny don't use the standard xbox live ports which is why the nat can be open on the dashboard but moderate or strict in the game.

When you play ghosts or destiny the game will use demonware port mapping to open required ports via UPnP.

Some routers dont seem to be compatible with demonware port mapping so the NATs in each game will be strict or moderate.

I had to stop using my bt homehub 5 router for this reason.

If your router is not compatible with demonware then you need to use port forwardin to open the nats.

COD ghosts requires port 3076 to get an open NAT.

Destiny beta seemed to require port 1200 and this may be true for the full game.

I am in sweden and could connect to live for a few minutes. Tried signing into destiny servers and got the nessage I needed to be connected to live, which I was. Husband having the same issue as well although my son in the US is online and playing Destiny
with no problems. Have reset everything but still can't get on the server. I also got kicked offline again with it switching to a strict nat. I never have a strict nat. Wth is going on? Why can't we connect but in US they can?

Also before I got the Oct update my Nat settings were strict and i didn't have any problems connecting to destiny since I changed them that's when the problems began

A cone NAT is normal

What game are you trying to play?

Not all games use the same Network port as xbox live so you can have an open NAT on the dashboard but your NAT in the game could be moderate or strict.

For instance COD requires port 3076 and Destiny port 1200 to be forwarded either by UPnP or port forwarding to get an open NAT.