JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Nemaxedout: 1/1/2015 7:37:31 PM
2

"Beaver" When Trying to go to Tower or Crucible

For two or three days I have had issues connecting to other people's Xbox's. For example, matchmaking in Crucible does not work. I am able to get to the flying part, but during or as soon as we fly in it gives me the error code "beaver". I have done some troubleshooting and research on the issue because this is the only error I get. Destiny's help section says that that error has to deal with connecting to other Xbox's. So I did more research on trying to fix it. I just set up a static IP address for my Xbox and I port-forwarded the ports necessary. When I test my connection through the Xbox settings, it tells me everything is working properly, and it is. Except for Destiny. When I test my multiplayer connection, it tells me that I have 100% packet loss. I ran a ping test on my laptop through the command prompt and it says 4/4 packets were transferred and 0% packets were lost. I did more research, and other people are having the same problem. They are saying it is probably an issue with Microsoft. My issue is though, I am not able to connect to a Crucible match without getting booted right away. I've been experiencing empty towers and empty strike matchmaking. Is anyone else having this 100% packet loss problem? Any feedback is appreciated! :)

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon