[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
-
Up.... Same problem
-
Bearbeitet von Qorton: 1/12/2017 1:55:28 AMI have been experiencing issues joining my local network fireteam. We have 3 xbox ones in our house. I play with my 2 sons, 15 and 13. My gamer tag is Qorton and theirs are ChippySnip and xxKNIFECHAOSxx. We have played on a local network fireteam since Destiny came out and only since December 2016 have we started having issues. Very frustrating as this is how I connect with my sons. Fix this please and quickly.
-
Wow, pathetic bungie. -blam!-ing pathetic
-
Hat ein neues Thema gestartet: Can't connect to fire team on local network(1 Antworten)
-
I've given up, 5 and a 1/2 months and you can't fix a simple glitch that you created in a week bungie? That's pathetic. Really thought you might fix things with roi then all those mini updates, then the dawning then the new year. No. You've forgotten about this topic and destiny is no fun anymore. Fix the fire teams glitch before I trade destiny for a better game like subnautica.
-
Bungie, look around at all the sad Christmas Noobs, the angry vets, the disenchanted fanatics, and fix this already! anyway gonna go buy another CoD game to beat while waiting on you.
-
It would be great to get another official bungie update on this topic...silence since 11/17 is pretty sad...
-
Can Bungie please stop screwing me over, or give me my money back, i got destiny to play with my younger brother but cant, cause for some reason, yall cant fix the damn problem thats been going on for months, fix it or give me my effing money back
-
Bearbeitet von RAIST5150: 1/2/2017 8:04:39 PMA thought just hit me in a discussion about security issues in another forum: Wonder if a large part of the problem is the game's insistence on a two-way path between client/server on UDP: 3074. UPnP assigns it fine for the first console to request it, but on some firmwares it may get knackered up when the second console goes to use it? I farted around with the blacklist, and if I block 3074, the game goes nowhere without it. Even if the higher 307x UDP ports are opened/forwarding for the player broadcasts (I set a separate rule to open/forward a block from 3075-3080 in the test)...it goes nowhere fast if you lose 3074....didn't seem to try an alternate port for that specific connection. Not every SPI firewall functions the same....maybe some aren't managing that multiple request on 3074 gracefully? IDK...but maybe we need fallover to 3075 and maybe 3076 as well for those server sessions for the 2nd or even 3rd clients on the local LAN? Or maybe....and I hate to even suggest it because of the extra overhead...maybe that server session needs to flip to a TCP port instead so all stateful firewalls and/or NAT tables can manage it more gracefully?
-
Since the last update, i got troubles to connect, Nothing that I do, connecting the internet directly from the cable, changing DNS, deleting game and reinstalling it completely, NOTHING works! I think they want me to give up of playing the Destiny, neither on twitter nor on facebook or here they answer me or at least one possible solution.
-
Still not fixed I even set the ps4s to separate IP addresses
-
Has there been any update on a eta when we can expect this to be fixed. I have been trying for over an hour each time to play with my son. Very frustrating!
-
This is a very frustrating problem. I have superfast broadband for my business, and we bought 2 extra PS4s, and copies of the game so that my girls and I could play together, in June. At first it worked very well, then as the updates came it got more and more difficult to connect so that we could play. All kinds of jiggery pokery....we ran 2 PS4s off one hub and 1 off another all using LAN. Now it won't work at all! I've reset the routers, ensured they are using uPnP, done everything I can think of. We have tons of bandwidth and good connections. We don't often get time to play together and when we do most of it is taken with trying to join the fireteam. Now we don't seem to be able to do even that.
-
I face the same issue at home and even though my spouse and I are able to join one another for the most time if we start the game and select characters at the exact same time I must say this absolutely annoying. Bungie only wants money. They show no care for its players when it comes to this issue.
-
My biggest suspicion is that it has something to do with Internet/TV providers that do not support UPnP if their routers provide a TV service. Yes I've tried all of it. Connection is a non-issue with other games but I think this problem is so core to the game it won't be resolved until D2 or later. I also don't know why it's gotten progressively worse.
-
This is an enormous issue. Why has no attempt been made to fix it.
-
This is still a problem.
-
In all honesty Bungie is trying to help the situation by asking people to switch to UPnP because it does help with online connect with any online game you are playing. I have seen issue while work for internet technical support where customers only had online game play connection issue and once they set up UPnP setting on their devices they were able to connect just fine. Now I am not saying that it is not Bungies fault because it obviously is but, if there are people whom where having this issue before the update that they find that messed things up for a majority of the people then UPnP might help. I have not been able to play since I downloaded Rise of Iron and I bought two copies of the DLC as well as Three of my other roommates and none of us have been able to play unless we start everything up at the exact same time to trick the internet system into think we are using the same IP and if we get disconnected then we have to start the process all over again. Bungie has to be careful in what changes they make because the fix could cause a lot more problems and make it take a hell of a lot longer to fix it. I trust in Bungie that they will find it but, I am sure that it is not as simple as everyone makes it out to be. I am disappointed 😔 that this is happening and hope that they will in the near future find the bug in their work an fix it.
-
Sure would be nice if Bungie would actually fix this. It's quite obvious this is in no way a priority. It's insulting. I bought two copies of Destiny and all the DLC's out of respect for Bungie instead of using the same digital copy. What do I get from Bungie, no respect for me as a player. All I wanted was to be able to play with my daughter when i actually get to have her for custody.
-
Should I see this issue if I have one PS4 hard wired and one on wifi?
-
[url]http://imgur.com/lYX70XD[/url] Done Bungie, this ongoing issue is utterly ridiculous. Disappointment of 2016, by far.
-
I'm just have general P2P connection issues in general (as of Christmas Day). Not sure if my own connection has just gotten very unstable lately or if it's Bungie or Xbox One. Well...the investigation continues...
-
por favor arreglarlo ya llevo un año ya con eon el xbox y quiero jugar con mi hermano no fue un juego barato para que sus creadores no puedan arreglar ese error en tanto tiempo -.-
-
Error code "cannery" is an issue
-
Bearbeitet von Rain 130: 12/23/2016 1:39:13 AMgoing over the posts, the only solutions that work involve confusing your server. none of the solutions that actually have worked for anyone involve player's network settings. the problem is on your end Bungie, you know what update did it, unlike me you have access to the code, this should be easy for you. sit down and read the code, find the mistake, and fix it. people are going to think this isn't a glitch but an intentional feature before long. Destiny: the only multiplayer game that will send you to an empty world to avoid putting you on the same server as those you want to play with. if you end up using that sales pitch i want credit. i was ok with you and microsoft using my signature but sales pitches are personal.
-
Sadly, there are going to be allot of disappointed Christmas noobs soon. Maybe Santa could sprinkle some of that magic Christmas dust over there and Bungie and magically fix the problem. I think that's the best option we have of getting this issue fixed.