Constant beavers

[KilledJoy]

Every. Single. Time. i load in its "Beaver" disconnect from game world to ship, Beaver again and againn and again, yet friend on same wifi currently has not 1 disconnect. What the hell is going on.

5 minutes, 12 "Beaver errors"

[KilledJoy]

Originally posted by ZERO KAY PER CENT:

do you know what beaver means ^^

Originally posted by Bungie:

BEAVER/FLATWORM/LEOPARD 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.

Yes. so. Again, what the hell is going on because it sure as hell isnt my end like I said.

[KilledJoy]

Originally posted by ZERO KAY PER CENT:

Originally posted by KilledJoy:

Yes. so. Again, what the hell is going on because it sure as hell isnt my end like I said.

no, I mean what "beaver" means ^^

Im aware, trying to get help here. Helpful posts

[v]

I'm having a lot of beaver issues too, may I ask you, what country do you live?

[KilledJoy]

US, Wifi is shared in house with others one other playing this game like i mentioned, 0 issues im getting an error every 5-10 seconds once loading in.

[Depthcharger]

Frankly this is how I feel about this too. Season of Worthy.... BAM, Beaver, the occasional Anteater, they all paint a picture of a flawed network setup on MY end, yet Season of Dawn was perfectly fine, I have no other network flaws anywhere, I'm a purely wired network, and security settings haven't changed.

It clearly has occurred on their end yet all the resources seem to tell me I need to look in house for "the problem."

The game is virtually unplayable. Complete loss of progress in strikes, gambits, crucible matches. Even start seeing "lockouts" from failed competitive game completions.

Almost ready to walk from Bungie for good.

[tohita]

100mb/s
all time this f*ing error

[Nyderiwen]

I am getting the same thing, I keep getting either beaver or anteater error codes, and I can confirm that my network has not had any connection issues, no internet connection problems, nor any issues with my connection to my router. The issue is entirely an internal bungie/game issue. Getting real freaking old, real fast.

[THUNDER7DELTA]

glad to know im not the only one, also add anteater to the list..

[Realigo Actual]

go into settings and hit gameplay, scroll down to Network Data and see what you see there

go into your router and see if upnp has anything there for it

if it doesn't, whatever mechanisms you have available and open up that port

[Reign In Blood]

are you forwarding your ports? If wired connection, replace wire with another (swap with your friends). high up/down speeds are less important than packet loss. Modern games can easily be played on a 15/30 connections. its quality, not speed. I would also reboot the router and modem and verify router settings. Search port forwarding for help if you need it.

Good luck.

[EVILE-VON-OVERKILLE]

Hi my name is Wynona I just wanna know...is my beaver trying to leave me?

[EVILE-VON-OVERKILLE]

But Seriously BUNGIE release a beaver arrival in compensations for all the aungishes

[KilledJoy]

Yesterday was Beavers today is Desync from fireteam groups. Blizzard servers not once had this kinda issue lol.

[Forrest Gimp]

Found sorta workaround, at least for free roam. If you join instance, and get disco 2-3 times in a row, go back to orbit and come back in. Odds are, you just hit bugged instance that will be giving you beavers non-stop.

Dudes that post stuff about networking workarounds with routers are funny. Literally every new season D2 servers turn into complete and utter ♥♥♥♥♥♥♥♥. What could be the problem on user side, if say, on my example, I had 0 disconnects or any issues with connection at all, and now I can get dropped pretty much endlessly from anywhere?

[tohita]

at the end, the servers completely failed and became unavailable. the third day