{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/10/2014 1:55:34 PM
2
Xbox one open nat/ Destiny strict nat
Hi all!
I'm a newbie on this but i'll try to explain my problem, my xbox one shows an open nat and when i run the various network tests it's everithing fine but when i launch Destiny, the game tells me that i have a strict nat type, anyone has experienced this? Sorry if there is another discussion on this argument but i haven't find anything similar...if anyone can help i'll appreciate!
Sorry for my poor english and thanks in advance
English
#Help
-
Edited by BillFngMurry: 12/2/2014 6:44:23 PMI've been having the exact same issue with conflicting NAT types. My Xbox One says it's open, but I get the strict NAT warning when I launch Destiny. I see this thread is a bit old now. Have you found a solution? It's only been happening to me since the previous update to Destiny. I know my gateway is setup correctly, and everything else connected to my network reports an open NAT, except Destiny. I ignore it as much as possible, but I get booted from the game world frequently. Doesn't happen during Crucible much, or when playing a strike, but I get booted from the free roam A LOT.
-
1 ReplyIgnore it.... You have 3 type's of NAT Type 1 - directly connected to web or via the DMZ function of a router (this is the only setting where Destiny doesn't gives the Strict NAT message) Type 2 - connected through a router with common ports open (often enabled through upnp) (probably your setting, because the xbox says it's open, everything should work with this setting) Type 3 - strict setting, router will block a lot of ports, often trouble to find other players and/or to use voicechat
