{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Big Daddy Wayne:
4/20/2021 3:30:54 PM
1
Constantly kicked, anteater & weasel
When I load into an activity with other players I get contacting destiny servers followed by a brief disconnect with the error code "anteater". Sometimes it reconnects me to the activity and sometimes it does not. If it does reconnect me, it will always kick me back to the menu screen after a few seconds with the error code "weasel". Every time I load into the tower I also get the weasel error, either kicking me instantly or after about 30 seconds. I have a decent wired internet connection and it is not the cause of these error codes. After many attempts I was able to complete a battlegrounds after I loaded in by myself with no connection issues. This leads me to think it has something to do with matchmaking and only happens when other players are present. I have had this issue for the entire season and it's really frustrating, any help would be greatly appreciated.
-
Edited by ErMahGurdXBurkz: 4/16/2021 5:19:48 AMI'm having the same issue. Has only been a problem this season and only when I'm in a fire team. Error code is nearly always anteater. Makes Trials and GMs nearly impossible. My connection is wired. I've replaced my modem. I've forwarded my ports. NAT is open. I even restored my entire console to factory settings. My ISP has been to my house 2 times and they are insisting it's not a problem on their end. Not having this issue with other online multiplayer games... I've been seeing people reporting this since the console launched. It would be nice to at least get acknowledgment from Bungie that they're looking into this.
