Xbox one says my nats open, but games says its not.

Well during the beta it would say that it was caused by my nat, now it just gives me a error code and tells me to go to help.bungie. I'm getting bee and centipede errors, are you getting the same error codes? I will mark your previous statement about forwarding
1200 as the answer seeing as the game is no longer saying I have strict nat. Until bungie says other wise I'm going to assume this new problem is on their end. Thanks for the help Malacath!

P.S I forwarded the port you suggested plus the ports bungie told me to as well.

 

retrolink im having the same problems I keep getting the bee and centipede errors my nat is open and behind a cone nat like yours. I dont even lag online but about jalf way through without warning it just kicks me out the game I had the same problem in the
beta to. I dont understand why this is happening as I can play other shooters that would take up similar bandwidth.

 

I'm having the same problem with Destiny. My X1 always says my nat is open, but destiny says it is set to strict and I get booted from games a lot with a load of different creature codes given. It's making the game unplayable as I rarely get through a mission
without being disconnected.

Also having issues with party chat where after a minute or so I will lose the ability to hear anyone or be heard by them.

 

I'm also having this issue and have tried various methods but with no success. It really is becoming infuriating, please, please please if anyone knows of any other methods let me know!

 

@The Reddevil 84 and @Ownz vengeance

Post the make and model of your routers. If someone has the same routers they may be able to help.

Also there is a bug in destiny effecting people using university campus connections that causes them to have centipede errors. It also effects some home users as well. Apparently bungee are looking into it.

 

Here is a update to my situation crucible seems to be where the biggest issue lies for me, when I play 6v6 modes I usually get kicked half way through, when I went and played lower player count playlists like salvage or rumble I haven't gotten kicked so
far, but it could still happen. The notification that use to pop up when I would go to orbit that said your nat is strict even though my one said it was open is gone. I have all the ports that bungie has suggested for me to port forward unless I did something
wrong which I will admit I don't know completely what I am doing I just go by what little I do know. If it helps I've tried to apply the same methods I used to make my one open to make my 360 open and nothing works. I get the feeling that my one says its open
and I am behind a cone nat but I don't think I actually am, one of my friends can join my party with a strict nat but when he tried to join my Diablo game it wouldn't let him. Honestly there has to be something wrong with my UPnP I shouldn't be having this
many problems, Malacath this may seem like a dumb question but do I have to do anything special to make my UPnP work on a console or should it just automatically work with any device that is connected to the internet? Could settings I have set on my router
be causing issues, like not port forwarding correctly, static ip issues, having dmz activated... I've thought about resetting my router to default settings to see if the errors would go away.

 

Before I made it out that the size of the player count mattered, I was patrolling on venus with just me and my friend the only people in the server and I still got the bee error code.

 

Yes UPnP should just work although you need to use address reservation in the routers settings to tell it to always give the Xbox the same IP address. Otherwise Nat issues may return. Also IP address in the Xbox settings should be set to automatic as I've
found with my router that if I set a static IP in the Xbox itself the UPnP wont work.

 

I have a BT Homehub-2, I've found that having DMZ activated is the only solution although I am still getting kicked from games, however the destiny servers are not registering my nat as strict anymore...

I'm getting the error code Bee I'm not sure if this is due to having DMZ activated on my hub or not. I have found resetting my hub to default settings improved the speed of my network in general, I would advise doing this as on a Homehub there are little
downsides.

 

Yeah the home hubs are terrible.

Don't bother upgrading to the latest home hub 5 as those hubs are terrible. They are not compatible with the Xbox one(or ps4 for that matter). The UPnP on them is not compatible with demonware port mapping that Activision games use and require port forwarding.
I would recommend anyone with BT to ditch the hubs and replace them with a decent compatible router.

 

I have Madden 15 and NHL 15 and I have trouble connecting to players online. NAT says open but I get the Teredo

error 2 out of every 3 times I play my Xbox one. Frustrating!!!!!!

 

I found out if your having the error code: Bee on Destiny, it is caused by packet loss.