{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/14/2015 10:37:52 PM
1
Error code Mole, Banjo
I was playing Destiny yesterday and got 17 errors over a period of four hours, the majority being Anteater and Weasel. Although extremely frustrating, I figured it may be due to preparation for the patch. I tried resetting my router and my console network settings, along with clearing the system cache and nothing worked.
Today since downloading the update 1.1.2 I have gotten kicked twelve times, including three times from Nightfall. I got errors Banjo and Mole, which I've never seen before, as well as Lionfish and several others (9 different errors so far today). Any help/suggestions would be most appreciated. I have a wired connection for my 360 as well as several ports forwarded thanks to here:
https://www.bungie.net/en/Help/Article/11931
and yes, I have looked at the network settings configuration page.
-
Have had some similar issues. Things started acting strange in the 24 hours coming up to the patch- kept getting "lionfish" - an unusual to the occasional "pineapple" or "hare" that appears. Since then, without warning I have suddenly started getting "banjo" when trying to launch the game. It will happen 5 or 6 times in a row when I start Destiny. Then it finally lets me in and I dont have any problems after that. Not sure what the deal is, Banjo points to my end- but everything on my end is great. I have a 125mbps down 24 mbps up directly wired on new Cat6a cable and have run latency and packet loss tests, etc. At a loss as to why this has suddenly started.
