{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/12/2019 8:44:28 PM
5
Destiny 2 Problems
Hello Bungie,
I gather the past month or so has been quite a challenge so far, what with the move from Battle.net to Steam. I am writing to say that I like many others have issues that prevent me from playing the game. I noticed an increase in connection errors over the past two weeks. They were annoying at first but now they are so common I cannot stay connected for more than ten minutes. The most frequent is currant but also beaver, anteater, moose, and the dreaded - cabbage. Thinking back to when they started I remembered I installed new firmware on my home router from ASUS that same week. Just today I saw there was newer new firmware and I installed that hoping the previous was buggy and it was the buggy firmware that was the problem. Nope. Whenever I enter an area that is populated with other players, bam! Disconnected.
So, to recap - the game is unplayable.
Steps I have taken to try to solve this puzzle. I enabled port forwarding in the aforementioned router and got all the required ports forwarded. I even tried UPnP but not at the same time. Neither helped obviously since I am here crafting this post.
-
The mystery gets more mysterious. I tried to reproduce errors but cannot. On Monday (Sept. 16) I connected to the modem directly and played for a bit. No errors. I then connected to the router and enabled security settings that were thought to be an issue. No errors. I disabled the security settings and got no errors. On Tuesday with all the same hardware and router settings from the day before, beaver and cabbages. Wednesday, no errors. ¯\_(ツ)_/¯
-
4 通の返信Hi. Thanks for reaching out to us. We've noticed a trend with this router receiving CABBAGE error codes. This error code usually implies that there is a security feature happening with the router that is blocking Destiny 2. [url=https://www.bungie.net/en/Forums/Post/252482968?page=0&sort=0&showBanned=0&path=1]A player reported here[/url] that they somewhat resolved this issue by going into their settings [Network Application - ALG Configuration] and disabled everything. This may help you but could also open up your network to outside risks. Typically, we only notice these errors with Thompson and Technicolor routers. Aside from what I said above, the only other solutions I can offer are from other players who found a fix for this issue by following the steps [url=https://www.bungie.net/en/Forums/Post/231008613]in this thread[/url] or [url=https://www.bungie.net/en/Forums/Post/241743364]in this thread[/url].
-
1 返信Well, last night (Thursday Sept. 12th) the game became playable. Ninety minutes of playable without a single disconnect. The thing that is most interesting to me is the degradation over time. The last week of August the errors were few. They got much more frequent as the calendar moved through to the second week of September and by the middle of the week - unplayable. Except for last night. Just like that. Poof! As if nothing happened. It's an enigma wrapped up in a conundrum. A mystery equal to how many licks does it take to get to the center of a Tootsie Pop?
-
1 返信strange I am having issues with my connection and I have an asus router as well. Mine isnt connection errors however, I am just getting massive latency issues. I have tried UPnP and port forwarding as well and my NAT always stays in moderate.
