{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/28/2019 10:09:26 PM
2
Hi Foxy. Thanks for your report.
What region are you located in?
WEASEL and BABOON errors indicate that you are experiencing a general networking issue. This could be your internet connection in general, your connection to the Destiny 2 servers, or even an internet service provider issue. You may want to review our WEASEL article for more information that may help with your issue.
Here are some steps you can take to try and resolve the issue:
[quote]
[b]1.[/b] Performing a [url=https://www.bungie.net/en/Help/Article/46501]Scan and Repair[/url] in the Battle.net app
[b]2.[/b] Power cycling your internet router
[b]3.[/b] Review our guide on [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13603]improving latency and packet loss[/url] to see if that might help
[b]4.[/b] Following our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url] for best optimizing your connection to Destiny. If issues persist, try our [url=http://www.bungie.net/en/Help/Troubleshoot?oid=13610]Advanced Steps Networking Guide[/url] for possible router solutions, such as enabling UPnP and IPV6.
[/quote]
English
-
由「 F o x y 」编辑： 5/1/2019 1:48:38 PMHello again~ Okay, I actually took my time to check my network properly within the last days and NO it is definitely, as I already expected, NOT my network!! I reinstalled Battle.net AND Destiny totally new. I ran several speedtest as soon as I noticed that I'm kicked out again (I had a speedtest page open, waited untill enemies stopped shooting which means I probably have 10 sec untill Im kicked. So I started the test as soon as they stopped shooting). Nothing here, all normal. My line is up and running! The only thing I actually noticed is, that Battle.net seems to have the issue with the connection, because in the upper corner, where the connection sign is, it is disconnected for some time (even tho I DO have a connection on my PC). I even contacted my provider and they also checked for me and said they couldn't find andy issue. But, again, it is NOT my router, NOT my internet, NOT my PC! Every other page and game is running fine and the stats are fine too. And apperently, as I can see it over the last few days on this page, I'm not the only one in europe who has that [b]exact[/b] issue! Since yesterday it's actually not the Weasel error anymore for me but only Buffalo and Bee. And I KNOW Buffalo is a connection error. But that issue, I assure you, is not on my side. I ceckted it. Multiple times. So please... do not answer me with tips for my side. I know my way around on my end and it's always the first thing I make sure to check if something happens. I will provide you with everything you need but please do not send me help-pages with steps I already did before I even reached out here. It gives me the feeling you dont even read what I tell you... ~Foxy
-
The BUFFALO error occurs when there is a connection issue with Battle.net's servers. You may want to review our BUFFALO help article for more information about this issue. If that doesn't help: [quote][b]1.[/b] You may also want to try opening the battle.net launcher "Settings" and change the "When I open a game" option to "close the battle.net launcher completely" option. [b]2.[/b] Some players have suggested disabling Internet Protocol Version 6 (TCP/IPv6) on the PC might help with this issue. [b]3.[/b] You may want to change your region/server to another location. [b]4.[/b] Some players have suggested disabling the "Always require authenticator for login" option in your Blizzard account settings. [b]5.[/b] Some players have reported that disabling IPV6 has helped them with this issue.[/quote]
