Xbox One Nat open, Destiny Nat Strict

Good evening

I've looked for help pretty much everywhere so this is my last place I can ask.

Due to age, I exchanged my BBox 2 for a BBox 3 from my provider Belgacom.

I was able to connect my Xbox to it no problem yet whenever I try to play Destiny

I receive warnings that my Nat is strict and get kicked a lot from game.

My first attempt to fix this was call my provider for assistance but those ' people '

refused to help me as it ' doesn't get supported ' for game console issues, his answer was look online. (thumbs up for that customer service btw)

I tried looking on my Router adress to see if I could Port forward or DMZ.

Did not work, infact it doesn't even allow me to do it. I looked on the Portforwarding website guide

but funny enough the screenshots they have of the BBox 3 internal settings doesn't even come close to what settings I can change.

Static IP doesn't seem to help aswell seeing I'm unable to change my xbox one network settings.

My Primary DNS doesn't even look right (instead of an IP looking number, I have a lot of letters, numbers and :'s in it)

If anyone would be kind enough to help me with this issue I'd appreciate it because at this point the game is unplayable.

(It might be an issue with the game but I can not be certain about that)

:)

 

Strict NAT in Destiny

In my Xbox One setting the NAT shows open and all the tests run fine. When I start Destiny I get a brief message that the NAT is Strict. Anyone seen this?



Richard

 

Weird issue with mic

Sounds like NAT or network issues. Sometimes when two people have a certain network config you can play and chat with other people just fine, but not someone else with your same issue.

My wife and I used to have a similar issue with chat in OG Destiny. Check your NAT and make sure it is open not moderate or strict.

 

it maybe a issue with destiny. i had the same issue. my nat type said open and destiny said strict. i do not know how to open port forwarding on bbox3 as i do not have one. the best thing i can tell you is to log into it if you can. most login info can be
found on the box or device itself. click on the tabs until you find port forwarding and fill in all the ports xbox live and bungie recommends. do be scared to search for it. as long as you don't mess with the other settings it shouldn't give you any problems
in the future.

 

I did log in on my router to see if I could do anything in that area.

I used the Portforwarding website as a guide but the screenshots they have

do not match what I see when I log into it. I have no portforwarding option whatsoever

and DMZ didn't work either. There are 3 login options on my router:

User, Expert and Admin. Customer service told me I can't change anything for the Xbox on it and I can't have access to the Expert and Admin login.

 

Boy, Andy, I hate to say it, but you might need to check into buying a cable modem/router on your own, because it sounds like your ISP is more like a Gestapo. I don't know for sure, but simply getting a router (linksys, netgear, etc.) may allow you to forward
the ports as necessary, while still using the BBOX. I have a DOCSIS 3.0 modem through my ISP that I've never actually logged into, I've only ever logged into the router, set up the port forwarding there, and everything worked perfectly.

 

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.

 

Hey Assassin! Try visiting this page:
portforward.com/.../Activision.htm and forwarding the ports which are specific to Destiny. For some reason, Activision's port communication is very odd and doesn't stick to the seven xbox one ports. Many also notice issues with Open NAT but the Call of
Duty mp menus saying strict or moderate.

Let me know!

 

Actually, that link only shows the xbox ports for destiny. Try adding 3075 & 3076 udp.

 

Destiny requires port 1200 for an open NAT.

You should also forward 1001 as well as I've seen that listed somewhere as a possible port.

Port 3075 and 3076 are the call of duty ports.

 

Mal, is that 1001 and 1200 on UDP, TCP or both?

 

I found it, it looks like Bungie is saying just UDP in/out, not TCP.

 

Oh and just to point out I looked at that portforward.com link and most of the ports listed are totally wrong. It gives the wrong port numbers for ps3, ps4 and xbox 1 versions of the games.

 

Interesting.... I looked back at it and it looks like Destiny just has the basic Xbox One ports, not the ones listed on the Bungie page. As for the rest, Call of Duty looks like the only other game with Xbox One specific info, and the rest are Xbox 360 games
at the bottom. Very odd. Makes me wish there was a more complete resource somewhere.

On the subject of Destiny's ports, can you clarify for me the difference between OPENING the ports and just forwarding them? Bungie's Destiny Port page seems to indicate there's a difference, but I've only ever used Port Forwarding in the past. Is there
a substantial difference, or will forwarding the ports for the Xbox's IP achieve the same result?

 

As far as I know open ports just mean they are not being blocked. Traffic can pass through them unless its unsolicitated.

But forwarded means all traffic to a specific ports gets routed to a particular IP address. It means unsolicitaded traffic to that port number can get through

So technically the only ports that need to be actually forwarded are 3074 for xbox live, 1200 for destiny and 3076 for call of duty.

The rest of the ports dont really need forwarding unless they are blocked.

Somebody else could probably explain it better than me though.