Just in case that helps some, I solve this by connecting one of the ps4 on the wifi hotspot of my phone. So the ps4 are not on same network anymore You may need a good 4G connexion and enough data (data consumption seems fair but I didnt measure accuratly)

Since this issue has not been fixed in the several months since you created the issue me and my partner have lost interest in destiny. We returned for the dawning but upon seeing the issue wasn't resolved we lost interest quite quickly. We use to play pretty much every day since day 1 only previously taking a break during the content drought last year. If you aren't going to fix the issue just tell the community rather that string us along for the ride promising a fix that's so far taken far too long to arrive

Omg check ur trouble shooting guide 😂😂😂 thats a laugh!! Hang on let me load COD oh wait you mean u can actually play together on a multiplayer game wow! Here i thought it was every game pfft no just YOUR GAME. Love how u tell people its their issue! What a crock u maybe able to fool PEOPLE WHO only just recieved the game 🤔 but not us who actually had a working game before YOU YES YOU DID UR UPDATE HAHAHAHAHA YOU have stuffed up so bad now that No one believes your lies Clearly YOUR NOT READY TO BE DEVELOPERS admit it if you wanted this issue fixed u would have done it by now yet u can nerf weapons and subclasses yeah because that totally out weighs HALF OF YOUR CLIENTS NOT BEING ABLE TO PLAY get a clue how to program a game no wonder the creater left this is a walking disaster not to mention your an embarrassment to the whole gaming community congrats I wonder how many original copys u sold to how many were returned. 🤔

Does Bungie plan to fix this issue? An honest answer would be much appreciated because I am sick of waiting around. My roommate purchased a new tv, a PS4, and Destiny so we could play together; come to find out this isn't possible which is incredibly frustrating. I, along with many others, have invested a significant amount of money in your product and it's disheartening to see this issue has gone unaddressed for so long. Show some respect and appreciation for your users/fans by providing a fix or, at the very least, an update on this issue (November 2016 doesn't cut it).

[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've had the same problem trying to join my wife on the same network. We just get the message unable to join target player. No error codes come up. Had this issue in the past but renaming the xboxes fixed it. Now nothing does. Tried changing the modem settings and all the other tips but nothing works.

My wife and I still have this problem. How can we think about buying Destiny 2 when this is still happening? We should make sure that the game reviewers know that this flaw still exist and point out this flaw for Destiny 2.

Destiny should advise players that have dual modem/routers on review for those setups. I had to reconfigure mine to allow for local network play within my house, since than I have not had any issues or error codes while playing. However, there has been a slight bandwidth share on the network but this appears to something with Destiny codes showing connection strength while playing. I believe the issues may have to do with the operator side of things.

BNGHelp afk? Given up on a solution? Next cash grab gets priority? FIX.THE.DAMN.PROBLEM.ALREADY!!

Why is this still a problem.

Good job at being the worst customer service team in the history of video games. I have a home made work around to YOUR issue. But don't worry everything is going to be ok because Bungie is "actively looking into the issue". What a joke, you guys are the worst.

Skullcollec7er8 and shrillgecko908

Same issue here. Halo 5 multiplayer works perfectly with local LAN fire team. Destiny chokes. So disappointing. I'm actually a new player and bought a second copy specifically to play with my daughter. Spent the evening trying to get this to work. We gave up and just played other WORKING LAN multiplayer games instead. So silly. I thought since this game had been around for a while that basic stuff like this would actually work. It's ridiculous.

Local fireteam connectivity issues are still persisting. When are you going to fix this problem once and for all? You've clearly decided to stop talking about it (the past 2 months anyway)

Up.... Same problem