[quote][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][/quote] I'd just like to state something for perspective but let me preface with this, "I am in no way claiming to be an expert or professional on the matter of networking". Having said that I want to tell ppl that networking can be a fickle beast and sometimes finding the issue is easier than fixing it. There are so many factors involved in correcting this sort of issue. Bungie may need 6mo just to gather data, meta-data and logs. Some of you have been able to discover work arounds like leaving team going to orbit then joining together again. This (in my simple analysis) my be due to how your home network systems ( i.e. gateways, routers, switches, etc.) interact with one another and how poorly or how good they translate network data request. NAT (network address translation) and PAT (port address translation) are key factors in this. Unfortunately certain network devices perform this poorly when dealing with certain connection types. This [u]may[/u] be what we are experiencing when attempting to connect to each other within the same household. Transmission of the request out then back in is sometimes fumbled by our own network devices for one game (servers) and not the others. This is a harsh reality of networking but I do agree that we should see more info from bungie but they don't report to us. That's for their CTO to receive. Some may want to try simplifying their setup for example, connecting directly to the gateway or first router after modem eliminating any secondary router connections on the home network. Removing any port forwarding that may have been setup prior. Setting IP designations within the router (DHCP reservations) for each device then ensuring UPnP is enabled. Remove any static IP settings set within the console. Maybe these suggestions help or perhaps they don't but I'm sure the real professionals will have it working for the majority of us soon enough.

My family has given up after 5 months and just installed a second cable to the house so we could play in the same fire team once again. That's $600 per year to fix a Bungie created issue. Oh well at least all manufacturers don't behave this way. Maybe we should tweet Donald - he can kick some arse and get this fixed a la Carrier ;)

Local network fireteams will not be addressed in Tuesday's patch. Shocker. Disappointed doesn't cover it.

That's funny considering me and my spouse play other games together like Division & Watchdogs, yet we come to Destiny since day one and purchased the game and expansion twice over and showed loyalty yet you cannot show any loyalty back to your players, it takes the .... blaming it on our routers... Seriously???

Bogus, none of that works, if we want to play together - me and my partner - he has to go to his parents house which he shouldn't need to do just to play one sodding game....

Still having this issue since June or July's update. Takes forever if jumping through hoops to get matched up. 30 minutes last night. I figure they know what the issue is and how to fix it, but just don't like the solution and want to save face so they are just not doing anything about it. Prove me wrong Bungie with an update which isn't about my hardware.

So, this hasn't been updated since Oct. 6th...

Console: xbox one Gamertag: kylemallanm98 cannot join mkultraops and vice versa Same network all ports opened/forwarded and upnp is enabled 1 xbox is WiFi the other is ethernet

This problem still persists, no one is posting about it anymore because you all have failed. This means your customer base is becoming very upset and now understands that you do not care nor appreciate the situation that you caused to your game. We have paid for a specific set of features and you all have completely dropped the ball by breaking it with crappy net code. Failure to address this has now continues to decrease the number of people willing to purchase Destiny 2. If Bungie and Activision want to continue to make money on this then you will need to resolve this problem. You all do understand how business works and that keeping your customers happy is very important, right? You all are acting like the soup dude from Seinfeld; trust me, your soup (the game) is not worth the horrible way that you are treating the players, you know, the people who are paying your bills!

We manage to play in the same fireteam by disabling the internet connection on one console and re-enable it after a few seconds (Destiny can be left running in the backgropund). Sometimes it works to join the same fireteam after the first attempt, sometimes after several attempts (including restarting the console) and sometimes this doesn't work at all. To be honest - this doesn't sound like an issue with my router. Our "Plan B" - if every thing listed above fails - is to use a 4G WiFi Router and connect one of the consoles to this WiFi router. We have a ZyWall 110 Firewall and there is no option called "NAT Acceleration" which could be disabled. Also UPnP is not working correctly with Destiny - Marionberry at each and every logon attempt. The situation looks exactly the same when exchanging the ZyWall 110 by a Netgear FVS336G v3. No "NAT Acceleration" which could be disabled, activating UPnP leads to Marionberry. I've asked some questions around UPnP implementation with Destiny in another thread, but it appears that the Bungie support is ignoring questions with certain concrete questions whis is very disappointing to me. Also disappointing is the frequency of update information from Bungie concerning this issue. What kind of priority does this have on your side? There are a lot of postings here in the forum from people (including myself) who claim that this fireteam issue wasn't there before the RoI patches came out. To claim that this issue is caused on the home network side may be a bit hard to believe for these people. I think the question from [b]Consternation [/b]is very feasible. If you (Bungie) point out that the fireteam issue is linked to certain hardware constellations on the home network side (which I don't believe, as written above) then please kindly post a list of hardware which enables us to circumvent this issue. Cheers Arnie

Gamer tags are T E M N Y Y and SirMaddog117, have followed all steps but still get the error every now and then...

Whoops

I've been having a local network joining problem. It seems to be with just my sister and I. I can join friends fine, but with my sister even I join a friend and they invite her it won't just work. It's problem seems like it's with the IP adress' that makes it freak out. We tried other things, but they didn't help at all.

I will not ever purchase another game from bungie due to this issue they just do not care about there players anymore. I feel bad for the creative minds that come up with concepts and art and have it ruined by the selfish money hungry team that doesn't care for the players.

My cousin, housemate and I are still having this issue. We had 3 Xbox 1's in our household on the same network, and have just added a 4th for my cousins fiance. We are all trying to play together. Sometimes 2 of us can join a fireteam, other times we can all get in, some times none of us can get in together, and the strange part is sometimes when 2 people are successful in joining (A+B) the third cannot (C) but then if B leaves, C can join A. And it just continues like this. We can temporarily fix the problem by restarting all xbox's completely, but this only works sometimes. I have an Asus AC88U router that is brand new, and I have a hard time believing that this router is having UPnP issues, especially when the Xbox's can all be on the network playing other games, browsing Netflix, etc without issues. I'm really hoping Bungie can at least be more transparent with this problem. Explain to us why it is taking so long to fix.