{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by BNGHelp5:
12/10/2016 12:01:55 AM
1389
[BUNGIE] UPDATED 11/17: Marionberry, Canary, and Local Network Fireteam Issues
[quote][b]Update 11/17[/b]
Since the release of Destiny Update 2.3.1.1, we have been investigating an issue where players on Local Networks are unable to form a Fireteam within Destiny. We have made some progress in identifying the root cause, and are continuing to investigate ways in which we may resolve this issue.
We wish to ensure Destiny remains stable for all players. One change may resolve the issue at hand, while creating more issues that impact a greater number of players in alternate ways. As such, we must approach any proposed networking changes with caution and vigorous testing.
For players impacted by this issue, please ensure that UPnP is enabled, if possible. Not only do UPnP settings create a better Destiny experience when playing online, this also makes it possible for multiple consoles on a Local Network to form Fireteams. Additionally, manual port forwarding on your network may negatively impact your ability to connect to other players in Destiny. For additional information concerning UPnP, please see our Network Troubleshooting Guide.
[/quote]
[b]Previous Updates[/b]
[spoiler]
[quote][b]Update 9/15:[/b] From [url=https://www.bungie.net/en/News/Article/45223/7_This-Week-At-Bungie--09152016]This Week at Bungie - 09/15/16[/url]
[b][u]Local Network Fireteam Issues[/b][/u]
Since the release of Destiny Update 2.3.1.1, we have been investigating an issue where some players are unable to join Local Network Fireteams. Through our investigation, we have identified some of the causes for this issue. Destiny Update 2.4.0 addressed one of these, and we are continuing to investigate other potential causes.[/quote]
[quote][b]Update 9/9:[/b] From [url=https://www.bungie.net/en/News/Article/45188/7_This-Week-At-Bungie---09082016]This Week At Bungie - 09/08/2016[/url]
[b][u]Local Network Fireteam Issues[/u][/b]
[url=https://www.bungie.net/en/News/Article/45172/7_Destiny-Update-090816]Destiny Update 2.4.0[/url] contains a potential fix for an issue where players were unable to join Fireteams with other players on Local Networks. If you continue to experience this issue, or encounter any other issues after accepting the update, please let us know by posting a thread in the [url=https://www.bungie.net/en/Forums/Topics/?tg=Help]#Help[/url] forum or visiting our pinned 2.4.0 Known Issues Thread.[/quote]
[quote][b]Update 9/1:[/b] From [url=https://www.bungie.net/en/News/Article/45135/7_This-Week-At-Bungie---09012016]This Week At Bungie - 09/01/2016[/url]
[b][u]Local Network Fireteam Issues[/u][/b]
Over the last few weeks, we have been actively investigating an issue which is prohibiting players on Local Networks from forming a Fireteam. We have identified the issue, and are investigating a potential resolution. [/quote]
Hello all,
With update 2.3.1.1 an issue was introduced where players experiencing connection issues were not receiving proper Error Codes when attempting to log in to Destiny. After successfully logging in, players experiencing this issue were not able to launch activities or performing other in-game tasks.
On Aug. 9th, 2016, we have reverted back to the previous behavior which allows these players to see these error messages again. If you are met with Marionberry or Canary error messages consistently when attempting to log in, please refer to our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url] for proper network settings. If you continue to experience these issues, you may need to contact your ISP for further assistance.
Investigations concerning Local Network Fireteam Join Issues are ongoing.
As a first troubleshooting step, we recommend that all impacted players ensure that proper connections are allowed for Destiny Gameplay. Please see the [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13612]Allowing Destiny’s Connections[/url] page of our Network Troubleshooting Guide for a list of Ports that should be allowed, unblocked, or forwarded.
[b]NOTE:[/b] We highly recommend disabling any network restrictions going to your Console, as this may cause additional issues when attempting to play Destiny.
Additionally, players should clear the cache of both consoles on a local network, and attempt to form a Fireteam once more.
[quote][b]If this issue continues to impact you and your desired Fireteam members, please post a report below.[/b]
When filing a report, please provide the following information:
• Have you [url=https://www.bungie.net/en/Help/Article/12539]cleared cache[/url] of all consoles on your local network?
• Have you followed appropriate steps in the “[url=https://www.bungie.net/en/Help/Troubleshoot?oid=13612]Allowing Destiny’s Connections[/url]” section of the Network Troubleshooting Guide?
• Are you experiencing any specific error codes when attempting to join Fireteams, or are you only witnessing “Unable to join. You were unable to join the Fireteam.” messaging?
• Please list the PlayStation Network ID’s or Xbox Live Gamertags of all impacted accounts.
[/quote]
[/spoiler]
English
#Help
-
16 RepliesUpdate: I have previously commented (3x) on this issue. Essentially the same experience as most of the posters in the thread. Followed all the Bungie recommendations to the letter. Also tried two different high-performance wired routers (Ubiquiti ERL (with miniupnpd2 UPNP, the best open-source UPNP implementation) and a Netgear Nighthawk X4S). My ISP is Comcast (Blast). All three XBox Ones consistently report Open NAT, and we have never had any problem with local fireteams on any game other than Destiny. We could all also play Destiny at the same time, no problems, just not with each other. Our Destiny local fireteam problems started back in July, just like most of the posters. I had been broken since. Always the immediate "Unable to join target..." error. But a couple of weeks ago, it started working, and has been bulletproof since. There was nothing that I did on my end. We tried it a few days after RoI came out, just in case it worked, and it did and still does without a hiccup. So, to speculate... it seems pretty apparent that the root of this problem is in the Destiny server implementation, in the way that it allocates/load-balances player traffic. Sometimes you get lucky and your local fireteam players land on the same (or otherwise co-hosted or compatible) servers, and it works... and sometimes (most of the time) not. Which is why all the crazy spam-the-join-button, quit-and-relauch, simultaneous-join, etc. work-around stories appear, but none are reliable/repeatable. I also suspect that there may be some elves working in the background at Bungie Ops that are able to manually provision load/server-allocation based on the Gamertags we report. This may be dependent on geography, network provider and datacenter allocations, and many other factors. Which may explain why they can fix some of us, but maybe not all of us. And, also why there is no console patch that can fix it and it doesn't show up in the release notes. I am reporting this because I expect that a lot of people that have experienced the local fireteam problem and reported it here, may have had their problem resolved. Most happily go on with their lives, and don't report the resolution here. I am a networking engineer, and have had to deal with problems like this from the other side. It's hard, and I feel for the Bungie Ops team. But, the lack of communication and transparency on this is really problematic. And there is no excuse for it. Those of us that have bought multiple consoles, multiple copies, DLCs, etc. are probably among Bungie's best net-promoters and they are doing irreparable damage to their reputation with their silence and perceived indifference. WAKE UP and OWN UP! Good luck to all, Dave
