Today, May 15th, marks 3 months in which Destiny 1 players encounter the beaver error all the time. nothing has been done until today, and the worst thing is that when someone talks about this error here on the forum, moderators say it's our internet problem and the problem comes from bungie
-
Hi Im Swat
Bungie fan! Here since 2008 - old
Hey, pedroowinicius I'm here every day and your post is the first I've seen about 'beaver' error's in Destiny 1. If you know of other player's having issues with Destiny 1, could you please encourage to post on Bungie.net for support? Thanks. As for the error, please see the information below regarding this error. [quote]BEAVER errors are caused by a failure to connect your console to another player’s console via the internet. This can be caused by connection quality issues (such as packet loss, ISP saturation, or general internet congestion). It can even be caused by certain WiFi setups, faulty in-home wiring, or other issues that require on-site support or expert investigation. However, they are most commonly caused by router or network configuration issues. - These errors are most common when multiple consoles are connecting to the internet through a single router. Some players have been able to work around this issue by enabling UPnP on their router. - Strict NATs tend to see these errors far more often than Open or Moderate NATs – [url=https://help.bungie.net/hc/articles/360049024092]opening your NAT[/url] can significantly reduce the frequency of these errors. - Some types of connection quality issues (packet loss, etc) can trigger this family of errors. If you are using WiFi to play Destiny, we strongly recommend switching to a [url=https://help.bungie.net/hc/articles/360049496871]wired connection.[/url] https://help.bungie.net/hc/en-us/articles/360049195651-Error-Code-BEAVER[/quote]