JavaScript is required to use Bungie.net

Hilfe

Hilf uns, dir zu helfen.
10/14/2015 10:36:06 PM
2

Weasel, Canary, Marionberry - Same error code sequence for 6+ months now

For at least the last 6 months and maybe longer I have had my share of Destiny connection issues. They always occur in the same order, Weasel->Canary->Marionberry. First, come on, combine these into one code if they are legitimate issues and not some sort of glitch. My real question though is what is this about, and why does it persist after a dozen or more patches? I find it very hard to believe, as many would try to tell me, that I am the problem. That either through my choice of router, my ISP, or sheer stupidity have caused the problem. I have a 100mbps down and 25mbps up connection through Cox which I routinely verify to be giving me what I pay for. I had a $200 gaming router, properly configured, open NAT, port forwarding/triggering, everything that is recommended. Even ran the Xbox One through the DMZ with a static IP. All of this over both WiFi & Ethernet (gigabit over Cat5e). Fast forward a few months and one home move later, and I bought a new $200 ASUS router (which is freaking awesome) and I am still encountering the same errors, in the same sequence, but maybe with slightly lower regularity. Is it possible this is related to my console? My roommate is on the same network, same settings, playing the same game, and never gets booted, especially with this error code combo. PLEASE HELP!

Sprache des Beitrags:

 

Bearbeiten
Vorschau

Benimm dich. Nimm dir eine Minute, um dir unsere Verhaltensregeln durchzulesen, bevor du den Beitrag abschickst. Abbrechen Bearbeiten Einsatztrupp erstellen Posten

Gesamtes Thema ansehen
Es ist dir nicht gestattet, diesen Inhalt zu sehen.
;
preload icon
preload icon
preload icon