{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Kostek:
10/29/2016 11:15:02 PM
2
Error code marionberry over and over
Hi,
For past 2 months I've been forced to use Alcatel MiFi router and play over LTE. And it worked fine, no lags, always connecting, no problems at all except constant "Strict NAT" message but it didn't bother me, I could play. 3 days ago I got my internet "wired" to my home. It is over radio (broadcast antenna is near so very good signal), symetric 40/40 Mb/s (tested 35/38). Pings are better than LTE (obviously). And provider also said there are no restrictions/firewall on their side that would block any connections.
So I bought new router TP-LINK TL-WR1043ND, connected internet to its WAN port, didn't change any default settings, just checked that NAT option is enabled (this model has such option) and also UPnP is enabled, and no parental security or port blocking. So I made no changes, and I got internet on my PC and XboxOne.
I logged in xbox live, without any problems, then I started rocket league over internet and worked like a charm. Same goes for other games.
So I finally wanted to play destiny, I started it, got title screen which says press "A", so I press it and after about 20-30 seconds I get marionberry error. Every time. Normally I would get a " Select character" screen but no.
I did try Bungie's solution for this error code, for NAT setting and for other networking bugs but no luck. i have to play over LTE and update over "wire".
Can anyone help? Thanks!
-
Edited by Kostek: 11/17/2016 10:38:52 PMSeems like noone is giving a f#%& about this issue..I read more and more people posts about it, always same stupid solutions with restartin xone, router, offline mode and other shit from troubleshot page but THIS IS NOT MY NETWORKS PROBLEM. I PAID DAMN MONEY FOR GAME AND I CANNOT PLAY IT. WTF?! and still other games work...just not destiny, one that I actually enjoyED playing..
-
9 RepliesHey there, Currently, Bungie is aware and actively investigating the issue. You can find current updates and information in the [url=https://www.bungie.net/en/Forums/Post/210716770?sort=0&page=0]Marionberry, Canary, and Local Network Fireteam Issues[/url] pinned thread. Make sure your home network is properly configured by following instructions in the [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13612]'Allowing Destiny Connections' KB article.[/url] After attempting the above, you can provide Bungie additional information by following instructions in the pinned thread, Apologies for the inconvenience. Hope this helps! [spoiler][i]Death is not The Sickness unto death. ~ Soren Kierkegaard[/i][/spoiler]
