{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Bearbeitet von 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
-
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.
-
Bearbeitet von panzerfaust: 11/28/2016 6:33:16 PM[quote][quote]Update 10/4Local Network Fireteam IssuesOur investigation has found that routers with "NAT Acceleration" enabled may be causing issues for some players attempting to join a Fireteam on the same local network. Please ensure that this setting is disabled in your network hardware. For information on how to disable this setting, please review the manufacturer's instructions for your device. We are continually investigating this issue to identify other causes.[/quote] Doesn't work. Just disabled fasttrack (NAT hardware acceleration) still have the same results and I'm still unable to join my brother. This is going for almost half a year... This is going from poor to pathetic... It used to work before without issues on the same hardware without any changes...
-
1 AntwortenI didn't get the chance to write this yesterday, but I have a few minutes today. First, you, Bungie, actually said something about this in the weekly update. Color me astonished. My praise ends there. A brief preamble, I work with politicians, and their staff. I've even been on staff. I know all about how to say something without saying anything at all. That's all that you've done, said a few words in an attempt to assuage the players who are dealing with this. Those words ring hollow, forced and pointless. The short truth is that you broke it. You've pretty obviously got no idea how to fix it, or you don't care to. You've got our cash for the expansion, you've got the FoTL suckers money - but that's not funding Destiny anymore, is it? It's funding Destiny 2. Come clean, no more lies, no more empty words. Either fix it, or tell us that you're not going to, because it's too late for this game. #deej #cosmo #bungiehelp
-
If I have to change settings on my router to fix your game and every other game is fine, then you're the one with the issue Bungie. Four months, no fix, I'm begin for to lose my cool. I enjoy Destiny, I really do, but your pointing the finger at us just infuriates me. You are a company with a large amount of resources, you can identify and fix the issue without me having to change all my setting just to play your game. I do hope someone will sue you like EA's investors sued EA over the broken state of Battlefield 4 at launch, because you could use a swift kick in the butt. At least Battlefield gave us free maps and weapons without it being funded by micro transactions.
-
I have tried to use UPnP with a Zyxel ZyWall 110 and a Netgear FVS336G v3 and with both devices using UPnP results in Marionberry error and no playing Destiny at all. I can't find a "NAT acceleration" feature on these devices which I could deactivate. With reference to my post https://www.bungie.net/de/Forums/Post/218489109 you may want to give a comment on how many and what ports should be seen being forwarded by UPnP. For me there's a big gap between the port forward recommendations and what I see being forwarded by UPnP.
-
4 AntwortenBearbeitet von sickmonkeh: 11/20/2016 9:26:33 AM[b]*** Updated for Clarity ***[/b] [b]How to Fix the Local LAN FireTeam Issue[/b] [b]UPNP Info[/b]: [url]https://en.wikipedia.org/wiki/Universal_Plug_and_Play[/url] It helps to have an understanding of how UPNP works. What I was seeing on my wireless network was not the expected result of the SSDP protocol, so I had to make a change in order to isolate the SSDP traffic I wanted, on a network that wasn't filled with devices trying to respond to the SSDP Notify requests. I did some digging into this issue, as I was having the same problems. I reviewed my router and firewall configs and verified that NAT acceleration etc., was already turned off as it's not an option on the Fortinet 60D firewall. I broke out Wireshark and configured my AP settings so that I could sniff the wireless traffic. What I found was that my other UPnP capable devices were interfering with my XBox One UPnP traffic in that the gaming consoles could never get a legitimate SSDP registration response from WR1. [b]Elaboration on the Problem[/b]: Essentially, my other network devices that were UPNP enabled, chiefly Windows 7/10 systems were trying to respond to the Xbox. The secondary Xbox was not among the responders to the SSDP notify packet, nor was the wireless router that I was connecting to. To fix this non-response by the appropriate hardware, I had to isolate the UNPN SSDP protocol to its own subnet in order to avoid interference from other devices. [b]Background[/b]: I have a Fortinet 60D firewall which allows me to assign individual subnets to ports which allows the firewall to do the primary NATting of all outbound/inbound traffic. Since I can configure individual subnets on a per-port basis on the firewall, I can truly segment the two wireless routers that I have, using the routing mechanism built into the firewall to route the Xbox traffic to the wireless router that the Xboxes are configrured on, and all other traffic to my primary wireless router. I understand that standard home networking gear doesn't allow you to assign subnets on a per-port basis, so this may be where many of you are running into trouble. In both instances I'm double-natting. ISP to firewall, then firewall to WR1, and firewall to WR2. However, the only NAT that is of any consequence is the firewall to ISP NAT. [b]How I fixed the problem[/b]: WR1 was left at router defaults and with all hosts except for the two Xbox gaming consoles. I connected a second wireless router to my firewall and configured the wireless settings. The two Xbox consoles were isolated by moving them to the new wireless segment so as to avoid unwanted UPNP traffic. Aside from configuring the wireless LAN for WR2, all other router settings were left at default. [b]Result[/b]: I can now make a FireTeam at will, and have it link up without resetting consoles, logout/in etc. I'm elaborating on my configuration in hopes that it helps, but I cannot guarantee that it will work for everyone. [b]Original Setup[/b]: Internet | Modem | Fortinet 60D 8-Port Firewall with public IP (Natting with routing on a per-port basis) | Fortinet Port1 statically configured with network 192.168.254.1/30 | WR1 with WAN port statically configured with 192.168.254.2/30 | WLAN1 configured with 192.168.1.0/24 Hosts on 192.168.1.0/24: 2 - WiFi TV's 2 - XBox One Consoles 3 - Windows-based laptops 2 - Linux-based network appliances 2 - iPhones 2 - iPads 2 - Android phones This configuration did not work because the Xbox UPNP traffic was being responded to by Windows 7/10 workstations rather than the WR1 router or the secondary Xbox. In order to correct the issue, I had to configure a secondary firewall port with a new network connected to WR2 so that I could host both gaming consoles. At this point I've got a firewall that is routing packets based on source and destination in the firewall security policy, where routing and NAT decisions are truly being handled by the Fortinet firewall and not the wireless routers. Routers only route when the traffic is destined from inside your home network (or local network) to a network that differs from the internal network you are currently on (or is external to you). If the traffic is destined from Inside (your local network), to Inside (your local network), then the packets aren't routed they are switched, and this is where UPNP, not NAT, is important. [b]New Setup[/b]: Internet | Modem | Fortinet 60D 8-Port Firewall with public IP (Natting with routing on a per-port basis) | Fortinet Port1 statically configured with network 192.168.254.1/30 --- WR1 WAN port statically configured with network: 192.168.254.2/30 --- WR1 WLAN1: 192.168.1.0/24 | Fortinet Port2 statically configured with network 192.168.254.5/30 --- WR2 WAN port statically configured with network: 192.168.254.6/30 --- WR2 WLAN2: 192.168.2.0/24 Hosts on 192.168.1.0/24: 2 - WiFi TV's 3 - Windows-based laptops 2 - Linux-based network appliances 2 - iPhones 2 - iPads 2 - Android phones Xbox Hosts migrated to 192.168.2.0/24: 2 - XBox One Consoles Hopefully this helps. Have fun storming the castle!
-
My son and I can no longer play together. We've been playing since launch. We won't be purchasing your next expansion if you cannot resolve the issue.
-
Coming back in this topic once again, just to say that at last you won, Bungie, and me and my wife stopped playing. You've ignored all the players in this thread for so much time that you did a silent and unpleasant choice: you don't care about friends and families playing together. We're probably a very small percentage of your players, so at the crossroad you had two possibilities: force your incompetent engineers to fix this problem, or keep them on Destiny 2 to ruin that game also. Now we know what was the choice. Shame on you, Bungie. Itoriachi, out.
-
Bearbeitet von BJohnny: 11/22/2016 8:52:57 PMI hope this issue is resolved soon. My wife and I have been unable to form a Local Fireteam since ROI launched without jumping through hoops. For the record, we have followed all the troubleshooting guidelines provided by Bungie with zero positive results. The only thing that works for us is following the steps in this post by [b]azzazmarazza[/b]: [url]https://www.bungie.net/en/Forums/Post/217232044?sort=0&page=0&path=1[/url].
-
So I've tried all the suggestions below minus going into my router settings as I'm not a network engineer, and still no luck. I'm very disappointed that Bungie doesn't care enough to fix it. Telling players to adjust settings for one game is a waste of time. I enjoy the game but not being able to play with my kids is annoying.
-
2 AntwortenI bought a new xbox one to play with my wife, can't join fireteam no matter what my isp router is disabled port forwarding by default I have tried every setting in there and I can't get it to work now I feel like I wasted money
-
1 AntwortenBearbeitet von S0ulBearer: 11/18/2016 11:37:37 PMLook, I will not pretend to know a lot about how the back end works for this network stuff and I know it isn't easy. But I just wanted to say as somebody who had terrible issues with this (with that update that started causing issues that you have already noticed), it has gotten much better. At worst, if it doesn't work, we restart both xboxes simultaneously and have no issues connecting. Thanks for the work you have done, at least I can play with minimal hassle with my girlfriend now!
-
2 AntwortenI've been patient. 3 months I've been patient. I've played this game since year one and it has worked dang near flawless until Rise of Iron came out. After the release and update of Rise of Iron me and my brother have tried connecting once a day for three months straight. We've had success twice. It's not our internet or modem or anything, y'all need to stop counting your money and patch this before you start losing money. You've said these BS "solutions" over and over again but that's kinda bad when the players have to fix a game that y'all could patch. Don't tell me this horse manure that "We're investigating the issue" it's been an ongoing issue for three long months! This makes y'all look lazy, it makes it seem like you don't care. Well you're probably going to lose a lot of customers over something that could easily be fixed, and DO NOT say that it can't be easily fixed because if y'all can program a game that is only online then y'all probably have a good team for network issues, but right now it seems like this game has been abandoned. FIX IT!!!
-
1 AntwortenBearbeitet von ProfBraun: 11/15/2016 2:20:43 PMDo you seriously think it's yet alright? Is this supposed to be acceptable? Do you call it yourself support? What's wrong with you, Bungie? Or do you think something is wrong with us? Edit: It may be that I have expressed myself hard, but I do not take anything back.
-
Since yesterday I can't connect with my friend. I was able to join in fireteam cleaning the cache of the PS4 until yesterday. Disconnecting the PS4 and wait to start to play was very frustrating, but I really enjoy play with my friend. Our usernames are jmbarrios and ponchote26.
-
The matter was alluded personally by DeeJ. It may be that I have become too modest ... but, it's good. I think one should not see only the negative. So, it is a small progress that is also due to our constant efforts. A greeting to all the guardians and the ones we have lost (in our networks at home)^^. Have a nice Weekend! B.
-
It was worling before you broke it with the rise of.iron update. Just change back whatever you did!! How hard is it!!! Stop ignoring us, and giving us BS responses like 'nat acceleration' and uPNP....which by the way, in the case of nat acceleration is only selectable on like 1 brand of router, and upnp is on by default for like every new router..... just fix the issue!!!
-
The tards managed to mention us in an update saying ... wait for it ... still looking !!! Useless, give it away Bungie and just be honest that you can't be -blam!-ed looking at it...D2 will be out before you fix it.
-
Hi BNGHelp4, My daughter, and me, has played the game nearly since day one. She was a bit late in buying the last DLC and just did it a couple of weeks ago. We can't connect to play together as we have always done. This is very sad for us and for our clan that is now always divided. :( For some reason it DID work a couple of times during these last 2 weeks. Please advice! Thanks in advance! PSN: Kratoz_SH and: Carro_lollipop
-
1 AntwortenI've stopped playing this shitfest because of this local fireteam issue and won't be buying D2... GG Bungie
-
3 AntwortenDear Bungie, or dear reader, We are 3 in my house to play destiny, from France, and now it's more and more the mess to join the fireteam from the same network. Upnp is well activated, we are all player from 1 year, and yes the bug is more there since one update, it was not so tough to join before. Every time with my son we need to reboot from scratch the ps4...start the game, wait...join, and this is never garantee that it will solve the issue even... My son need to connect to 4g...and magic we can login all together him me and people from our team... Please find a solution, people are tired to just can't play...especially year's one player...you know how many money we put us to play from begining, a minimum of respect to us player no... You know, on the same network, my wife or my son we have zero issue to play other games...so our router is pretty well (upnp or not...).... Thanks bungie, understand that the noise we are doing is never for nothing, like when you do your... stephane
-
1 AntwortenMy wife and I have been having this issue for a while now and this works for us (on PS4 that is.) 1. Both turn off (not rest mode) console AT THE SAME EXACT TIME 2. Turn on Console 3. Open Destiny 4. Pick character THEN IMMEDIATELY 5. Have one join the other. Step 5 is crucial because even a good 5 second delay in between joining will make you repeat the process. It seems Bungie's servers don't realize you are on the same network the first couple of seconds yall log on. "60% of the time, it works everytime"
-
2 Antworten6 Weeks since our last update. Please give us some good news. It's very hard to play with the family when we have to spend 20+ minutes resetting everything just to play a little together after the kids are done with homework. And now today after 30 minutes it's still not letting us join. thanks, -Groupal and family.
-
2 AntwortenAre you all still working on this issue? We are still experiencing it and I'm hoping you have an update on when it is going to be resolved. 3rd post with the same message....3rd post, maybe 3 is my lucky# and you will finally respond?
-
Por favor arreglen esto, de una vez. Please fix this, all at once. https://www.bungie.net/es/Forums/Post/218038965
-
1 AntwortenI just recently bought destiny for my BF and we play on separate tvs but same network and we can't join fire teams . I did not know about that issue until it happened to me . If I would have known that I would have never bought it for him . When will it be fixed so that we can play on the same fire team . This has got to be fixed please
