{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Swat The Bot:
6/5/2023 6:15:39 PM
6
Have you checked your NAT type? If your NAT type is anything other than type 1 (OPEN) you will find that you may struggle to matchmake and join people's Fireteams. See the link below for help with NAT.
https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types
[quote] But allows me to join on another system[/quote]
By "another system", do you mean another network or console?
English
-
Same issue here, my network type is moderate, my friend's is open, although according to the help page should still allow me to connect to them
-
Swat The Bot
Bungie fan. Here since 2008 - old
[quote]although according to the help page should[/quote] "Should" does not mean you will be able to. As per the guide, it clearly states "some connections may be blocked" for a type 2 NAT. For the best experience, it is highly recommended you have a type 1 (OPEN) NAT. Refer back to the guide for support. https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types -
While i'm sure this guide is usually helpful @Swat, this is not the issue here. Fireteams which have had consistently perfect connections and that have changed nothing are now experiencing network issues which are erronously throwing NAT errors. This is an issue that bungie is having with only some instances.
-
Swat The Bot
Bungie fan. Here since 2008 - old
If players are reporting that their NAT has changed to anything other than a type 1 NAT, they will experience issues connecting to other players. A player can check their own NAT by running a simple NAT check. A NAT issue is on the player's end. [quote][/quote] If you're having issues connecting to Destiny 2, I recommend you create a post detailing exactly what the issue(s) are, any error codes you're seeing, troubleshooting methods you have attempted and the platform you play on. -
@swat i'd encourage you to look both at other posts in the bungie forum and across other areas such as reddit. Today alone there's been a massive increase in NAT issues for players on Type 1, Type 2 and otherwise. One of the players in my squad was on Open NAT and couldn't get access to the fireteam, there were no players on Strict NAT at all and therefore has never had a problem before today. Destiny's servers are experiencing stability issues and it's important that the Devs see people make these complaints without a blanket "computer says follow guide" approach otherwise nothing will be fixed. [b]As a debugging measure, it appears most of these complaints are from common DNS servers of some UK based ISP's and in some cases, Spectrum in the US. Switching to Google's DNS has been shown to fix the issue for some players.[/b]
-
My NAT is open even done network test for it and it's on console Xbox is the issue but fine on playstation
