[BUNGIE] UPDATED 11/17: Marionberry, Canary, and Local Network Fireteam Issues
Since the release of Destiny Update 18.104.22.168, 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]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 22.214.171.124, 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]
With update 126.96.36.199 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.
I posted this last week and am posting it again as the message got buried under more people having this issue. Like everyone else on this thread, I am beyond frustrated with this issue that's been going on for me since August. I can't believe Bungie hasn't fixed the code that they broke by now. Below is a solution that has been working consistently for me on my two Xbox Ones. It may or may not work for you.
Temporary solution for Xbox One :
Both players start Destiny, choose a character and go to the Tower (don’t try to join each other)
Once in the Tower, each player hits the Xbox button to minimize the game, then hit the Start button and choose “Quit” to quit out of Destiny
Both players should immediately start up Destiny again
As soon as you get to the main splash screen, hit the A button to start Destiny
Destiny will try to start but then you will get a “Weasel” error
Both players should then hit the A button again
The game will start and both players can choose their characters
You can now probably join each other. If you can't, try this a 2nd time and it should be successful.
(I am not the founder of this work-around. Credit for this solution goes to a user named Tom Nighthawk)
Not sure if a similar solution will work for PS4 users or not.
If this doesn't work for you, there is one other option that works for me: I set up my iPhone as a hotspot and connected one of my Xboxes through the iPhone. Definitely not an optimal solution as it uses wireless data.
Diese Webseite verwendet Cookies für Analysezwecke, personalisierte Inhalte und Werbung. Durch Anklicken des „Annehmen“-Buttons erklärst du dich mit diesen Bedingungen einverstanden. Näheres erfährst du unter Datenschutzerklärung.
Diese Seite verwendet Cookies für Analysezwecke, personalisierte Inhalte und Werbung. Durch weiteres Browsen dieser Seite erklärst du dich mit dem Nutzen dieser einverstanden.Datenschutzerklärung