{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Der Sheff:
5/16/2016 8:07:44 PM
10
Error Codes: Baboon and Weasel
Been getting a string of errors lately. It starts with "trying to connect. Baboon." Then I get booted and a Weasel code. I lose party connectivity and have to sign out and sign back in. I've restarted both my Xbox and Router. Not sure where to go. I am on Xbox One. When I switch to the 360, I have no problems. Any suggestions?
Edit:
The error codes are actually taking my router offline...
Added the #MayMelee tag as the error codes started post update.
-
Bump. I've had a serious resurgence with error codes.
-
Weaseled like crazy
-
3 RepliesHi Der Sheff, Are you still encountering this issue? If so, you may want to try clearing your console cache as a first troubleshooting step. Here is a guide on how to do so: https://www.bungie.net/en/Help/Article/12539
-
Having the same problem with Weasel errors. Never was a problem before.
-
5 RepliesBump. Still looking for help.
-
3 RepliesI switched my one to power saving mode and it fixed everything. Havent had an issue since. Not all ones have the issue though... give it a shot!
-
1 ReplyWeasels are typically due to an overload of information and your system not being able to process it fast enough. It's most likely due to a DDoS attack, that's how they most commonly occur, but otherwise they occur because of destiny's crap servers not knowing how to send or receive information.
-
3 RepliesThese are typically NAT connectivity based issues and there aren't any specific ways to prevent them. Your best bet is to retry whatever it is you were trying to do or change up your router's port settings so that you can allow the necessary connection responses to the game's servers to pass through unrestricted.
-
Bump.
-
It's the stupid SBMM I swear...I just made a video about this.
